[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: |
Albert Chin |
Subject: |
Re: libtool doesn't hardcode libg2c when linking with g77 |
Date: |
Fri, 16 Aug 2002 12:51:14 -0500 |
User-agent: |
Mutt/1.2.5i |
On Fri, Aug 16, 2002 at 01:42:47PM -0400, John David Anglin wrote:
> > > 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
> >
> > Ok, looked at this again. Does libtool add the -rpath entry correctly
> > when building C++ programs? I don't think so. Based on the input file
> > above, how can it tell the correct path of where libg2c.sl is located?
>
> I linked a simple C++ program with libtool. It doesn't add the
> -rpath for libstdc++.sl.4 :-(
>
> Regarding how libtool can tell the correct path for libg2c, libstdc++,
> etc., I think the best way is to link a simple test program. For example,
>
> [skipped]
>
> The autoconf macro, AC_F77_LIBRARY_LDFLAGS, provides an example of how to
> parse the above output. If you look at the Makefile in f77demo, you will
> see a FLIBS define. This is set using AC_F77_LIBRARY_LDFLAGS to
Is this really libtool's job though? Not even the system linker
would handle this.
--
albert chin (address@hidden)
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