From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] cross-compiling btsco
Date: Sat, 21 Jan 2006 01:13:14 -0700 [thread overview]
Message-ID: <43D1ED1A.1090400@xmission.com> (raw)
Marcel,
I'm trying to straightening out fixed-point using a gumstix board to
test stuff. I used to be able to cross-compile btsco for gumstix but
something changed. Now during the link libtool translates "-lbluetooth"
into /usr/lib/libbluetooth.so instead of the arm libbluetooth.so inside
the cross-compile tree. I've tried overriding this in the configure and
make statements with just about everything I can think of.
Is there something our sources are missing for enabling a cross-compile?
Brad
make[3]: Entering directory
`/home/bmidgley/buildroot-2.6.14/build_arm_nofpu/btsco/sbc'
/bin/sh ../libtool --mode=link
/home/bmidgley/buildroot-2.6.14/build_arm_nofpu/staging_dir/bin/arm-linux-uclibc-gcc
-DUSE_FIXED
-I/home/bmidgley/buildroot-2.6.14/build_arm_nofpu/staging_dir/include
-DFORCE_LITTLE -Os -march=armv5te -mtune=xscale -Wa,-mcpu=xscale -o
sbcinfo sbcinfo.o -lbluetooth
/home/bmidgley/buildroot-2.6.14/build_arm_nofpu/staging_dir/bin/arm-linux-uclibc-gcc
-DUSE_FIXED
-I/home/bmidgley/buildroot-2.6.14/build_arm_nofpu/staging_dir/include
-DFORCE_LITTLE -Os -march=armv5te -mtune=xscale -Wa,-mcpu=xscale -o
sbcinfo sbcinfo.o /usr/lib/libbluetooth.so
/usr/lib/libbluetooth.so: could not read symbols: File in wrong format
collect2: ld returned 1 exit status
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
reply other threads:[~2006-01-21 8:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=43D1ED1A.1090400@xmission.com \
--to=bmidgley@xmission.com \
--cc=bluez-devel@lists.sourceforge.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;
as well as URLs for NNTP newsgroup(s).