Always link against static libgcc on hppa-linux

[John David Anglin]

> running executable: the main application, all shared libraries, and all
> dynamically loaded shared objects.  When we link against both shared and
> static libraries, we run the risk of having multiple copies of the EH
> routines.  We especially do not want some parts of a running executable to
> use tightly-bound versions of the routines distinct from other parts of
> the executable.

The EH routines are not in libgcc.a.  They are in libgcc_eh.a and it
isn't included when using "-shared" or "-shared-libgcc".

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