From: Rob Landley <rob@landley.net>
To: lkml@serverphorums.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bluez with uclibc
Date: Mon, 08 Jul 2013 21:19:36 -0500 [thread overview]
Message-ID: <1373336376.27613.23@driftwood> (raw)
In-Reply-To: <6e9104c416ff417b9c63f47891f947ea.LinuxKernel@www.serverphorums.com> (from lkml@serverphorums.com on Mon Jul 8 03:06:15 2013)
On 07/08/2013 03:06:15 AM, lkml@serverphorums.com wrote:
> Hi,
>
> Today, I need to cross compile Bluez for arm with uclibc library into
> Buildroot environment.
> However, I meet some dependencies between bluez-utils package and MMU
> deactivation due to dBus.
>
> Do you know a way to use Bluez with uclibc library?
Dunno about buildroot, but if you just want to statically link
something against uClibc on arm, you could grab either the cross or
native "armv5l" compiler from
http://landley.net/aboriginal/bin
and add its "bin" subdirectory to your $PATH. I just updated that
toolchain so it's using the 3.10 headers (yes, with the patch for
http://lkml.indiana.edu/hypermail/linux/kernel/1305.2/01452.html the
kernel developers never did fix), and it's the last release version of
uClibc (from a year and change ago, but that's uClibc for you).
As for fixing dependencies beyond "building against uClibc", that's a
buildroot question. They have their own mailing list...
Rob
next prev parent reply other threads:[~2013-07-09 2:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 8:06 Bluez with uclibc lkml
2013-07-09 2:19 ` Rob Landley [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-07-05 9:41 Julien COUVRAND
2013-07-08 19:02 ` Marcel Holtmann
2013-07-09 7:58 ` Julien COUVRAND
2013-07-09 8:37 ` Marcel Holtmann
2010-05-31 4:39 bluez " arjun rath
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=1373336376.27613.23@driftwood \
--to=rob@landley.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@serverphorums.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.