All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Oberritter <obi@opendreambox.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: deb packages architecture problem.
Date: Fri, 18 Feb 2011 11:11:13 +0100	[thread overview]
Message-ID: <4D5E45C1.7010504@opendreambox.org> (raw)
In-Reply-To: <AANLkTinr=zf_zn16kQrx4h=ZTVnJnZyQVE46oLjN+v-Q@mail.gmail.com>

On 02/17/2011 10:40 PM, Filip Zyzniewski wrote:
> there is a problem with deb packages.
> 
> When installing packages on the target system dpkg complains:
> "package architecture (arm) does not match system (armel)"
> 
> The question is - should we convince dpkg that the architecture is
> arm, or build the packages so that their architecture is armel?
> 
> First solution may cause some problems with dpkg not expecting this
> value on a particular system, the second means potential bugs
> resulting from a deeper change in OpenEmbedded.

Looking at package_deb.bbclass, the solution seems to be setting
DPKG_ARCH_arm ?= "armel" in there.

Regards,
Andreas



  reply	other threads:[~2011-02-18 10:12 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 [this message]
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
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=4D5E45C1.7010504@opendreambox.org \
    --to=obi@opendreambox.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.