[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: libtool doesn't hardcode libg2c when linking with g77
From: |
John David Anglin |
Subject: |
Re: libtool doesn't hardcode libg2c when linking with g77 |
Date: |
Fri, 16 Aug 2002 15:25:18 -0400 (EDT) |
> > 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
Dave
--
J. David Anglin address@hidden
National Research Council of Canada (613) 990-0752 (FAX: 952-6605)
RE: libtool doesn't hardcode libg2c when linking with g77, Boehne, Robert, 2002/08/21
Re: libtool doesn't hardcode libg2c when linking with g77, John David Anglin, 2002/08/21
RE: libtool doesn't hardcode libg2c when linking with g77, Boehne, Robert, 2002/08/22