From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2017-05-01
Date: Thu, 4 May 2017 14:58:16 +0200 [thread overview]
Message-ID: <20170504145816.351b3345@free-electrons.com> (raw)
In-Reply-To: <CAOMZO5CG_H47Xcpo=eTF+K7Rm0YMd9XTjfvzwktrYrsCKULWgA@mail.gmail.com>
Hello,
On Thu, 4 May 2017 09:11:09 -0300, Fabio Estevam wrote:
> On Tue, May 2, 2017 at 3:28 AM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
> > Hello,
> >
> > This is the list of Buildroot build failures that occured on
> > 2017-05-01, 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:
> >
> > arm | atest-895b0183a89c15f5e2305... | http://autobuild.buildroot.net/results/24081a28132899e9853dcb33a345db55c7c9d04a
>
> What about adding a "depends on BR2_USE_MMU" to package/atest/Config.in?
>
> Would this be the correct fix for this issue?
No, this has absolutely nothing to do with atest. Lots of other
packages fail to build with the same reason. There is an issue between
binutils 2.27 and elf2flt.
I think we instead need to disable binutils 2.27 on !mmu, and use
binutils 2.28.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-05-04 12:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170502062817.7C03E207D4@mail.free-electrons.com>
2017-05-04 12:11 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2017-05-01 Fabio Estevam
2017-05-04 12:58 ` Thomas Petazzoni [this message]
2017-05-04 13:03 ` Fabio Estevam
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=20170504145816.351b3345@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