From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot compilation using uClibc and activating bluez
Date: Tue, 9 Jul 2013 12:50:37 +0200 [thread overview]
Message-ID: <20130709125037.0a4e0077@skate> (raw)
In-Reply-To: <747C1E83C744F44E9ACFB89FAEEC2C7B2423BF9923@EXDCVYMBSTM005.EQ1STM.local>
Dear Julien COUVRAND,
On Tue, 9 Jul 2013 10:57:13 +0200, Julien COUVRAND wrote:
> I would like to enable Bluez packages using uClibc but i meet some dependencies with MMU.
> We can't enable bluez-utils package while MMU is deactivated.
>
> As soon as i compile Buildroot deactivating MMU dependencies into Config.in from bluez-utils package such as:
>
> --
> config BR2_PACKAGE_BLUEZ_UTILS
> bool "bluez-utils"
> depends on !BR2_avr32
> depends on BR2_USE_WCHAR # libglib2
> depends on BR2_TOOLCHAIN_HAS_THREADS # dbus, alsa-lib
> # depends on BR2_USE_MMU # dbus
> select BR2_PACKAGE_DBUS
> select BR2_PACKAGE_LIBGLIB2
> help
> bluez utils
> --
>
> I have got following compilation errors:
>
> --
> >../dbus/.libs/libdbus-internal.a(libdbus_internal_la-dbus-sysdeps-util-unix.o): In function `_dbus_become_daemon':
> > dbus-sysdeps-util-unix.c:(.text+0x530): undefined reference to `fork'
> > ../dbus/.libs/libdbus-internal.a(libdbus_internal_la-dbus-spawn.o): In function `_dbus_spawn_async_with_babysitter':
> > dbus-spawn.c:(.text+0xe38): undefined reference to `fork'
> > dbus-spawn.c:(.text+0xea0): undefined reference to `fork'
> > collect2: error: ld returned 1 exit status
> > make[3]: *** [dbus-daemon] Error 1
> > make[3]: *** Waiting for unfinished jobs....
> > ../dbus/.libs/libdbus-internal.a(libdbus_internal_la-dbus-sysdeps-util-unix.o): In function `_dbus_become_daemon':
> > dbus-sysdeps-util-unix.c:(.text+0x530): undefined reference to `fork'
> > collect2: error: ld returned 1 exit status
> > make[3]: *** [dbus-daemon-launch-helper] Error 1
> --
>
> So, currently, using uclibc for bluez, without MMU activation, I can't compile Buildroot due dBus and the "fork".
> Does it exist a way to enable bluez using uClibc avoiding Dbus issues?
Well, as you've seen, bluez requires DBus (it's a mandatory
dependency), and DBus uses fork(). Maybe it's possible to build and
make DBus work on non-MMU platform by patching it to not use fork().
Maybe you want to check the Blackfin Buildroot repository at
http://blackfin.uclinux.org/git/?p=buildroot;a=shortlog to see if they
have dbus patches in package/dbus/ to make it work on non-MMU
platforms. If they do, don't hesitate to integrate it in Buildroot, and
send us a patch to make DBus work on non-MMU platforms.
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next 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 [this message]
[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
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=20130709125037.0a4e0077@skate \
--to=thomas.petazzoni@free-electrons.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