Re: Special names tha ld needs to recognize for hppa64-hp-hpux11.X

[law at redhat dot com]

In message <200201221906.g0MJ6QN5015867@hiauly1.hia.nrc.ca>, "John David Anglin
" writes:
 > In looking at the gcc testresults for hppa64-hp-hpux11.00, I noticed that
 > there is a problem with linking using binutils ld when "-static" was
 > specified.  You get the following error:
[ ... ]
Also note the set of symbols that are special changes based on what patches
from HP you have installed :(  The set that we handle is based on a
1999 hpux11.00 release and haven't been significantly updated over time.

Furthermore, some of the symbols have specific meanings which we don't
implement (like the TLS symbols for thread-local storage).


 > Does anyone have any suggestions on how to best handle the definition
 > of these special symbols in ld?  I am guessing that "_end" and related
 > symbols must already be handled because that's pretty standard.
I'd been defining them in the PA64 specific linker emulation script
(elf64hppa.sh).  It's likely further changes to those files will be
needed over time to bring the PA64 GNU tools closer to conformance with
the behavior of HP's tools.

I do know when I did the initial development that static linking worked --
because that's what we relied upon in the early development before we 
actually supported shared libraries.

Note that static linking still produces a "dynamic" binary for PA64.  Fun
fun.


jeff