[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 10:53:10 -0500 |
User-agent: |
Mutt/1.2.5i |
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
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?
--
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