Re: Always link against static libgcc on hppa-linux

[Bryce McKinlay <bryce at waitaki dot otago dot ac dot nz>]

John David Anglin wrote:

>>  4. Now, we have a shared libgcc.  On most platforms, one wants to
>>     link with either the static libgcc, or the shared version, but
>>     not both -- that can cause a variety of known EH problems, one
>>     of which David seems to have (re)discovered.  However, on
>>     hppa-linux, if we don't link with the static libgcc, we are
>>     missing the critical support routines.
>>
>
>There currently are problems with unwinding on hppa-linux which I
>haven't been able to resolve yet.  Just getting the frame note code
>working, is new.  I thought that most of the EH issues were resolved
>when the routines got reorganized for gcc-3.  I know previously that
>there were problems with a shared libstdc++ under hpux due to
>duplication of routines.  If this is still a real problem, then I
>think a separate libmilli.a would be the best bet.  I don't know
>enough about the gnu linker to have an informed opinion on the matter.
>

libgcc should ideally always be a shared library when EH might be used. 
If it isn't, then the possibility of having different, incompatible 
versions of the EH runtime (in different shared libraries) exists.

regards

Bryce.