[Bluez-devel] Error compiling bluez-utils for buildroot/ARM

[Stephan Henningsen <sth@amplex.dk>]

[-- Attachment #1: Type: text/plain, Size: 4056 bytes --]

Hi,

This is not about a bug in bluez-utils, but I would like some help 
integrating BlueZ into the buildroot crossplatform environment.

I've made two packages (i.e. Config.in and .mk file) for the 
buildroot environment, that should support bluez-libs and 
bluez-utils.  The libs appear to install smoothly, but the utils 
fail during configure.

I've attached both the packages in a .tar.gz which can be extracted 
into buildroot/package/ where it will create both BlueZ packages. 
These packages basically delegate to the Makefile of BlueZ, so you 
guys should be home free ;)

The attached packages result in this error, when installing bluez-libs:

sth@speedball:~/au/buildroot$ make bluez-utils-dirclean bluez-utils
rm -rf /home/sth/au/buildroot/build_arm/bluez-utils-2.15
zcat /home/sth/au/buildroot/dl/bluez-utils-2.15.tar.gz | tar -C 
/home/sth/au/buildroot/build_arm -xf -
touch /home/sth/au/buildroot/build_arm/bluez-utils-2.15/.source
(cd /home/sth/au/buildroot/build_arm/bluez-utils-2.15; \
 
PATH=/home/sth/au/buildroot/build_arm/staging_dir/bin:/bin:/sbin:/usr/bin:/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/buildroot/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 \
         --datadir=/usr/share \
         --sysconfdir=/etc \
         --localstatedir=/var \
         --infodir=/usr/info \
         --mandir=/usr/man \
         --with-bluez=/usr \
);
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... mawk
...
...
...
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$






If I add  --libdir=${TARGET_DIR}/usr/lib  (which expands to 
--libdir=/home/sth/au/buildroot/build_arm/root/usr/lib) to the 
configure command, the configuring succeeds, but compilation fails:

...

/home/sth/au/buildroot/build_arm/staging_dir/bin/arm-linux-uclibc-gcc 
-I/usr/include -DDBUS_API_SUBJECT_TO_CHANGE  -Os -pipe    -o hcid 
main.o security.o storage.o lib.o parser.o lexer.o kword.o 
glib-ectomy.o     -L/home/sth/au/buildroot/build_arm/root/usr/lib 
-lbluetooth
lexer.o(.text+0x7e0): In function `yy_get_next_buffer':
: undefined reference to `_IO_getc'
collect2: ld returned 1 exit status
make[3]: *** [hcid] Error 1
make[3]: Leaving directory 
`/home/sth/au/buildroot/build_arm/bluez-utils-2.15/hcid'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory 
`/home/sth/au/buildroot/build_arm/bluez-utils-2.15'
make[1]: *** [all] Error 2
make[1]: Leaving directory 
`/home/sth/au/buildroot/build_arm/bluez-utils-2.15'
make: *** 
[/home/sth/au/buildroot/build_arm/bluez-utils-2.15/src/l2ping.o] Error 2
sth@speedball:~/au/buildroot$


I am new to buildroot and not very experinced with compiler flags, 
especially not in a cross-compile environment.  For all I know, the 
extra --libdir may very well result in a hardcoded path, that 
doesn't resolve on the target system.


Any help is appreciated as I am stuck!


-- 
Stephan Henningsen

[-- Attachment #2: bluez-packages.tar.bz --]
[-- Type: application/octet-stream, Size: 1433 bytes --]