Another Python namespace pollution (was: r147958 - in /trunk/libstdc++-v3: ChangeLog Mak...)

Gerald Pfeifer gerald@pfeifer.com
Thu Jan 27 19:54:00 GMT 2011


On Thu, 27 Jan 2011, Gary Benson wrote:
>> The files should reside in a directory that is private to gcc or
>> at least mangled with the gcc version it comes from.  Otherwise
>> multiple parallel gcc installations conflict.
> Ah, ok, that shouldn't be too hard.  I'll get working on a patch.

Thanks!

In case you are wondering where to put them, there is prior art
based on Tom's fix:

  ./share/gcc-4.6.0/python/libstdcxx/__init__.py       <--- The good
  ./share/gcc-4.6.0/python/libstdcxx/v6/printers.py
  ./share/gcc-4.6.0/python/libstdcxx/v6/__init__.py
  ./share/python/classfile.py                          <--- The bad
  ./share/python/aotcompile.py
  ./lib/libstdc++.so.6-gdb.py                          <--- The ugly :-)
 
Gerald



More information about the Java mailing list