Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] reenable microblaze little endian for internal musl toolchain
Date: Sun, 1 Jun 2014 09:04:25 +0200	[thread overview]
Message-ID: <20140601070425.GA4197@waldemar-brodkorb.de> (raw)
In-Reply-To: <CAPALihOk0J7b7GWzth6AsiEm5KE7EZJ1w_XeSfRXbBvZ_Aa04Q@mail.gmail.com>

Hi,
William Welch wrote,

> Greetings,
> 
> Recall this is for 2014.05-rc3. ?I just ran through the process again.
> 
> All I did was make simple selection choices in menuconfig.
> 
> 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.?

Try the internal buildroot toolchain and musl, this will work for
little endian targets. 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.
 
best regards    
        Waldemar

  parent reply	other threads:[~2014-06-01  7:04 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 [this message]
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=20140601070425.GA4197@waldemar-brodkorb.de \
    --to=wbx@openadk.org \
    --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