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

[law at redhat dot com]

 In message <200202082242.g18Mg0MU005514@hiauly1.hia.nrc.ca>, "John David 
Anglin
" writes:
 > I have looked a bit more into this problem and it appears more difficult
 > to solve than first thought.  We can't just provide these symbols because
 > they are provided by the dynamic loader.  Because static linking still
 > produces a "dynamic" binary, we need to allow undefined dynamic-loader
 > absolute symbols in static links.  This is what the HP linker does.
 > If we produced a true static binary, the linker would have to provide
 > these symbols.
Since we always create a dynamic binary it should be OK to leave the symbols
undefined -- as long as the dynamic linker defines them for us.

Hell, with that I wonder if defining the various magic symbols in the linker
script like I did was the right thing to do for those older symbols.


 > It looks like elf-hppa.h needs to be hacked but I have the sense that
 > the generic elf code may not like undefined symbols from archive libraries.
It should be OK to have an undefined symbol from an archive library,
shared library or dynamic executable (as long as the symbol is never used or
somehow defined at runtime).

jeff