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 09:30:05 +0200 [thread overview]
Message-ID: <20140601093005.46935ca3@free-electrons.com> (raw)
In-Reply-To: <20140601070425.GA4197@waldemar-brodkorb.de>
Dear Waldemar Brodkorb,
On Sun, 1 Jun 2014 09:04:25 +0200, Waldemar Brodkorb wrote:
> Try the internal buildroot toolchain and musl, this will work for
> little endian targets.
Unfortunately, due to a misunderstanding from me, in 2014.05, it's not
possible to build a Microblaze little endian toolchain with musl in
Buildroot. It will be re-enabled for 2014.08, or in a 2014.05.1 release
if we do one.
> The external toolchain for musl is big endian
> only and furthermore contains a bug, because musl 1.0 didn't work
> for microblaze. At least not for qemu-system-microblazeel.
> Rich Felker fixed the Bug after 1.0 release, after I reported it via
> #musl on IRC.
I'm going to send soon a patch that updates a lot of external
toolchains, including the musl ones, and they use a more recent musl
version than 1.0.0.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-06-01 7:30 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
2014-06-01 7:04 ` Waldemar Brodkorb
2014-06-01 7:30 ` 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=20140601093005.46935ca3@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.