All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Rama <john.rama01@gmail.com>
To: yocto@yoctoproject.org
Subject: dpkg --print-architecture returns wrong result
Date: Wed, 8 Nov 2017 20:11:12 -0500	[thread overview]
Message-ID: <5A03AB30.5040907@gmail.com> (raw)

Hi, Yocto specialists

I've built the whole system with deb package,
and trying to use package feed feature of yocto.

When try trying to install some package from target, I faced following error.

# apt-get install fontconfig-utils
....
package architecture (armhf) does not match system (armel)
....

When checking the install package of the target system, everything is armhf architecture. 
# dpkg -l 
...
||/ Name                                           Version                     Architecture Description
+++-==============================================-===========================-============-===========================================================================================
ii  alsa-conf:armhf                                1.1.0-r0                    armhf        ALSA sound library
ii  alsa-conf-base:armhf                           1.1.0-r0                    armhf        ALSA sound library
ii  alsa-lib:armhf                                 1.1.0-r0                    armhf        ALSA sound library
...

However, when checking with following commands, it tells armel.
# dpkg --print-architecture
armel

I think "dpkg --print-architecture" returns wrong result. 

I'm using toolchain "arm-poky-linux-gnueabi-gcc" and result of dumpmachine option is as followings.
$ arm-poky-linux-gnueabi-gcc -dumpmachine 
arm-poky-linux-gnueabi

I have no idea how to tell yocto to configure the target system correctly.
Any feedback is highly appreciated.

Kind Regards,
Jonh Rama


             reply	other threads:[~2017-11-09  1:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-09  1:11 John Rama [this message]
2017-11-09 23:50 ` dpkg --print-architecture returns wrong result John Rama
2017-11-10 22:53   ` John Rama

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=5A03AB30.5040907@gmail.com \
    --to=john.rama01@gmail.com \
    --cc=yocto@yoctoproject.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.