Re: hppa*64* and dependent libraries

[John David Anglin]

> I agree that we should use +b to embed the path. Is everyone else in
> agreement?

What about the alternative "-L" and "-l" approach which ia64 uses and
I adopted in my original patch?  I tried to stay away from using "+b".
Maybe I am missing something but the package which I have built seem
to have a reasonable embedded path.  For example,

/bin/sh ./libtool --mode=link gcc -W -Wall -Wstrict-prototypes 
-Wmissing-prototypes -O2  -o ld-new  ldgram.o ldlex.o lexsup.o ldlang.o mri.o 
ldctor.o ldmain.o ldwrite.o ldexp.o ldemul.o ldver.o ldmisc.o ldfile.o ldcref.o 
eelf64hppa.o  ../bfd/libbfd.la ../libiberty/libiberty.a  
mkdir .libs
gcc -W -Wall -Wstrict-prototypes -Wmissing-prototypes -O2 -o .libs/ld-new 
ldgram.o ldlex.o lexsup.o ldlang.o mri.o ldctor.o ldmain.o ldwrite.o ldexp.o 
ldemul.o ldver.o ldmisc.o ldfile.o ldcref.o eelf64hppa.o  
../bfd/.libs/libbfd.sl ../libiberty/libiberty.a -L/opt/gnu64/lib

The installed version of ld has the embedded path

        shared library dynamic path search:
            LD_LIBRARY_PATH    enabled  first 
            SHLIB_PATH         enabled  second
            embedded path      enabled  third  
/opt/gnu64/lib:/opt/gnu64/lib/gcc-lib/hppa64-hp-hpux11.00/3.3:/opt/gnu64/lib/gcc-lib/hppa64-hp-hpux11.00/3.3/../../../../hppa64-hp-hpux11.00/lib:/usr/ccs/bin:/usr/ccs/lib/pa20_64:/opt/langtools/lib/pa20_64:/opt/gnu64/lib/gcc-lib/hppa64-hp-hpux11.00/3.3/../../..
        shared library list:
            libbfd-2.13.90.sl
            libc.2

The important addition by libtool is "-L/opt/gnu64/lib" to the gcc link
command.  This comes because ../bfd/.libs/libbfd.sl has the embedded
path /opt/gnu64/lib.  It has this because the libtool command to build
it had "-rpath /opt/gnu64/lib".  It is true that the embedded path doesn't
contain a path to libbfd.sl in its build location but I don't think
you want that unless that's its final location.  The testsuite scripts
use LD_LIBRARY_PATH to modify the search path when you want to test the
library in its build location prior to install.  This all seems reasonable
to me.

This was generated using my original libtool patch for binutils.

Dave
-- 
J. David Anglin                                  address@hidden
National Research Council of Canada              (613) 990-0752 (FAX: 952-6605)