From: Marco Trapanese <marcotrapanese@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Which package for bluetooth management?
Date: Sun, 8 May 2016 11:09:35 +0200 [thread overview]
Message-ID: <572F024F.3000609@gmail.com> (raw)
In-Reply-To: <e3cfa132-94c0-2b3d-7593-3286bab1e535@mind.be>
Il 08/05/2016 01:41, Arnout Vandecappelle ha scritto:
> I've just seen bluez5 requires glibc or musl toolchain.
>> I tried to rebuild all with glibc (instead of uClibc) but the RPi3
>> refuses to
>> boot due to a kernel panic.
In the meanwhile I did something weird... but it seems to work.
I used uClibc adding in the config file the following:
UCLIBC_HAS_REGEX=y
UCLIBC_HAS_WORDEXP=y
UCLIBC_HAS_FOPEN_CLOSEEXEC_MODE=y
then I removed the dependency of bluez5_utils from glibc and tried to
set the latest version: 5.39.
Well... I don't know if it might explode in few minutes but it compiles
fine and bluez5 is (almost) working.
I have to fix some things like the path of bluetoothd
(/usr/libexec/bluetooth/ instead of /usr/sbin) and errors on dbus
(org.bluez.Error.Failed)
But the most important questions is: it's obvious that if I was able to
enable wordexp in uClibc and you didn't enable it - there is a good
reason, which I don't know. Perhaps is it not safe?
Best regards
Marco
prev parent reply other threads:[~2016-05-08 9:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 20:55 [Buildroot] Which package for bluetooth management? Marco Trapanese
2016-05-04 22:40 ` Arnout Vandecappelle
2016-05-05 6:41 ` Marco Trapanese
2016-05-05 7:54 ` Marco Trapanese
2016-05-05 12:25 ` Thomas Petazzoni
2016-05-05 12:29 ` Marco Trapanese
2016-05-05 21:29 ` Marco Trapanese
2016-05-05 21:37 ` Thomas Petazzoni
2016-05-05 21:47 ` Marco Trapanese
2016-05-07 7:32 ` Marco Trapanese
2016-05-07 23:41 ` Arnout Vandecappelle
2016-05-08 5:52 ` Thomas Petazzoni
2016-05-08 9:09 ` Marco Trapanese [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=572F024F.3000609@gmail.com \
--to=marcotrapanese@gmail.com \
--cc=buildroot@busybox.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