From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot compilation using uClibc and activating bluez
Date: Tue, 09 Jul 2013 12:50:51 +0200 [thread overview]
Message-ID: <8738rohur8.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <747C1E83C744F44E9ACFB89FAEEC2C7B2423BF9923@EXDCVYMBSTM005.EQ1STM.local> (Julien COUVRAND's message of "Tue, 9 Jul 2013 10:57:13 +0200")
>>>>> "Julien" == Julien COUVRAND <julien.couvrand@stericsson.com> writes:
Julien> Hi,
Julien> I would like to enable Bluez packages using uClibc but i meet
Julien> some dependencies with MMU. We can't enable bluez-utils
Julien> package while MMU is deactivated.
Julien> As soon as i compile Buildroot deactivating MMU dependencies
Julien> into Config.in from bluez-utils package such as:
Julien> --
Julien> config BR2_PACKAGE_BLUEZ_UTILS
Julien> bool "bluez-utils"
Julien> depends on !BR2_avr32
Julien> depends on BR2_USE_WCHAR # libglib2
Julien> depends on BR2_TOOLCHAIN_HAS_THREADS # dbus, alsa-lib
Julien> # depends on BR2_USE_MMU # dbus
Julien> select BR2_PACKAGE_DBUS
Julien> select BR2_PACKAGE_LIBGLIB2
Julien> help
Julien> bluez utils
Julien> --
Indeed, dbus really requires a MMU.
Julien> So, currently, using uclibc for bluez, without MMU activation,
Julien> I can't compile Buildroot due dBus and the "fork". Does it
Julien> exist a way to enable bluez using uClibc avoiding Dbus issues?
Well, uClibc works nicely with a MMU. What hardware platform is this,
doesn't it have a MMU?
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2013-07-09 10:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 8:57 [Buildroot] Buildroot compilation using uClibc and activating bluez Julien COUVRAND
2013-07-09 10:50 ` Thomas Petazzoni
[not found] ` <747C1E83C744F44E9ACFB89FAEEC2C7B2423BF9A50@EXDCVYMBSTM005.EQ1STM.local>
2013-07-09 15:14 ` Thomas Petazzoni
[not found] ` <747C1E83C744F44E9ACFB89FAEEC2C7B2423BF9A66@EXDCVYMBSTM005.EQ1STM.local>
[not found] ` <20130709173907.06199659@skate>
2013-07-10 7:56 ` Julien COUVRAND
2013-07-10 9:04 ` Thomas Petazzoni
2013-07-09 10:50 ` Peter Korsgaard [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=8738rohur8.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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