Build help

["Donnie Hale" <dhale@columbus.rr.com>]

This is my first message to the mailing list. If I'm not following proper
etiquette, please let me know.

I'm hoping that I can get involved in the effort on this library. It's taken
a while, but thus far I've finally gotten egcs-1.1.1 built; and I have the
2.90.3 snapshot untarred.

My environment:
- RH Linux 5.1 on an AMD K6-2/266
- the "dev root" of this stuff is "/usr/local/egcs-devtools"
- the egcs install is in a directory called "egcs" under the dev root
- the snapshot is in libstdc++-2.90.3 under the dev root
- 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?

Second, other than what's in RELEASE-NOTES, are there any other
environmental changes that need made to ensure that I'm using the
appropriate egcs?

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 looks to me like two lines have been merged; i.e. the part beginning
"../libstdc++-2.90.3/configure" is a command that should be run. So, in ksh,
should this instead be:

export CXX=g++
../libstdc++-2.90.3/configure --prefix=/usr/local/egcs-devtools/H-libstdc++

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?)?

Fifth, it seems that the standard C library "behind" this library is the one
that's part of the newer egcs. Correct?

Finally, any other hints?

Many thanks in advance for the help. FWIW, I'd like to work on the
thread-safety side of things if that's still needed. We'll see how my
availability holds out and how quickly I can get up to speed.

Take care,

Donnie Hale
dhale@columbus.rr.com