Re: [PATCH] Support gcc-3.4 and greater under Solaris 2.5 without pdump
Vin Shelton <ethersoft(a)gmail.com> writes:
Aside - I don't understand why the option was removed.
Maybe they changed the default to use the system linker. Maybe
there's now another (better?) way to specify the linker to use.
`-fno-gnu-linker' always seemed awkward to me.
(AFAIK this is an issue only because because Sun bundled GCC and
binutils together on their freeware CD's. Omitting binutils would
have resulted in GCC happily using the system linker. The minority
who *wanted* the GNU linker in production would know how to get it.)
Apparently, gcc uses the system linker. I must admit that I
don't
have binutils installed here, so gcc doesn't have a choice. Your
implicit suggestion here is that the effect is still required.
The suggestion was implicit because I don't know for sure. However,
that's what the comment said and still says after your patch. Unless
Dynodump was changed to accomodate GNU ld or the behavior of GNU ld
under Solaris has changed to comply with Dynodump requirements --
either of which is highly unlikely -- the comment can be assumed to
stand.
I'll take the hint and see if there's a new option to use
instead.
Thanks.
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?
Thanks for the review, Malcolm and Hrvoje!
No problem -- it's the least I can do.