From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Problem building package usbutils under buildroot-2011.11
Date: Sun, 4 Dec 2011 21:49:39 +0100 [thread overview]
Message-ID: <20111204214939.29b10ebe@skate> (raw)
In-Reply-To: <1323013713.2865.9.camel@ceri>
Le Sun, 04 Dec 2011 15:48:33 +0000,
Mike Davies <busybox_mail@rovoreed.com> a ?crit :
> /bin/sh ../libtool --tag=CC --mode=link /home/mike/br/output/host/usr/bin/x86_64-unknown-linux-uclibc-gcc -Os -Wall -Os -fPIC -DPIC -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -o usbhid-dump usbhid-dump.o ../lib/libusbhid_dump.la -lusb-1.0
> libtool: link: /home/mike/br/output/host/usr/bin/x86_64-unknown-linux-uclibc-gcc -Os -Wall -Os -fPIC -DPIC -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -o usbhid-dump usbhid-dump.o ../lib/.libs/libusbhid_dump.a /usr/local/lib/libusb-1.0.so -lrt -pthread -Wl,-rpath -Wl,/usr/local/lib -Wl,-rpath -Wl,/usr/local/lib
Here it's linking against /usr/local/lib/libusb-1.0.so and not the
libusb that has been built by Buildroot against uClibc and installed in
$(STAGING_DIR). A quick, but very ugly, workaround is to uninstall
libusb-dev from your development machine. But we need to find why
usbutils is preferring the host libusb instead of the one built by
Buildroot.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-12-04 20:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-04 15:48 [Buildroot] Problem building package usbutils under buildroot-2011.11 Mike Davies
2011-12-04 20:49 ` Thomas Petazzoni [this message]
2011-12-05 12:22 ` Mike Davies
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111204214939.29b10ebe@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox