Building libgcc_s.so seperately

[Florian Bachmann]

Hi,

I am thinking of upgrading my Linux system from GCC 2.95.3 to GCC 3.1, but I 
don't like the idea of fundamental things like glibc depending on yet another 
shared library - namely, libgcc_s. So I was thinking of forcing GCC 3.1 to 
use a static libgcc with a configure script option like this one:

	--enable-shared=libstdc++,libjava,libffi

Now I wonder if there is a way of bootstrapping GCC with the above option, and 
afterwards building a shared libgcc_s for compatibility with foreign RPM 
packages and such that might require it.

Regards

-- 
Florian Bachmann <f_bachmann@t-online.de>