Re: [PATCH] Support gcc-3.4 and greater under Solaris 2.5 without pdump
On Wed, 23 Mar 2005 10:59:31 -0500, Vin Shelton <ethersoft(a)gmail.com> wrote:
On Wed, 23 Mar 2005 16:44:54 +0100, Hrvoje Niksic
<hniksic(a)xemacs.org> wrote:
> Vin Shelton <ethersoft(a)gmail.com> writes:
> > I actually am a little surprised that configure attempts to force
> > the system linker, because: 1) the PROBLEMS file calls out this very
> > issue and 2) I'm pretty sure we recently received an email where the
> > user was attempting to build on Solaris with the GNU linker.
>
> It seems reasonable for configure to force the system linker if it's
> known that the GNU one doesn't work, and when the system one is always
> available (unlike Sun's cc, the linker ships with Solaris). Why do
> you find it surprising?
Primarily because of my reason #2. We get occasional build errors on
Solaris that trace back to trying to build with binutils. I agree
that it's good to avoid the binutils on Solaris since they don't work.
I still haven't found if there's an easy way to force the new system
linker on gcc 3.4.0 and above. I found the change that removed the
option from gcc, but I haven't found the rationale.
OK, I have now found out that the -fgnu-linker option never worked.
See http://gcc.gnu.org/ml/gcc-patches/2003-12/msg00068.html for
details. In particular, Zack Weinberg wrote:
The -fgnu-linker option has had no effect in the entire history of the
CVS repository, except for a few days in 2001 when iris6.h used it.
Note that this is consistent with my observation #2 above - we still
see build failures where people are trying to use GNU binutils on
Solaris. My new plan is to remove the entire -fno-gnu-linker support
from configure. Comments?
- Vin