From: Phil Blundell <philb@gnu.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] package_deb.bbclass: armel architecture name for eabi systems.
Date: Mon, 21 Feb 2011 15:12:32 +0000 [thread overview]
Message-ID: <1298301152.2178.375.camel@phil-desktop> (raw)
In-Reply-To: <4D5EE9A9.10205@mentor.com>
On Fri, 2011-02-18 at 14:50 -0700, Tom Rini wrote:
> I'm a little puzzled. So little endian gnueabi ARM is armel, little
> endian OABI ARM is arm. What about big endian ARM cases? Thanks!
Debian has never had big-endian ARM as an officially supported
architecture, so to that extent there's no precedent to follow in this
area.
The natural name for a big-endian gnueabi port would obviously be
"armeb". That does leave big-endian OABI somewhat out in the cold but,
given that OABI has been obsolescent for the best part of a decade, this
doesn't seem totally unreasonable. If anybody did want to use dpkg with
such a thing (and wanted to avoid colliding with armeb) then I guess
they'd have to name it "armob" or something.
p.
next prev parent reply other threads:[~2011-02-21 15:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 21:40 deb packages architecture problem Filip Zyzniewski
2011-02-18 10:11 ` Andreas Oberritter
2011-02-18 21:16 ` [PATCH] package_deb.bbclass: armel architecture name for eabi systems Filip Zyzniewski
2011-02-18 21:50 ` Tom Rini
2011-02-19 17:52 ` Filip Zyzniewski
2011-02-21 15:12 ` Phil Blundell [this message]
2011-02-21 15:41 ` Leon Woestenberg
2011-02-21 19:15 ` Khem Raj
2011-02-19 23:30 ` [PATCHv2] package_deb.bbclass/apt: " Filip Zyzniewski
2011-02-20 1:11 ` Khem Raj
2011-02-20 10:20 ` [PATCHv3] " Filip Zyzniewski
2011-02-20 10:23 ` [PATCHv2] " Filip Zyzniewski
2011-02-20 10:27 ` [PATCHv4] " Filip Zyzniewski
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=1298301152.2178.375.camel@phil-desktop \
--to=philb@gnu.org \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.