public inbox for
 help / color / mirror / Atom feed
From: Gerald Pfeifer <>
To: Gary Benson <>
Cc: Richard Guenther <>,
	    Tom Tromey <>,,
Subject: Re: Another Python namespace pollution (was: r147958 - in /trunk/libstdc++-v3: ChangeLog Mak...)
Date: Thu, 27 Jan 2011 19:54:00 -0000	[thread overview]
Message-ID: <alpine.LNX.2.00.1101272052540.7158@gerinyyl.fvgr> (raw)
In-Reply-To: <>

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.


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/       <--- The good
  ./share/python/                          <--- The bad
  ./lib/                          <--- The ugly :-)

  reply	other threads:[~2011-01-27 19:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
     [not found] ` <>
     [not found]   ` <>
     [not found]     ` <>
     [not found]       ` <>
     [not found]         ` <>
2011-01-27  1:48           ` Gerald Pfeifer
2011-01-27 10:38             ` Gary Benson
2011-01-27 10:43               ` Richard Guenther
2011-01-27 11:00                 ` Gary Benson
2011-01-27 19:54                   ` Gerald Pfeifer [this message]
2011-01-27 23:59                     ` Another Python namespace pollution Matthias Klose
2011-02-02 15:00                   ` Another Python namespace pollution (was: r147958 - in /trunk/libstdc++-v3: ChangeLog Mak...) Gary Benson
2011-02-18 14:21                     ` Gerald Pfeifer
2011-02-18 14:32                       ` Another Python namespace pollution Andrew Haley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LNX.2.00.1101272052540.7158@gerinyyl.fvgr \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).