This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Another Python namespace pollution (was: r147958 - in /trunk/libstdc++-v3: ChangeLog Mak...)
- From: Gary Benson <gbenson at redhat dot com>
- To: Richard Guenther <richard dot guenther at gmail dot com>
- Cc: Gerald Pfeifer <gerald at pfeifer dot com>, Tom Tromey <tromey at redhat dot com>, gcc-patches at gcc dot gnu dot org, java at gcc dot gnu dot org
- Date: Thu, 27 Jan 2011 10:59:52 +0000
- Subject: Re: Another Python namespace pollution (was: r147958 - in /trunk/libstdc++-v3: ChangeLog Mak...)
- References: <20090528171422.508.qmail@sourceware.org> <Pine.LNX.4.64.0905282258430.24872@digraph.polyomino.org.uk> <m33aan21h4.fsf@fleche.redhat.com> <Pine.LNX.4.64.0905291955130.18075@digraph.polyomino.org.uk> <m3y6sfzk3y.fsf@fleche.redhat.com> <m3ljofzhtd.fsf@fleche.redhat.com> <alpine.LNX.2.00.1101021134130.4999@gerinyyl.fvgr> <20110127103801.GA5165@redhat.com> <AANLkTikxP-MPRBiy-HU55LwtD63Wb+c8Roa6ikJjPhzx@mail.gmail.com>
Richard Guenther wrote:
> On Thu, Jan 27, 2011 at 11:38 AM, Gary Benson <gbenson@redhat.com> wrote:
> > Gerald Pfeifer wrote:
> > > I noticed that coming from the Java side of things we also have two
> > > files that are installed in common namespace:
> > >
> > > ? share/python/aotcompile.py
> > > ? share/python/classfile.py
> > >
> > > These have been added by the following patch from all can tell:
> > >
> > > 2008-06-30 ?Joshua Sumali ?<jsumali@redhat.com>
> > > ? ? ? ? Andrew Haley ?<aph@redhat.com>
> > >
> > > ? ? ? ? * configure.ac (java-home): new AC_ARG_ENABLE.
> > > ? ? ? ? (aot-compile-rpm): Likewise.
> > > ? ? ? ? :
> > > ? ? ? ? * contrib/aot-compile.in: New file.
> > > ? ? ? ? * contrib/aotcompile.py.in: Likewise.
> > > ? ? ? ? * contrib/aot-compile-rpm.in: Likewise.
> > > ? ? ? ? * contrib/classfile.py: Likewise.
> > > ? ? ? ? * contrib/rebuild-gcj-db.in: Likewise.
> > >
> > > This is also http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47484 .
> >
> > I'm on the hook to fix this, but it's been a while since I worked
> > on this stuff so I'm a little out of touch with GCC. ?Can you tell
> > me what you mean by "common namespace", and what the alternative
> > should be?
>
> 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,
Gary
--
http://gbenson.net/