libtool
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: fixing linkage against uninstalled libtool archives on macos?


From: Ralf Wildenhues
Subject: Re: fixing linkage against uninstalled libtool archives on macos?
Date: Thu, 13 Nov 2008 21:46:59 +0100
User-agent: Mutt/1.5.18 (2008-05-17)

* Andy Wingo wrote on Thu, Nov 13, 2008 at 11:41:15AM CET:
> >> >
> >> >>    http://lists.gnu.org/archive/html/bug-libtool/2008-11/msg00012.html
> >> >>
> >> >> Just to recap, the bug is that having
> >> >> "../../../gst/libgstreamer-0.10.la" on the link line expands into
> >> >> "-L../../../gst/.libs -lgstreamer-0.10" instead of
> >> >> "../../../gst/.libs/libgstreamer-0.10.dylib". I tested replacing the
> >> >> "-L -l" combination with the path to the dylib, and that seems to
> >> >> work.

> But the badness is still there, of course, on line 6985, column 466:
> 
>    -L/opt/yobuild/lib -L../../../gst/.libs -lgstreamer-0.10

This shouldn't happen on darwin.

Here is where it happens the first time in your trace:

> + test -n ''
> + test lib = prog
> + test link '!=' relink
> + add_shlibpath=
> + add_dir=
> + add=
> + lib_linked=yes
> + case $hardcode_action in
> + test yes = no                       (*)
> + test no = no
> + case $host in
> + add_dir=-L../../../gst/.libs
> + add=-lgstreamer-0.10
> + test yes '!=' yes
> + test -n ''
> + test lib = prog
> + test -n -L../../../gst/.libs
> + deplibs='-L../../../gst/.libs -L/opt/yobuild/lib '
> + test -n -lgstreamer-0.10
> + deplibs='-lgstreamer-0.10 -L../../../gst/.libs -L/opt/yobuild/lib '
> + test yes '!=' yes

In ltmain.m4sh, search for 'case $hardcode_action in' to find the place
corresponding to the trace.

Everthing looks ok except for the trace line right after the case
statement (marked with (*)).  It corresponds to
              if test "$hardcode_direct" = no; then

What I don't understand is: your --config output had
| hardcode_direct=no

so something set this to "yes" in the meantime.  That bit is wrong.

Any chance the package you are building is using a patched ltmain.sh
file?

Cheers,
Ralf




reply via email to

[Prev in Thread] Current Thread [Next in Thread]