Re: libstdc++.a in gcc-lib?

[dave madden <dhm at paradigm dot webvision dot com>]

 =>From: Marco Manfai Yu <yumf@ultimatech.com>
 =>...
 =>    I am upgrading my compiler from 1.0.3a to 1.1. In the mean time
 =>I need to compile my code using both compilers from time to time.
 =>This causes a problem: both compilers have their own libstdc++ and
 =>they are not compatible. The default installation installs libstdc++.a
 =>into /usr/local/lib, which overwrites the old one. My question is:
 =>is it a better idea to move libstdc++ into gcc-lib/<version> like
 =>libgcc.a? Seems to me that the compiler depends on the library to
 =>provide certain functions (such as EH) so libstdc++ is
 =>compiler-specific anyway.
 =>
 =>Comments?

If you need to run multiple versions of gcc or egcs, the simplest way
to do it is to install them in completely separate trees.  You can
cause this to happen with the "--prefix=/some/special/directory"
argument to configure.  I always install large packages like gcc,
egcs, emacs, gdb, and perl into directories like:

	/usr/local/packages/egcs-1.1b

Then I symlink the binaries for the version I want to use by default
into /usr/local/bin:

	ln -s /usr/local/packages/egcs-1.1b/bin/gcc /usr/local/bin/egcs
	ln -s /usr/local/packages/egcs-1.1b/bin/g++ /usr/local/bin/egcs++

This way, the libraries and support files for a specific version live
in a place where no other version will accidentally find them, and I
can remove all the parts of an old version without having to spelunk
through common directories looking for pieces of a package whose names
I don't even know.

d.