Date: Mon, 08 Jul 2013 21:19:36 -0500
From: Rob Landley <rob@landley.net>
Subject: Re: Bluez with uclibc
To: lkml@serverphorums.com
Cc: linux-kernel@vger.kernel.org
References: <6e9104c416ff417b9c63f47891f947ea.LinuxKernel@www.serverphorums.com>
In-Reply-To: <6e9104c416ff417b9c63f47891f947ea.LinuxKernel@www.serverphorums.com>
	(from lkml@serverphorums.com on Mon Jul  8 03:06:15 2013)
Message-Id: <1373336376.27613.23@driftwood>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; DelSp=Yes; Format=Flowed
Content-Disposition: inline
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1251
Lines: 30

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--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/