On 03/09/2011 10:41 AM, Wu, Ruiyu (GE Healthcare) wrote:
>
> I have use the LDFLAGS
>
> ./configure
> CC=arm_v5t_le-gcc
>
> --prefix=/usr/local/opt/mv_pro_4.0_1.20/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/target/
> --exec-prefix=/usr/local/opt/mv_pro_4.0_1.20/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/target/
> LDFLAGS=-L/usr/local/opt/mv_pro_4.0_1.20/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/target/usr/lib
> --host=arm-linux
>
> but still get the same error:(.
>
> Entering directory `/home/wry/sysapps/libftdi-0.18/src'
> /bin/sh ../libtool --tag=CC --mode=link arm_v5t_le-gcc -g -O2
> -version-info 19:0:18
> -L/usr/local/opt/mv_pro_4.0_1.20/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/target/usr/lib
> -o libftdi.la -rpath
> /usr/local/opt/mv_pro_4.0_1.20/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/target/lib
> ftdi.lo -lusb
> libtool: link: arm_v5t_le-gcc -shared .libs/ftdi.o
> -L/usr/local/opt/mv_pro_4.0_1.20/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/target/usr/lib
> /usr/lib/libusb.so -Wl,-soname -Wl,libftdi.so.1 -o .libs/libftdi.so.1.18.0
> /usr/lib/libusb.so: could not read symbols: File in wrong format
> collect2: ld returned 1 exit status
Hi,
maybe you could try to temporarily rename your /usr/lib/libusb.so to see
if that library is really tried to be linked. Is your prebuilt libusb
library built using the same toolchain you are using for cross-compilation?
--
Teemu
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
|
