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

[Albert Chin]

On Fri, Aug 16, 2002 at 03:25:18PM -0400, John David Anglin wrote:
> > > Is this really libtool's job though? Not even the system linker
> > > would handle this.
> > 
> > I'm not entirely sure.  I brought it up because libtool hardcodes
> > paths for libraries that are explicitly specified.  So, why not
> > hardcode all the shared libraries used in a link?
> 
> Here is an easier wat to get the correct result.  Of course, this
> just applies to "gcc":
> 
> # ./libtool --mode=link g77 -o main main.o `g77 -print-file-name=libg2c.la`
> g77 -o main main.o  /opt/gnu64/lib/libg2c.sl -lm -Wl,--rpath 
> -Wl,/opt/gnu64/lib -Wl,--rpath -Wl,/opt/gnu64/lib

This works because you pass libg2c.la to libtool. If the -L, -l, or
.la file is not on the command-line to libtool, how is it suppose to
find the library?

-- 
albert chin (address@hidden)