All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: Architecture mismatch QA check not fatal?
Date: Mon, 20 Jun 2011 08:23:04 -0500	[thread overview]
Message-ID: <4DFF49B8.9050908@windriver.com> (raw)
In-Reply-To: <AE69955E-732E-4002-90F9-FF833BC78D8A@dominion.thruhere.net>

On 6/20/11 2:41 AM, Koen Kooi wrote:
> Hi,
> 
> I was building qt this weekend and I noticed this one:
> 
> WARNING: QA Issue: Architecture did not match (40 to 62) on /work/armv7a-angstrom-linux-gnueabi/qt4-embedded-4.7.3-r26.1/packages-split/qt4-embedded-tools/usr/bin/moc
> WARNING: QA Issue: Architecture did not match (40 to 62) on /work/armv7a-angstrom-linux-gnueabi/qt4-embedded-4.7.3-r26.1/packages-split/qt4-embedded-tools/usr/bin/uic
> WARNING: QA Issue: Architecture did not match (40 to 62) on /work/armv7a-angstrom-linux-gnueabi/qt4-embedded-4.7.3-r26.1/packages-split/qt4-embedded-tools/usr/bin/rcc
> 
> Shouldn't that be a fatal error, shipping x86 binaries in arm packages?

There are a couple of very minor use cases where this may be necessary.  So I'm
wondering if we can put in an override mechanism that tells the system to make
the QA a warning instead of an error for select packages.  Otherwise, yes.. this
should be an error.

(The minor cases are primarily firmware loaded into off-board cards in PCI
chasis and such.. occasionally these firmware are ELF and of an architecture not
the same as the host..  it's rare, but I have seen it before.)

--Mark

> regards,
> 
> Koen
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core




  reply	other threads:[~2011-06-20 13:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-20  7:41 Architecture mismatch QA check not fatal? Koen Kooi
2011-06-20 13:23 ` Mark Hatle [this message]
2011-06-20 13:29   ` Phil Blundell
2011-06-20 13:31     ` Koen Kooi
2011-06-20 13:55       ` Mark Hatle
2011-06-20 14:25         ` Koen Kooi

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=4DFF49B8.9050908@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-core@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.