From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libglib2: needs threads
Date: Mon, 15 Jul 2013 17:21:16 +0200 [thread overview]
Message-ID: <20130715172116.141937ad@skate> (raw)
In-Reply-To: <1373900642-9049-1-git-send-email-spenser@gillilanding.com>
Dear Spenser Gilliland,
On Mon, 15 Jul 2013 10:04:02 -0500, Spenser Gilliland wrote:
> See autobuild failures
>
> http://autobuild.buildroot.net/results/d1fb882fe4d22a17bdd438360da515011dda2b30/build-end.log
> http://autobuild.buildroot.net/results/b66e807769ead5caa3e3b6312e9f7c35c14eafe7/build-end.log
> http://autobuild.buildroot.net/results/9c3fa0c5003a6369e70bfe6d611f7d745742a8c7/build-end.log
>
> Signed-off-by: Spenser Gilliland <spenser@gillilanding.com>
> ---
> package/libglib2/Config.in | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/package/libglib2/Config.in b/package/libglib2/Config.in
> index 5282885..0ee53b7 100644
> --- a/package/libglib2/Config.in
> +++ b/package/libglib2/Config.in
> @@ -5,10 +5,12 @@ config BR2_PACKAGE_LIBGLIB2
> select BR2_PACKAGE_LIBFFI
> select BR2_PACKAGE_ZLIB
> depends on BR2_USE_WCHAR # gettext
> + depends on BR2_TOOLCHAIN_HAS_THREADS
No this doesn't work. If you want to do this, you should remove the
libglib2 patch that attempts at making glib work without thread support
and propagate this depends on to all the reverse dependencies of
libglib2.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-07-15 15:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 15:04 [Buildroot] [PATCH 1/1] libglib2: needs threads Spenser Gilliland
2013-07-15 15:21 ` Thomas Petazzoni [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=20130715172116.141937ad@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