From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2013-07-03
Date: Thu, 4 Jul 2013 15:34:38 +0200 [thread overview]
Message-ID: <20130704153438.5417c004@skate> (raw)
In-Reply-To: <51D55EC4.70209@googlemail.com>
Dear Carsten Schoenert,
On Thu, 04 Jul 2013 13:38:44 +0200, Carsten Schoenert wrote:
> 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.
I don't think that's what we want to do. We have a patch on libglib2
that normally allows libglib2 to build and work without thread support,
see
package/libglib2/libglib2-0002-fix-build-when-no-thread-support.patch.
However, when libglib2 was bumped by Spenser Gilliland to 2.36.x, this
patch was not completely properly updated it seems. Maybe this is
something that Samuel Martin could have a look at, since he was the one
who did the original patch?
Unless of course we decide that we don't care about supporting libglib2
without threads, but in this case, the addition "depends
on !BR2_TOOLCHAIN_HAS_THREADS" has to be propagated to *all* reverse
dependencies of libglib2 (quite a significant number of packages).
Best regards,
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-04 13:34 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
2013-07-04 13:34 ` 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=20130704153438.5417c004@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