Always link against static libgcc on hppa-linux

[John David Anglin]

>         * gcc.c (init_gcc_specs): Add static libgcc to link when "-shared"
>         is specified.
> 
> No, this is not okay!
> 
> Richard, you have again approved a patch which breaks AIX.
> 
> John, you just reverted a previously approved and applied fix without
> proper investigation.  You obviously did not investigate the impact of
> your patch sufficiently before proposing it.  See
> 
> http://gcc.gnu.org/ml/gcc-patches/2001-12/msg02414.html
> 
> John's patch must be reverted.

Did you investigate what you broke when you proposed your patch?  You
also didn't update the documentation in invoke.texi to reflect your
change.  You forget in the above message that some targets require
functions other than _eprintf and __gcc_bcmp from libgcc.a.  You can't
build a shared library at all on hppa-linux without linking against a
static libgcc.a.  The static library is needed to resolve millicode
references.  You will still have the same problem if you link with
shared-libgcc.

Frankly, from the description you provide for the problem in the above
message, it looks as if collect needs to be fixed to prevent it adding
the frame information from DIVMOD in libgcc.a when a shared libgcc
is being used as well.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6605)