[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Cannot link correct libltdl.so. Is it a bug?
From: |
Mike Frysinger |
Subject: |
Re: Cannot link correct libltdl.so. Is it a bug? |
Date: |
Fri, 9 Jan 2009 01:20:26 -0500 |
User-agent: |
KMail/1.10.3 (Linux/2.6.28; KDE/4.1.3; x86_64; ; ) |
first off, dont spam every e-mail address you can find.
On Thursday 08 January 2009 17:50:20 Gary Yang wrote:
> ./configure runs successfully with the following warnings
the warnings are from a deficiency in your setup, not bugs in autotools. you
need to provide cross-compiler prefixed scripts.
> make errors:
> /bin/sh ../libtool --tag=CC --mode=link powerpc-linux-gcc -g -O2 -g -O2
> -no-undefined -export-symbols ./libgphoto2_port.sym -version-info 8:0:8
> -L/tools/eldk/4.2/ppc_4xx/usr/lib -o libgphoto2_port.la -rpath
> /tmp/safebox/install_libs/lib libgphoto2_port_la-gphoto2-port-info-list.lo
> libgphoto2_port_la-gphoto2-port-log.lo
> libgphoto2_port_la-gphoto2-port-version.lo
> libgphoto2_port_la-gphoto2-port.lo
> libgphoto2_port_la-gphoto2-port-portability.lo
> libgphoto2_port_la-gphoto2-port-result.lo -lltdl echo "{ global:" >
> .libs/libgphoto2_port.ver
> cat ./libgphoto2_port.sym | sed -e "s/\(.*\)/\1;/" >>
> .libs/libgphoto2_port.ver echo "local: *; };" >> .libs/libgphoto2_port.ver
> powerpc-linux-gcc -shared
> .libs/libgphoto2_port_la-gphoto2-port-info-list.o
> .libs/libgphoto2_port_la-gphoto2-port-log.o
> .libs/libgphoto2_port_la-gphoto2-port-version.o
> .libs/libgphoto2_port_la-gphoto2-port.o
> .libs/libgphoto2_port_la-gphoto2-port-portability.o
> .libs/libgphoto2_port_la-gphoto2-port-result.o
> -L/tools/eldk/4.2/ppc_4xx/usr/lib /usr/lib/libltdl.so -Wl,-soname
> -Wl,libgphoto2_port.so.0 -Wl,-version-script -Wl,.libs/libgphoto2_port.ver
> -o .libs/libgphoto2_port.so.0.8.0 /usr/lib/libltdl.so: could not read
> symbols: File in wrong format
> collect2: ld returned 1 exit status
> make[4]: *** [libgphoto2_port.la] Error 1
either due to your previous warnings where you didnt setup build env fully
enough, or the package itself sucks and uses -L paths. or you're hitting a
bug in libtool having to do with relinking. use a --prefix pointing to your
development root to workaround the issue.
if you have cross-compiling questions, you should really ask them on an
embedded mailing list. like the one for eldk.
-mike
signature.asc
Description: This is a digitally signed message part.