From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Maxwell Bottiger <sleepylight@jive-turkey.net>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: architecture mismatch during kernel build (40 to 3)
Date: Mon, 4 Nov 2013 23:28:23 -0500 [thread overview]
Message-ID: <527873E7.8000103@windriver.com> (raw)
In-Reply-To: <CADi-vsxH-E=StkCnZtw9-U7RLSC6cn-RFw684GXfANEhhMAe7Q@mail.gmail.com>
On 13-11-04 8:41 PM, Maxwell Bottiger wrote:
> I'm building a custom kernel, and I think I'm nearly there. I'm seeing
> an error when running mkimage. bitbake is complaining about an
> architecure mismatch, but I don't know which files it is comparing, or
> if the mismatch really matters (32bit x86 vs 64bit x86 or whatever)
>
> Here's the error string:
>
> WARNING: File '/usr/src/kernel/mkimage' from linux-yocto-custom was
> already stripped, this will prevent future debugging!
>
> ERROR: QA Issue: Architecture did not match (40 to 3) on
> /work/at91sam9x5ek-poky-linux-gnueabi/linux-yocto-custom/2.6.39-r1/packages-split/kernel-dev/usr/src/kernel/mkimage
The obvious answer is .. it is mkimage that it is complaining about. You
are packaging mkimage (which is likely an x86 elf file) into your
kernel-dev package (which is your target arch, likely powerpc or ARM).
Hence the QA error.
In your kernel recipe, you can remove the file before packaging
(i.e. in the do_install_append) or inhibit the QA check for your recipe.
What exactly does your kernel recipe look like ? What is building mkimage
and then getting it installed into /usr/src/kernel ?
My suggestion is to track that down, versus inhibiting the QA check.
Bruce
>
> ERROR: QA run found fatal errors. Please consider fixing them.
>
> ERROR: Function failed: do_package_qa
>
> ERROR: Logfile of failure stored in:
> /home/sleepylight/workspace/yocto/poky/build-atmel/tmp/work/at91sam9x5ek-poky-linux-gnueabi/linux-yocto-custom/2.6.39-r1/temp/log.do_package.11527
>
> ERROR: Task 18
> (/home/sleepylight/workspace/yocto/poky/meta-atmel/recipes-kernel/linux/linux-yocto-custom_2.6.39.bb
> <http://linux-yocto-custom_2.6.39.bb>, do_package) failed with exit code '1'
>
>
> I'm building on a 64 bit linux platform, I don't know if that makes a
> difference.
>
> Thanks all. I'm nearly there!
>
> -Max
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
next prev parent reply other threads:[~2013-11-05 4:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 1:41 architecture mismatch during kernel build (40 to 3) Maxwell Bottiger
2013-11-05 4:28 ` Bruce Ashfield [this message]
2013-11-05 17:46 ` Maxwell Bottiger
2013-11-06 1:08 ` Maxwell Bottiger
2013-11-06 2:50 ` Bruce Ashfield
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=527873E7.8000103@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=sleepylight@jive-turkey.net \
--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.