Re: --enable-namespaces, -fhonor-std and libgcc.a

["Martin v. Loewis" <martin at loewis dot home dot cs dot tu-berlin dot de>]

> 1) Does gcc-2.95.2 have to be built with say
> 'CFLAGS=-fhonor-std CXXFLAGS=-fhonor-std'
> to obtain a valid libgcc.a, that will work with
> the std namespace in libstdc++-2.90.7?

There is a number of alternatives. I believe setting CXXFLAGS should
be sufficient. Personally, I always change cp/decl2.c:flag_honor_std
before building the compiler. Of course, such a compiler would not
work as a standard installation, unless you then pass -fno-honor-std
all the time.

> If so, what is the correct place to introduce these
> flags in the build process, i.e., as I usually
> do a make bootstrap, when do I interrupt this and
> tell it to build a std-namespace compatible libgcc.a.

Doing 

make bootstrap CXXFLAGS='-g -O2 -fhonor-std'

should be sufficient (again, untested) - CXXFLAGS should be passed
through the entire build process.

> 2) If I have a gcc 2.95 that was built with no use of
> -fhonor-std is it possible to just rebuild a std-compliant
> libgcc.a (without rebuilding the whole kaboodle). I still
> have my build tree available.

Yes. Just remove libgcc2.ready, libgcc.a, libgcc2.a, and 'make
libgcc.a CXXFLAGS=-fhonor-std' inside the gcc subdirectory.

You may want to watch the build process to see whether it does the
right thing.

Regards,
Martin