From: Ralf Corsepius <ralf.corsepius@rtems.org>
To: Joachim Nilsson <jocke@vmlinux.org>
Cc: crossgcc@sourceware.org
Subject: Re: Is it possible to build a cross compiler supporting both big & little endian?
Date: Sun, 06 Sep 2009 16:20:00 -0000 [thread overview]
Message-ID: <4AA3E149.5050009@rtems.org> (raw)
In-Reply-To: <4AA3DC6A.6030709@vmlinux.org>
On 09/06/2009 05:59 PM, Joachim Nilsson wrote:
> Hi!
>
> We run both little and big endian Arm targets at work. Currently both
> are Arm9 so naturally I started thinking about creating one single
> toolchain to bind them all...
>
> I put together a standard arm-unknown-linux-uclibc with crosstool and
> building the kernel worked fine using "-mbig-endian -mcpu=xscale
> -mtune=xscale -msoft-float", but when I reached userspace the first
> effort at linking with libgcc of course failed.
>
> So I wonder, is it even possible to maintain one toolchain supporting
> different endians?
Generally speaking, of course it is. What you are looking for is a
big/little endian multilib'ed toolchains.
Ralf
--
For unsubscribe information see http://sourceware.org/lists.html#faq
prev parent reply other threads:[~2009-09-06 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-06 15:59 Joachim Nilsson
2009-09-06 16:14 ` Yann E. MORIN
2009-09-06 16:27 ` Joachim Nilsson
2009-09-06 16:20 ` Ralf Corsepius [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=4AA3E149.5050009@rtems.org \
--to=ralf.corsepius@rtems.org \
--cc=crossgcc@sourceware.org \
--cc=jocke@vmlinux.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).