From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Quick note about one of the autobuilder failures
Date: Sun, 25 Sep 2011 12:10:35 +0100 [thread overview]
Message-ID: <1316949043.8185.4.camel@ted> (raw)
With the autobuilder now stressing out sstate more, we're seeing some
interesting build failures. One example which caught my eye is:
http://autobuilder.yoctoproject.org:8010/builders/nightly-arm/builds/100/steps/shell_57/logs/stdio
What this is telling us is we actually have some dependency issues in
the metadata. I've already established that:
libXinerama.so.1 is needed by libgtk-2.0-2.22.1-r4.armv5te
means that gtk+ needs to disable xinerama (preferred) or depend on
xinerama.
I've also seem a local error which showed:
neon needs to depend on libproxy (preferred) or to explicitly disable
it.
Once you understand these messages mean we need to look into the base
recipes dependencies, they become easier to dig into and fix.
Cheers,
Richard
reply other threads:[~2011-09-25 11:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1316949043.8185.4.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox