Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 25B59E00CCF; Thu, 2 Jun 2016 05:27:37 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=BAYES_40,HTML_MESSAGE autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -0.0 BAYES_40 BODY: Bayes spam probability is 20 to 40% * [score: 0.2804] * 0.0 HTML_MESSAGE BODY: HTML included in message X-Greylist: delayed 1421 seconds by postgrey-1.32 at yocto-www; Thu, 02 Jun 2016 05:27:33 PDT Received: from intranet.lincoln.ln-systems.com (post.ln-systems.com [62.49.123.66]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 99271E00CAF for ; Thu, 2 Jun 2016 05:27:32 -0700 (PDT) Received: from LNSYSCH3 (firewall-ext.lincoln.ln-systems.com [62.49.123.65]) by intranet.lincoln.ln-systems.com (8.13.1/8.13.1) with ESMTP id u52C2t85013515 for ; Thu, 2 Jun 2016 13:03:00 +0100 From: "Colin Helliwell" To: Date: Thu, 2 Jun 2016 13:03:35 +0100 Organization: LN Systems Limited Message-ID: <29e601d1bcc6$ce4b1a70$6ae14f50$@ln-systems.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 15.0 Thread-Index: AdG8xneVD92SS5XhSEiOX86MG4GQJQ== Subject: Mismatch (armel/armhf) between debs and dpkg X-BeenThere: poky@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: colin.helliwell@ln-systems.com List-Id: Poky build system developer discussion & patch submission for meta-yocto List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2016 12:27:37 -0000 Content-Type: multipart/alternative; boundary="----=_NextPart_000_29E7_01D1BCCF.3011F370" Content-Language: en-gb ------=_NextPart_000_29E7_01D1BCCF.3011F370 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I'm trying to understand where/why/how [the target] dpkg is setting it's default architecture. I'm building for BeagleBoneBlack, which is compiling for hardware floating point. The .deb packages created are suffixed armhf (correctly picked up through package_deb.class), yet the dpkg binary itself reports the architecture as armel. Hence, other than forcing/overriding this, dpkg complains about the architecture mismatch. Is there something in there somewhere which will correct dpkg's behaviour? ------=_NextPart_000_29E7_01D1BCCF.3011F370 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I’m trying to understand where/why/how [the = target] dpkg is setting it’s default architecture. I’m = building for BeagleBoneBlack, which is compiling for hardware floating = point. The .deb packages created are suffixed armhf (correctly picked up = through package_deb.class), yet the dpkg binary itself reports the = architecture as armel.

Hence, other = than forcing/overriding this, dpkg complains about the architecture = mismatch.

Is there something in there = somewhere which will correct dpkg’s behaviour?

 

------=_NextPart_000_29E7_01D1BCCF.3011F370--