From: Randy Yates <yates@digitalsignallabs.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: bluez 5.2 build problem
Date: Sat, 09 Feb 2013 05:31:42 -0500 [thread overview]
Message-ID: <8738x5zskx.fsf@randy.site> (raw)
In-Reply-To: <87d2w9zsnw.fsf@randy.site> (Randy Yates's message of "Sat, 09 Feb 2013 05:29:55 -0500")
PS: The target kernel is a patched 3.7.4 from Robert Nelson's
distribution.
--Randy
Randy Yates <yates@digitalsignallabs.com> 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
prev parent reply other threads:[~2013-02-09 10:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-09 10:29 bluez 5.2 build problem Randy Yates
2013-02-09 10:31 ` Randy Yates [this message]
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=8738x5zskx.fsf@randy.site \
--to=yates@digitalsignallabs.com \
--cc=linux-bluetooth@vger.kernel.org \
/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