From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: oe-core layer <openembedded-core@lists.openembedded.org>, Patches
Subject: Re: build logs of all images in or-core
Date: Thu, 29 Nov 2012 08:35:02 +0000 [thread overview]
Message-ID: <1354178102.4840.2.camel@ted> (raw)
In-Reply-To: <CAMKF1sopwPYzEsD8S0MmyH=7V+9cuV-oo+KdXRQj3Q9fO8ppRA@mail.gmail.com>
I had a look through these and we can group them as follows:
Unsupported configuration and sensible error given to user:
[x11 instead of directfb enabled]
eglibc.qemuarm.core-image-gtk-directfb.log
eglibc.qemumips.core-image-gtk-directfb.log
eglibc.qemuppc.core-image-gtk-directfb.log
eglibc.qemux86-64.core-image-gtk-directfb.log
eglibc.qemux86.core-image-gtk-directfb.log
[live image doesn't work on architecture]
eglibc.qemuarm.core-image-minimal-initramfs.log
eglibc.qemumips.core-image-minimal-initramfs.log
eglibc.qemuppc.core-image-minimal-initramfs.log
[Built ok but was misconfigured (two kernels)]
eglibc.qemuarm.core-image-rt-sdk.log
eglibc.qemuarm.core-image-rt.log
eglibc.qemux86-64.core-image-rt-sdk.log
eglibc.qemux86-64.core-image-rt.log
eglibc.qemux86.core-image-rt-sdk.log
eglibc.qemux86.core-image-rt.log
[No linux-yocto-rt]
eglibc.qemumips.core-image-rt-sdk.log
eglibc.qemumips.core-image-rt.log
eglibc.qemuppc.core-image-rt-sdk.log
eglibc.qemuppc.core-image-rt.log
In the above list, I would say that the two kernels being built is a bug
we should really fix, the only way to fix it is to make the bitbake
warning about multiple providers an error.
The "interesting" build failures:
[download issue, enable to fetch sources]
eglibc.qemuarm.core-image-lsb-sdk.log
[weird license build failures]
eglibc.qemuarm.core-image-minimal.log
eglibc.qemumips.core-image-minimal-dev.log
eglibc.qemumips.core-image-sato-dev.log
eglibc.qemuppc.core-image-lsb-dev.log
eglibc.qemuppc.core-image-minimal-dev.log
eglibc.qemuppc.core-image-minimal.log
eglibc.qemux86-64.core-image-basic.log
eglibc.qemux86-64.core-image-minimal-dev.log
eglibc.qemux86.core-image-basic.log
eglibc.qemux86.core-image-minimal-dev.log
eglibc.qemux86.core-image-x11.log
Of which this weird license issue is definitely the biggest problem and
the one we need to figure out. The download issue looks to be transient.
Cheers,
Richard
next prev parent reply other threads:[~2012-11-29 10:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 19:06 build logs of all images in or-core Khem Raj
2012-11-28 19:25 ` Saul Wold
2012-11-28 19:43 ` Khem Raj
2012-11-29 8:35 ` Richard Purdie [this message]
2012-11-28 19:26 ` Richard Purdie
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=1354178102.4840.2.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox