Re: solaris 2.7 binutils problem

[Jeff Sturm]

On Thu, 20 Sep 2001, Phil Edwards wrote:
> Problem #2:  What you're seeing is what happens when GCC has been configured
> to use one kind of "binutils" (e.g., the native Solaris kind), but the other
> kind (e.g., GNU's) is actually found.  If you plan on using GNU binutils,
> then you must configure GCC using the appropriate --with options.

Regardless, configuring without arguments should build a usable compiler.

The rules to build libgcc_s.so are chosen during configure, which always
chooses solaris ld unless --with-ld or --with-gnu-ld are given.
However the gcc driver first checks in ${prefix} for binutils.  If found,
the build fails on SHLIB_LINK.

This problem may probably worsen as more target-specific t-slibgcc-*
rules appear.  Perhaps it would be better if libgcc_s were configured
after the stage1 compiler is built so the correct ld could easily be
determined.  (For that matter, libtool could replace much of the
t-slibgcc-* mess if this were so.)

The workaround is to always specify --with-ld and/or --with-gnu-ld when
configuring on solaris.

Jeff