From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] bluez5_utils: new package
Date: Mon, 23 Dec 2013 11:16:26 +0100 [thread overview]
Message-ID: <52B80D7A.3010405@free-electrons.com> (raw)
In-Reply-To: <20131223111146.062adc71@skate>
On 23/12/2013 11:11, Thomas Petazzoni wrote:
> Dear Baruch Siach,
>
> On Mon, 23 Dec 2013 11:57:52 +0200, Baruch Siach wrote:
>
>>> Hum, right, it got copied from bluez-utils, I'll remove it
>> Also, it seems that libglib2 doesn't need threads, only wchar.
> libglib2 does need thread support:
>
> config BR2_PACKAGE_LIBGLIB2
> bool "libglib2"
> select BR2_PACKAGE_GETTEXT if BR2_NEEDS_GETTEXT
> select BR2_PACKAGE_LIBICONV if !BR2_ENABLE_LOCALE
> select BR2_PACKAGE_LIBFFI
> select BR2_PACKAGE_PCRE_UCP if BR2_PACKAGE_PCRE
> select BR2_PACKAGE_ZLIB
> depends on BR2_USE_WCHAR # gettext
> depends on BR2_TOOLCHAIN_HAS_THREADS
Yeah, anyway, my patch is doing less thant the one from Marcin last
month so maybe we should focus on getting his in and we can drop mine...
> Thomas
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-12-23 10:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-23 9:37 [Buildroot] [PATCH] bluez5_utils: new package Alexandre Belloni
2013-12-23 9:50 ` Baruch Siach
2013-12-23 9:54 ` Alexandre Belloni
2013-12-23 9:57 ` Baruch Siach
2013-12-23 10:11 ` Thomas Petazzoni
2013-12-23 10:16 ` Alexandre Belloni [this message]
2013-12-23 10:17 ` Baruch Siach
2013-12-23 9:50 ` Thomas Petazzoni
2013-12-23 9:57 ` Thomas Petazzoni
2014-03-07 22:56 ` Thomas Petazzoni
2014-03-07 23:03 ` Alexandre Belloni
2014-03-07 23:09 ` Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2013-11-04 12:59 Marcin Bis
2013-11-04 16:06 ` Thomas De Schampheleire
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=52B80D7A.3010405@free-electrons.com \
--to=alexandre.belloni@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