From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot for armeb, gcc-4.2.1 fails to build
Date: Mon, 15 Oct 2007 22:48:18 +0200 [thread overview]
Message-ID: <024701c80f6d$3b703380$01c4af0a@Glamdring> (raw)
In-Reply-To: d83696340710150806x33bc3b44ofe8d5cd349220e4@mail.gmail.com
>I have seen the exact same problem. It doesn't matter if you select EABI
>or
> not (the build doesn't complete either way). I have been unable to build
> when selecting "armeb" regardless of what other options I choose. Little
> Endian "arm" builds fine. I have been trying to look into what might be
> going wrong with little success. I added "--disable-libmudflap" to the
> GCC
> options, and that got me a little further in the build but it still failed
> building gcc-final.
>
> As I said, I have built the little endian toolchain with no issues at all.
> I have used the little endian toolchain to build a kernel and u-boot
> 1.2.0which are both big endian.
>
> One idea I had to simplify things is to modify the buildroot so that it
> ALWAYS builds the little endian toolchain, but passes -mbig-endian when
> the
> user selects "armeb". This should greatly reduce the effort required to
> test both "arm" and "armeb" since the same method/patches would be used
> for
> both. Thoughts?
>
I think this is possible to do this already,
select small endian, and make -mbig-endian an
extra TARGET_CFLAGS parameter.
This of course does not have the benefit of reducing the complexity of the
toolchain.
Best Regards
Ulf Samuelsson
next prev parent reply other threads:[~2007-10-15 20:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 5:48 [Buildroot] buildroot for armeb, gcc-4.2.1 fails to build Hamish Moffatt
2007-10-15 15:06 ` Jonathan Nalley
2007-10-15 20:48 ` Ulf Samuelsson [this message]
2007-10-16 0:16 ` Hamish Moffatt
2007-10-16 3:42 ` Hamish Moffatt
2007-10-16 5:56 ` Hamish Moffatt
2007-10-16 6:00 ` Ulf Samuelsson
2007-10-16 6:44 ` Hamish Moffatt
2007-10-17 1:19 ` [Buildroot] PATCH: " Hamish Moffatt
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='024701c80f6d$3b703380$01c4af0a@Glamdring' \
--to=ulf@atmel.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