From: Stephan Henningsen <sth@amplex.dk>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Trouble compiling BlueZ-utils in buildroot environment
Date: Wed, 16 Mar 2005 16:23:59 +0100 [thread overview]
Message-ID: <42384F8F.8030402@amplex.dk> (raw)
Hello World,
I'm trying to include bluez-libs and blues-utils buildroot
environment. I did this by making two seperate packages named
bluez-libs and bluez-utils, and a set of buildroot style
configuration files: bluez-libs.mk + Config.in and bluez-utils.mk +
Config.in. And the bluez-libs seems to cross-compile and install
fine into build_arm/root of the buildroot environment.
But when I try to install bluez-tools, I get the error below while
bluez-tools' configure is working. Apoligizes of line breaks
introduced by my mail client. Also note, that I did not include the
entire screen log.
Did I compile bluez-libs in a wrong way? I have compiled it and
bluez-tools successfully before normally, ie. without buildroot.
I can include the entire log together with buildroot scripts if needed.
sth@speedball:~/au/buildroot$ make bluez-utils
(cd /home/sth/au/buildroot/build_arm/bluez-utils-2.15; \
PATH=/home/sth/au/buildroot/build_arm/staging_dir/bin:/bin:/sbin:/usr/bi
n:/usr/sbin
AR=/home/sth/au/buildroot/build_arm/staging_dir/bin/arm-linux-uclibc
-ar
AS=/home/sth/au/buildroot/build_arm/staging_dir/bin/arm-linux-uclibc-as
LD=/
home/sth/au/buildroot/build_arm/staging_dir/bin/arm-linux-uclibc-ld
NM=/home/sth
/au/buildroot/build_arm/staging_dir/bin/arm-linux-uclibc-nm
CC=/home/sth/au/buil
droot/build_arm/staging_dir/bin/arm-linux-uclibc-gcc
GCC=/home/sth/au/buildroot/
build_arm/staging_dir/bin/arm-linux-uclibc-gcc
CXX=/home/sth/au/buildroot/build_
arm/staging_dir/bin/arm-linux-uclibc-g++
RANLIB=/home/sth/au/buildroot/build_arm
/staging_dir/bin/arm-linux-uclibc-ranlib \
CFLAGS="-Os -pipe " \
./configure \
--target=arm-linux \
--host=arm-linux \
--build=i386-pc-linux-gnu \
--prefix=/usr \
--exec-prefix=/usr \
--bindir=/usr/bin \
--sbindir=/usr/sbin \
--libexecdir=/usr/lib \
--sysconfdir=/etc \
--datadir=/usr/share \
--localstatedir=/var \
--mandir=/usr/man \
--infodir=/usr/info \
--with-bluez=/usr \
);
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
...
... (lots of checking going on)
...
checking for unistd.h... yes
checking bluetooth/bluetooth.h usability... yes
checking bluetooth/bluetooth.h presence... yes
checking for bluetooth/bluetooth.h... yes
checking for hci_open_dev in -lbluetooth... no
configure: error: Bluetooth library not found
make: ***
[/home/sth/au/buildroot/build_arm/bluez-utils-2.15/.configured] Error 1
sth@speedball:~/au/buildroot$
--
Stephan Henningsen
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
reply other threads:[~2005-03-16 15:23 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=42384F8F.8030402@amplex.dk \
--to=sth@amplex.dk \
--cc=bluez-users@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.