This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: would a gcc by any other name still smell?
- To: kate at ahab dot rutgers dot edu
- Subject: Re: would a gcc by any other name still smell?
- From: Manfred dot Hollstein at ks dot sel dot alcatel dot de
- Date: Wed, 26 Nov 97 08:33:13 +0100
- Cc: egcs at cygnus dot com, rittle at comm dot mot dot com, tim at wagner dot princeton dot edu
- References: <199711251359.IAA28937@ahab.rutgers.edu>
- Reply-To: Manfred dot Hollstein at ks dot sel dot alcatel dot de
On Tue, 25 November 1997, 08:59:18, kate@ahab.rutgers.edu wrote:
> > Doing it is just as easy as having two FSF gcc versions around. On
> > our machines here, I have 2.7.2 as the default gcc, and if I want
> > egcs, I use 'gcc -V egcs-2.90.17'. works like a charm.
>
> Unfortunately, this solution does not work so great. The standard C++
> libraries are located at the exact same location on the file system
> for both compiler versions by default.
My problem is more with the C++ include files. If you leave the 2.7.2
ones lying around in /usr/local/lib/g++-include, they are found before
the egcs ones in /usr/local/include/g++. I have had to delete the old
ones or use a different --prefix for one of the versions. Any other
solutions?
Yes, see <http://www.cygnus.com/ml/egcs-bugs/1997-Oct/0197.html>.
--
Manfred Hollstein Alcatel, Dept. US/EC4
<mailto:Manfred.Hollstein@ks.sel.alcatel.de> Lorenzstrasse 10
70435 Stuttgart
Public PGP key on request Germany