From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Does buildroot toolchain support GNU EABI?
Date: Wed, 22 May 2013 17:54:51 +0200 [thread overview]
Message-ID: <20130522175451.4c16fa6b@skate> (raw)
In-Reply-To: <CAAsE_ufrpUoERp3h34xz6GRqNtikoxtZVa3h_-Zz676VrU6+ow@mail.gmail.com>
Dear Woody Wu,
On Wed, 22 May 2013 23:04:31 +0800, Woody Wu wrote:
> > On Wed, 22 May 2013 11:33:56 +0200, Yegor Yefremov wrote:
> >
> > > BR toolchains are always EABI unless you specify it to generate OABI
> > > binaries. See Wikipaedia for EABI info:
> > > http://en.wikipedia.org/wiki/EABI#EABI
> >
> > The support for OABI has been deprecated in Buildroot since
> > c4cfa85b798cb744954d35aa05fa41e7a6956abd. I even believe it has been
> > deprecated or maybe removed from the latest version of gcc.
>
> Did you mean the GNU EABI is the OABI?
No. You have two ABIs:
* OABI, Original ABI (or "Old" ?), which was used by the Linux world
on ARM platforms before ARM (the company) standardized an ABI. This
ABI is deprecated, both in Buildroot and upstream in gcc, if I
remember correctly.
* EABI, Enhanced ABI, which is known in the Linux world as GNU EABI.
So when you have a arm-linux-gnueabi toolchain, or
arm-linux-uclibcgnueabi toolchains, those are using this EABI. This
ABI is standardized by ARM. And Buildroot always uses this ABI when
it generates a toolchain.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-05-22 15:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 9:20 [Buildroot] Does buildroot toolchain support GNU EABI? Woody Wu
2013-05-22 9:33 ` Yegor Yefremov
2013-05-22 11:51 ` Thomas Petazzoni
2013-05-22 15:04 ` Woody Wu
2013-05-22 15:54 ` Thomas Petazzoni [this message]
2013-05-22 15:12 ` Woody Wu
2013-05-22 17:37 ` Yann E. MORIN
2013-05-23 3:19 ` Woody Wu
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=20130522175451.4c16fa6b@skate \
--to=thomas.petazzoni@free-electrons.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