This is the mail archive of the
libstdc++@sourceware.cygnus.com
mailing list for the libstdc++ project.
Re: Build help
- To: Donnie Hale <dhale@columbus.rr.com>
- Subject: Re: Build help
- From: Benjamin Kosnik <bkoz@cygnus.com>
- Date: Fri, 8 Jan 1999 13:44:18 -0800 (pst)
- cc: libstdc++-v3@cygnus.com
> - At present, a "which g++" shows it in /usr/bin
>
> First, I presume I should change my path to point to
> "/usr/local/egcs-devtools/egcs/bin" first?
If this is where your egcs compiler is installed, yes. Please do this.
Then, assuming g++ points to egcs, you should see something like:
% g++ --version
egcs-2.92.34
> Third, a line in the RELEASE-NOTES file is confusing me a little. After
> explaining that the environment variable CXX should be set to find my g++,
> the example is:
>
> CXX=g++ ../libstdc++-2.90.3/configure --prefix=${PWD%/*}/H-libstdc++
This just means that you are going to have a separate install directory
for your v3 library binaries and library headers. This is what the
--prefix configure option does (you'll find this works the same on egcs or
other things like gtk+ as well)
The goal is to install the headers and libs in a separate place, other
than /usr/include (RH headers) or whatever /usr/local/* your are using for
egcs. . . . so that you can have all three on your system at once.
> Fourth, once configured, built, and installed, what's the "recommended" way
> to make this version of the library the "live" one when working w/ the newer
> egcs (just the appropriate -I and -L flags?)?
yup, just use -I and -L
> Fifth, it seems that the standard C library "behind" this library is the one
> that's part of the newer egcs. Correct?
?
glibc is a different distro than egcs. I don't understand your question,
can you please provide more info?
-benjamin
- References:
- Build help
- From: "Donnie Hale" <dhale@columbus.rr.com>