dpkg is using a script (dpkg-architecture.pl) to detect the target architecture automatically. Unfortunately, it is using the cross compiler prefix to do the detection and for ARM, oe-core is using <vendor>-linux-gnueabi for toolchains with and without call-convention hard. The script then always detects 'armel' and never gets 'armhf' for call-convention hard.
This solves: dpkg: error processing archive evtest_1.32+0+b8343ec112-r0_armhf.deb (--install): package architecture (armhf) does not match system (armel) Errors were encountered while processing: evtest_1.32+0+b8343ec112-r0_armhf.deb Signed-off-by: Alexandre Belloni <[email protected]> --- meta/recipes-devtools/dpkg/dpkg.inc | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/recipes-devtools/dpkg/dpkg.inc b/meta/recipes-devtools/dpkg/dpkg.inc index 440a500..1f29113 100644 --- a/meta/recipes-devtools/dpkg/dpkg.inc +++ b/meta/recipes-devtools/dpkg/dpkg.inc @@ -35,6 +35,7 @@ EXTRA_OECONF = "\ " EXTRA_OECONF += "TAR=tar" +EXTRA_OECONF += "DEB_HOST_ARCH=${DPKG_ARCH}" do_configure () { echo >> ${S}/m4/compiler.m4 -- 1.9.1 -- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel
