From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2016-09-22
Date: Tue, 27 Sep 2016 16:41:45 +0200 [thread overview]
Message-ID: <20160927164145.41d6d6c4@free-electrons.com> (raw)
In-Reply-To: <CAKbGBLhk7nPvHr_X_=htCAuJp2CkrsH3_kPR5FOuArHahk+Wyw@mail.gmail.com>
Hello,
(Added Waldemar + Buildroot ML in Cc)
On Thu, 22 Sep 2016 23:32:53 -0700, Steven Noonan wrote:
> It looks like this failed because pthreads was broken somehow. Could
> it be that the external toolchain didn't have libpthread or something?
Indeed, this seems like a uClibc issue. Waldemar, could you have a look
(see below the reference to the autobuilder failure).
Thanks a lot!
Thomas
>
> On Thu, Sep 22, 2016 at 11:30 PM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
> > Hello,
> >
> > This is the list of Buildroot build failures that occured on
> > 2016-09-22, and for which you are a registered architecture developer
> > or package developer. Please help us improving the quality of
> > Buildroot by investigating those build failures and sending patches to
> > fix them. Thanks!
> >
> > Build failures related to your packages:
> >
> > m68k | powertop-2.7 | http://autobuild.buildroot.net/results/5c63959a89d5761fdefe3bfd36c8168dbe882dc9
> >
> > --
> > http://autobuild.buildroot.net
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next parent reply other threads:[~2016-09-27 14:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160923063043.9B0AD102740@stock.ovh.net>
[not found] ` <CAKbGBLhk7nPvHr_X_=htCAuJp2CkrsH3_kPR5FOuArHahk+Wyw@mail.gmail.com>
2016-09-27 14:41 ` Thomas Petazzoni [this message]
2016-09-27 18:46 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2016-09-22 Peter Seiderer
2016-09-27 22:13 ` Waldemar Brodkorb
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=20160927164145.41d6d6c4@free-electrons.com \
--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