After configuring with the attached config.log, I'm getting the
following error during build:
CC btio/bluetoothd-btio.o
btio/btio.c: In function 'bt_io_get_type':
btio/btio.c:109:35: error: 'SO_DOMAIN' undeclared (first use in this function)
btio/btio.c:109:35: note: each undeclared identifier is reported only once for each function it appears in
btio/btio.c:123:35: error: 'SO_PROTOCOL' undeclared (first use in this function)
make[3]: *** [btio/bluetoothd-btio.o] Error 1
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/embedded-linux/tool/ti-sdk/bluez/bluez-5.2'
make[1]: *** [make] Error 2
make[1]: Leaving directory `/home/embedded-linux/tool/ti-sdk/bluez'
make: *** [bluez] Error 2
I checked the kernel/usr/include/sys/socket.h and it does not have
SO_DOMAIN defined. I am using a fresh (cross-)build of glibc-2.17.
Note that I am cross-compiling for the beagle-board xm using TI's Arago
cross-compiler tools.
Am I missing something obvious, or is this a build bug?
--
Randy Yates
Digital Signal Labs
http://www.digitalsignallabs.com
PS: The target kernel is a patched 3.7.4 from Robert Nelson's
distribution.
--Randy
Randy Yates <[email protected]> writes:
> After configuring with the attached config.log, I'm getting the
> following error during build:
>
> CC btio/bluetoothd-btio.o
> btio/btio.c: In function 'bt_io_get_type':
> btio/btio.c:109:35: error: 'SO_DOMAIN' undeclared (first use in this function)
> btio/btio.c:109:35: note: each undeclared identifier is reported only once for each function it appears in
> btio/btio.c:123:35: error: 'SO_PROTOCOL' undeclared (first use in this function)
> make[3]: *** [btio/bluetoothd-btio.o] Error 1
> make[2]: *** [all] Error 2
> make[2]: Leaving directory `/home/embedded-linux/tool/ti-sdk/bluez/bluez-5.2'
> make[1]: *** [make] Error 2
> make[1]: Leaving directory `/home/embedded-linux/tool/ti-sdk/bluez'
> make: *** [bluez] Error 2
>
> I checked the kernel/usr/include/sys/socket.h and it does not have
> SO_DOMAIN defined. I am using a fresh (cross-)build of glibc-2.17.
>
> Note that I am cross-compiling for the beagle-board xm using TI's Arago
> cross-compiler tools.
>
> Am I missing something obvious, or is this a build bug?
--
Randy Yates
Digital Signal Labs
http://www.digitalsignallabs.com