bug-libtool
[Top][All Lists]
Advanced

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

Re: libtool-1.5.14 static vs shared bug (gettext-0.14.2 fails make check


From: Ralf Wildenhues
Subject: Re: libtool-1.5.14 static vs shared bug (gettext-0.14.2 fails make check) ?
Date: Mon, 14 Mar 2005 14:24:29 +0100
User-agent: Mutt/1.4.1i

Hi Mike,

* Mike Frysinger wrote on Sun, Mar 13, 2005 at 05:17:38AM CET:
> 
> in gettext-0.14.2 (libtool-1.5.14), rpathz's make.log lacks such a warning 
> and 
> in fact tries to link librpathz.so with librpathy.a which obviously fails on 
> amd64 (.a is built w/out PIC and .so's cannot be linked with non-PIC 
> objects):
> 
> gcc -shared  .libs/rpathz.o 
> -Wl,--whole-archive 
> /home/vapier/gettext-0.14.2/autoconf-lib-link/tests/rp3aaf-prefix/lib/librpathy.a
>  
> -Wl,--no-whole-archive  -Wl,--rpath 
> -Wl,/home/vapier/gettext-0.14.2/autoconf-lib-link/tests/rp3aaf-prefix/lib 
> -Wl,--rpath 
> -Wl,/home/vapier/gettext-0.14.2/autoconf-lib-link/tests/rp3aaf-prefix/lib 
> -L/home/vapier/gettext-0.14.2/autoconf-lib-link/tests/rp3aaf-prefix/lib 
> /home/vapier/gettext-0.14.2/autoconf-lib-link/tests/rp3aaf-prefix/lib/librpathx.so
>  
> -lc  -Wl,-soname -Wl,librpathz.so.0 -o .libs/librpathz.so.0.0.0
> /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3-20050110/../../../../x86_64-pc-linux-gnu/bin/ld:
>  
> /home/vapier/gettext-0.14.2/autoconf-lib-link/tests/rp3aaf-prefix/lib/librpathy.a(rpathy.o):
>  
> relocation R_X86_64_PC32 against `rpathx_value' can not be used when making a 
> shared object; recompile with -fPIC
> /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3-20050110/../../../../x86_64-pc-linux-gnu/bin/ld:
>  
> final link failed: Bad value
> collect2: ld returned 1 exit status
*snip*
> comments/thoughts/etc... ?

Yes.  You also have been hit by the bug that libtool has
  deplibs_check_method=pass_all
for linux, which is plain wrong (but feels comfortable most of the
time).

Let's slap everyone that voted for this change back in libtool-1.5.1.

Adding it to the TODO list since it's not trivial to solve, and might
need some discussion.

Regards,
Ralf




reply via email to

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