[prev in list] [next in list] [prev in thread] [next in thread] 

List:       libusb-devel
Subject:    Re: [libusb] problem linking libusb-1.0
From:       Peter Stuge <peter () stuge ! se>
Date:       2014-05-09 22:28:01
Message-ID: 20140509222801.25812.qmail () stuge ! se
[Download RAW message or body]

Throstur Jonsson wrote:
> I managed to create a test program and compile/link/run it locally on
> my ARM.
> However when I want to cross-compile it for the same ARM-debian 
> platform, from my Linux-Mint platform, I run into a problem:
> 
> It compiles, but when linking I get.
> 
> Linking CXX executable temper1
> /usr/local/arm/cross-gcc-4.7.2-armv5te-soft/i686-pc-linux-gnu/arm-926ejs-linux-gnueabi/sys-root/lib/libusb-1.0.so: \
>  undefined reference to `clock_gettime@GLIBC_2.17'
> /tftpboot/rootfs/lib/arm-linux-gnueabi/libudev.so.1: undefined reference 
> to `secure_getenv@GLIBC_2.17'

This might be if you didn't build libusb also using the cross toolchain?

Try doing that, and if it works you don't need to move the libusb .so
files around, the application binary should work fine with either
libusb .so file.


//Peter

------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
&#149; 3 signs your SCM is hindering your productivity
&#149; Requirements for releasing software faster
&#149; Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
libusb-devel mailing list
libusb-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusb-devel


[prev in list] [next in list] [prev in thread] [next in thread]