From: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2017-04-29
Date: Wed, 3 May 2017 12:29:22 +0200 [thread overview]
Message-ID: <20170503102922.GB26389@argentina> (raw)
In-Reply-To: <20170430062822.F06D82097E@mail.free-electrons.com>
Hi Thomas,
On Sun, Apr 30, 2017 at 08:28:22AM +0200, Thomas Petazzoni wrote:
> Hello,
>
> This is the list of Buildroot build failures that occured on
> 2017-04-29, 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 | toolchain-external-custom | http://autobuild.buildroot.net/results/39888c188c0d13219a8419897a833275fcc81597
>
It seems that this is an invalid configuration:
BR2_arm=y
BR2_cortex_a8=y
BR2_ARM_EABI=y
BR2_ARM_INSTRUCTIONS_THUMB2=y
BR2_STATIC_LIBS=y
BR2_TOOLCHAIN_EXTERNAL=y
With STATIC_LIBS set, there is no downloadable external toolchain.
As such, Buildroot falls back to a preinstalled one and sets the toolchain
location to /path/to/toolchain, which does not exist.
However, I don't find this toolchain config in the list at:
http://autobuild.buildroot.net/toolchains/configs/
The build was submitted by Richard Braun, could it be that he is using toolchain
configs that are not in this list?
Thanks,
Thomas
next parent reply other threads:[~2017-05-03 10:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170430062822.F06D82097E@mail.free-electrons.com>
2017-05-03 10:29 ` Thomas De Schampheleire [this message]
2017-05-03 12:29 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2017-04-29 Thomas Petazzoni
[not found] ` <20170503124713.GA17301@shattrath>
2017-05-03 13:02 ` Thomas Petazzoni
2017-05-04 6:55 ` Arnout Vandecappelle
2017-05-04 7:37 ` 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=20170503102922.GB26389@argentina \
--to=thomas.de_schampheleire@nokia.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