From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] reenable microblaze little endian for internal musl toolchain
Date: Sat, 31 May 2014 23:43:15 +0200 [thread overview]
Message-ID: <20140531234315.3cc32e4e@free-electrons.com> (raw)
In-Reply-To: <CAPALihPyH5erdhQOsTiQ7E2_La9AuTi_7ED5tUqpfph713sjWw@mail.gmail.com>
Dear William Welch,
On Sat, 31 May 2014 15:56:01 -0500, William Welch wrote:
> What I know is, that the resulting images built by musl toolchain did not
> work, and readelf says the images are big-endian.
>
> I selected microblaze little endian target and then chose 3 different
> toolchains and made 3 separate builds. -- musl, buildroot internal, and
> the old Xilinx. Musl was the only one that did not run.
You did use the musl external toolchain, right?
> QEMU is nice but does not necessarily prove that a toolchain will work on
> my spartan6 microblazeel design, which I have been using with builroot,
> successfully, for some time now.
Absolutely. Do not hesitate to report back to us any issue that you
might see on Microblaze. We're definitely interested in growing the
user base of Buildroot users on this architecture.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-05-31 21:43 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 [this message]
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
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=20140531234315.3cc32e4e@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.