From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: lots of WARNING: QA Issue: Bit size did not match (32 to 0) warnings, what do they mean?
Date: Thu, 3 Mar 2011 10:24:53 -0600 [thread overview]
Message-ID: <4D6FC0D5.8@windriver.com> (raw)
In-Reply-To: <4D6FC05B.6040908@windriver.com>
I found the issue. Somewhere in a code merge in lib/oe/qa.py "self.bits = 32"
became "self.bits == 32"
lines 43 and 45 are incorrect. I'll submit a patch shortly to resolve this.
--Mark
> On 3/3/11 9:45 AM, Koen Kooi wrote:
>> > Hi,
>> >
>> > I started noticing a lot of warnings like this:
>> >
>> > WARNING: QA Issue: Bit size did not match (32 to 0) on /work/armv7a-angstrom-linux-gnueabi/udev-165-r2/packages-split/udev/sbin/udevd
> If the file is an ELF file, there are specific checks that are performed,
> machine type, os type.. and bit size. (I suspect the QA message for all of them
> probably need to be improved.)
>
> What I find interesting is it came back as "0". 0 indicates that the elf
> comparison loader was never run.. 0 is "unknown". (32 and 64 are obvious values...)
>
> The code that determines the size is in meta/lib/oe/qa.py. The normal use of
> the code is from the meta/classes/insane.bbclass function. The fact the
> comparison returned a 0 indicates that the qa.py functions did not run. This
> could be a bug in meta/lib/oe/qa.py, or it could be that the routine call in
> package_qa_walk (in insane.bbclass) failed for some reason and something went
> wrong with the exception handler?
>
>> > What do they mean and how can I (help to) fix them?
> First thing to do is check the binary that is being referenced and verify that
> it is infact a valid ARM EABI binary. Assuming it is file, we need to track
> down the code likely starting in qa.py and figure out why it didn't determine
> the bit size.
>
> --Mark
>
>> > regards,
>> >
>> > Koen
>> > _______________________________________________
>> > Openembedded-core mailing list
>> > Openembedded-core@lists.openembedded.org
>> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2011-03-03 16:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 15:45 lots of WARNING: QA Issue: Bit size did not match (32 to 0) warnings, what do they mean? Koen Kooi
2011-03-03 15:53 ` Khem Raj
2011-03-03 16:21 ` Koen Kooi
2011-03-03 16:22 ` Mark Hatle
2011-03-03 16:24 ` Mark Hatle [this message]
2011-03-04 10:46 ` 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=4D6FC0D5.8@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.