Re: libtool doesn't hardcode libg2c when linking with g77

[Albert Chin]

On Thu, Aug 15, 2002 at 07:39:35PM -0400, John David Anglin wrote:
> I observed this while testing a patch for 64-bit hpux:
> 
> === Running f77demo-make.test
> Making in ../f77demo
> make[3]: Entering directory `/xxx/gnu/libtool-1.4e/objdir64/f77demo'
> ...
> g77  -O2 -c /xxx/gnu/libtool-1.4e/tests/../f77demo/fprogram.f
> /bin/sh ./libtool --mode=link g77  -O2  -o fprogram  fprogram.o libfoo.la 
> g77 -O2 -o fprogram fprogram.o  ./.libs/libfoo.a
> ...
> === Running f77demo-exec.test
> Executing uninstalled programs in ../f77demo
> /usr/lib/pa20_64/dld.sl: Unable to find library 'libg2c.sl.0'.
> 
> # chatr fprogram
> fprogram:
>          64-bit ELF executable
>        shared library dynamic path search:
>            LD_LIBRARY_PATH    enabled  first 
>            SHLIB_PATH         enabled  second
>            embedded path      enabled  third  Not Defined
>        shared library list:
>            libg2c.sl.0
>            libm.2
>            libc.2
> 
> libg2c.sl.0 is not installed in a directory that the dynamic loader
> automatically searches.  If LD_LIBRARY_PATH is appropriately defined,
> then the program executes correctly.  However, I think libtool should
> have hardcoded the patch for libg2c.sl.0.  If I manually add
> "-Wl,-rpath,/opt/gnu64/lib" to the link command, then the path
> gets added to the embedded path list and the program will execute
> without having to set LD_LIBRARY_PATH.

What does libg2c.la look like?

-- 
albert chin (address@hidden)