LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Lennert Buytenhek <buytenh@wantstofly.org>
To: "Michael K. Edwards" <medwards.linux@gmail.com>,
Linux Kernel List <linux-kernel@vger.kernel.org>,
Sam Ravnborg <sam@ravnborg.org>,
linux-arm-toolchain@lists.arm.linux.org.uk,
linux-arm-kernel@lists.arm.linux.org.uk, crossgcc@sourceware.org
Subject: Re: More ARM binutils fuckage
Date: Wed, 6 Dec 2006 02:08:13 +0100 [thread overview]
Message-ID: <20061206010813.GC30401@xi.wantstofly.org> (raw)
In-Reply-To: <20061206002226.GK24038@flint.arm.linux.org.uk>
On Wed, Dec 06, 2006 at 12:22:26AM +0000, Russell King wrote:
> Enabling EABI needs a compiler which supports EABI. That's where I
> get fuzzy but recent gcc 4 should be suitable. I have had it suggested
> to me that EABI support in the toolchain isn't all that stable at the
> moment.
I use a bog-standard gcc 4.1.0 to cross-compile all my ARM kernels
with, which allows me to build both old-ABI and EABI kernels. (These
days I build all kernels in EABI mode with old-ABI compat.) I have
not run into any code generation issues with this compiler yet.
On the ARM I am running an EABI userland with glibc 2.5, and build
stuff natively with vanilla binutils 2.17.50.0.5 (2.17.5.0.3 is 'too
old', as it doesn't understand the two argument form of the .movsp
directive which one of the gcc ICE fix patches emits), and gcc 4.1.1
with some patches from gcc bugzilla to fix an ICE or two.
next prev parent reply other threads:[~2006-12-06 1:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-05 19:33 Russell King
2006-12-05 23:29 ` Michael K. Edwards
2006-12-06 0:22 ` Russell King
2006-12-06 1:08 ` Lennert Buytenhek [this message]
2006-12-06 6:43 ` Re[2]: " Paul Sokolovsky
2006-12-06 8:17 ` Koen Kooi
2006-12-06 14:37 ` Re[2]: " Bruce Ashfield
2006-12-06 1:34 ` Michael K. Edwards
2006-12-06 0:25 ` Russell King
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=20061206010813.GC30401@xi.wantstofly.org \
--to=buytenh@wantstofly.org \
--cc=crossgcc@sourceware.org \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-arm-toolchain@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=medwards.linux@gmail.com \
--cc=sam@ravnborg.org \
--subject='Re: More ARM binutils fuckage' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).