All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carsten Schoenert <c.schoenert@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2013-07-03
Date: Thu, 04 Jul 2013 13:38:44 +0200	[thread overview]
Message-ID: <51D55EC4.70209@googlemail.com> (raw)
In-Reply-To: <20130704063005.AD97652C109@lolut.humanoidz.org>

Hello,

I looked at a build failure on libglib2.

Am 04.07.2013 08:30, schrieb Thomas Petazzoni:
>        arm |                libglib2-2.36.3 | NOK | http://autobuild.buildroot.net/results/e9fc40239d13a2fcdc842eced2c39994ac2ca498/

I changed the Config.in file like that because libglib2 needs a thread
implementation.

> diff --git a/package/libglib2/Config.in b/package/libglib2/Config.in
> index 5282885..c36c76a 100644
> --- a/package/libglib2/Config.in
> +++ b/package/libglib2/Config.in
> @@ -5,10 +5,11 @@ config BR2_PACKAGE_LIBGLIB2
>  	select BR2_PACKAGE_LIBFFI
>  	select BR2_PACKAGE_ZLIB
>  	depends on BR2_USE_WCHAR # gettext
> +	depends on BR2_TOOLCHAIN_HAS_THREADS
>  	help
>  	  Low-level core library that forms the basis of GTK+ and GNOME.
>  
>  	  http://www.gtk.org/
>  
> -comment "libglib2 requires a toolchain with WCHAR support"
> -	depends on !BR2_USE_WCHAR
> +comment "libglib2 requires a toolchain with WCHAR and threads support"
> +	depends on !BR2_USE_WCHAR || !BR2_TOOLCHAIN_HAS_THREADS
> --

With that change I can't select the libglib2 package anymore with the
toolchain that is used in this defconfig.

But the config is still trying to build the libglib2 package.
Am I wrong or did I missed somthing?

Regards
Carsten

  reply	other threads:[~2013-07-04 11:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-04  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2013-07-03 Thomas Petazzoni
2013-07-04 11:38 ` Carsten Schoenert [this message]
2013-07-04 13:34   ` Thomas Petazzoni

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=51D55EC4.70209@googlemail.com \
    --to=c.schoenert@gmail.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 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.