Can't find libgcc after building 1.4.1

[Russ Allbery]

"Douglas E Engert" <deengert at anl.gov> writes:

> Another way around this is to use the static version of libgcc.

> This can be done by default by changing the specs file for example:

>  ./lib/gcc-lib/sparc-sun-solaris2.9/3.3.2/specs

> The patch makes the static version the default. You can still
> use the dynamic version if needed. We have done this for years
> with Kerberos, OpenSSL and OpenSSH without problems.

> http://www.mail-archive.com/openssl-dev@openssl.org/msg16145.html

> Gcc-3.1 introduced -shared-libgcc and -static-libgcc
> But when building shared libs, it wants to include the
> libgcc_s shared version, even when not needed by default.
> This causes problems when trying to build shared libs,
> as they will need the extra libgcc_s.so.n.n when it really
> is not needed.

Note that if you link the resulting Kerberos library produced after
applying this patch into a C++ program, you will may be unhappy.  The
reason why gcc wants to use the shared libgcc_s for shared libraries is
that if you don't have a single instance of the exception handling state
in the resulting executable image after dynamic linking, throwing and
catching exceptions runs into problems.

You may not have any C++ programs where you would care.

-- 
Russ Allbery (rra at stanford.edu)             <http://www.eyrie.org/~eagle/>