On 03/09/2011 09:47 AM, Wu, Ruiyu (GE Healthcare) wrote:
> make[1]: Entering directory `/home/wry/sysapps/libftdi-0.18'
> Making all in src
> make[2]: 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 -o libftdi.la -rpath
> /home/yang2000/211backup/yang2000/Develop/target_dvevm/usr/lib ftdi.lo -lusb
> libtool: link: arm_v5t_le-gcc -shared .libs/ftdi.o /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
> make[2]: *** [libftdi.la] Error 1
> make[2]: Leaving directory `/home/wry/sysapps/libftdi-0.18/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/wry/sys
>
> Could anybody tell me why file in wrong format?
Seems that your cross-compilation is trying to link libusb from host PC.
Cross-compile libusb for arm and link with that.
BR,
Teemu
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
|
