public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: crossgcc@sourceware.org
Cc: Khem Raj <raj.khem@gmail.com>
Subject: Re: Toolchain for ARM no-MMU OABI with FLAT binaries system.
Date: Thu, 09 Feb 2012 03:32:00 -0000	[thread overview]
Message-ID: <201202082231.53524.vapier@gentoo.org> (raw)
In-Reply-To: <CAMKF1srbBDBE_LrYFLd=cvVwGggHT9vjN+14tXa01-vvXd7cuw@mail.gmail.com>

[-- Attachment #1: Type: Text/Plain, Size: 776 bytes --]

On Wednesday 08 February 2012 08:24:06 Khem Raj wrote:
> On Wed, Feb 8, 2012 at 1:35 AM, Bob Dunlop <bob.dunlop@xyzzy.org.uk> wrote:
> > I know various people have proposed patches including the Debian crew but
> > I've yet to get EABI running on my old Balloon boards.  While it's now of
> > academic interest only, we've frozen that product, does anyone know of a
> > tool chain combo for EABI on ARMv4 without Thumb ?
> 
> OpenEmbedded has machines based on armv4 e.g. strongarm
> and uses EABI and it does work.

there is a linker flag or two to disable interworking so EABI should work on 
armv4 (which makes my NetWinder happy).

armv3 and older obviously won't work with EABI, but it sounds like support for 
that is being dropped from gcc/etc...
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-02-09  3:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-07 22:17 Piotr Grudzinski
2012-02-08  0:18 ` Martin Guy
2012-02-08  9:35   ` Bob Dunlop
2012-02-08  9:43     ` Piotr Borys
2012-02-08 13:24     ` Khem Raj
2012-02-09  3:32       ` Mike Frysinger [this message]
2012-02-08 14:30 ` Piotr Grudzinski
2012-02-08 15:56   ` Khem Raj
2012-02-08 18:37     ` Piotr Grudzinski
2012-02-09  0:13       ` Steve Bennett

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=201202082231.53524.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=crossgcc@sourceware.org \
    --cc=raj.khem@gmail.com \
    /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).