From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2017-04-29
Date: Thu, 4 May 2017 09:37:17 +0200 [thread overview]
Message-ID: <20170504093717.7513c27e@free-electrons.com> (raw)
In-Reply-To: <223d1087-7158-2bce-b145-774a871f1911@mind.be>
Hello,
On Thu, 4 May 2017 08:55:47 +0200, Arnout Vandecappelle wrote:
> The problem is that that defconfig file (sourcery-arm-thumb2.config) doesn't
> specify which toolchain to use:
>
> BR2_arm=y
> BR2_cortex_a8=y
> BR2_ARM_EABI=y
> BR2_ARM_INSTRUCTIONS_THUMB2=y
> BR2_TOOLCHAIN_EXTERNAL=y
> BR2_TARGET_OPTIMIZATION=""
>
> It just relies on the default external toolchain.
>
> Obviously this isn't very robust to begin with: when the external toolchains
> change, this could implicitly change this toolchain defconfig. E.g. imagine that
> Linaro would grow a Thumb2 option, then suddenly this sourcery-arm-thumb2.config
> would build using a Linaro toolchain...
Aaah, yes.
> So I think the solution is to explicitly add the predefined external toolchain
> to use to all the toolchain configs. I'll try to send a patch for that.
OK. Thanks.
> BTW, I notice now that we don't have configs for the Codescape toolchains. Any
> reason for that?
Nope, just nobody has suggested one. Or maybe at the time I was a bit
annoyed by having too many MIPS related configurations.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-05-04 7:37 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 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2017-04-29 Thomas De Schampheleire
2017-05-03 12: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 [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=20170504093717.7513c27e@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