From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] reenable microblaze little endian for internal musl toolchain
Date: Sun, 1 Jun 2014 08:39:25 +0200 [thread overview]
Message-ID: <20140601083925.45e9502d@free-electrons.com> (raw)
In-Reply-To: <CAPALihOk0J7b7GWzth6AsiEm5KE7EZJ1w_XeSfRXbBvZ_Aa04Q@mail.gmail.com>
Dear William Welch,
On Sat, 31 May 2014 17:12:45 -0500, William Welch wrote:
> I did not manually enter any specifics about where/how to download the
> toolchain.
>
> When I asked for an external toolchain, Musl was the only external
> toolchain listed.
Right.
> The resulting 'savedefconfig' looked like this (note: there is no mention
> of musl...)
>
> BR2_microblazeel=y
> BR2_TOOLCHAIN_EXTERNAL=y
> BR2_ENABLE_LOCALE_PURGE=y
> BR2_TARGET_OPTIMIZATION="-pipe -mno-xl-soft-mul -mxl-barrel-shift
> -mcpu=v8.20.a"
There is nothing wrong in what you did. There was a bug in Buildroot,
and I already sent a patch to fix it, and the fix is part of the final
2014.05 release.
The problem was that Buildroot was assuming the pre-built Musl
toolchain was valid for both Microblaze BE and Microblaze LE, which is
not the case. Therefore, in commit
http://git.buildroot.net/buildroot/commit/?id=77ef6a3a12ec1e41317ddfa54842c6a59d75dab8
this problem was fixed. You were in Cc of the patch.
So from now on, if you select Microblaze little endian as the
architecture, the pre-built Musl toolchain will not be selectable.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-06-01 6:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-31 8:45 [Buildroot] [PATCH] reenable microblaze little endian for internal musl toolchain Waldemar Brodkorb
2014-05-31 11:13 ` Thomas Petazzoni
2014-05-31 20:56 ` William Welch
2014-05-31 21:43 ` Thomas Petazzoni
2014-05-31 22:12 ` William Welch
2014-06-01 6:39 ` Thomas Petazzoni [this message]
2014-06-01 7:04 ` Waldemar Brodkorb
2014-06-01 7:30 ` 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=20140601083925.45e9502d@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