From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] package_deb.bbclass: armel architecture name for eabi systems.
Date: Fri, 18 Feb 2011 14:50:33 -0700 [thread overview]
Message-ID: <4D5EE9A9.10205@mentor.com> (raw)
In-Reply-To: <1298063776-2260-1-git-send-email-filip.zyzniewski@gmail.com>
On 02/18/2011 02:16 PM, Filip Zyzniewski wrote:
> For dpkg EABI system architecture is called armel, not arm.
>
> Signed-off-by: Filip Zyzniewski<filip.zyzniewski@gmail.com>
> ---
> classes/package_deb.bbclass | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/classes/package_deb.bbclass b/classes/package_deb.bbclass
> index 60e759d..87f31fa 100644
> --- a/classes/package_deb.bbclass
> +++ b/classes/package_deb.bbclass
> @@ -15,6 +15,8 @@ DPKG_ARCH_i486 ?= "i386"
> DPKG_ARCH_i586 ?= "i386"
> DPKG_ARCH_i686 ?= "i386"
> DPKG_ARCH_pentium ?= "i386"
> +DPKG_ARCH_linux-gnueabi ?= "armel"
> +DPKG_ARCH_linux-uclibceabi ?= "armel"
>
> python package_deb_fn () {
> bb.data.setVar('PKGFN', bb.data.getVar('PKG',d), d)
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!
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-02-18 21:51 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 [this message]
2011-02-19 17:52 ` Filip Zyzniewski
2011-02-21 15:12 ` Phil Blundell
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=4D5EE9A9.10205@mentor.com \
--to=tom_rini@mentor.com \
--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.