From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Cui, Dexuan" <dexuan.cui@intel.com>
Cc: Koen Kooi <koen@dominion.thruhere.net>,
Martin Jansa <martin.jansa@gmail.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: opkg still breaks meta-toolchain-gmae
Date: Wed, 21 Dec 2011 13:13:35 +0000 [thread overview]
Message-ID: <1324473215.16323.27.camel@ted> (raw)
In-Reply-To: <1865303E0DED764181A9D882DEF65FB6EA8B6E1B67@shsmsx502.ccr.corp.intel.com>
On Wed, 2011-12-21 at 17:51 +0800, Cui, Dexuan wrote:
> Richard Purdie wrote on 2011-12-21:
> > On Wed, 2011-12-21 at 16:51 +0800, Cui, Dexuan wrote:
> >> Cui, Dexuan wrote on 2011-12-21:
> >>> Hi all,
> >>> After I upgraded to the latest poky master (commit 4648aadf),
> >>> core-image-sato-sdk can build file, but meta-toolchain-gmae (with
> >>> ipk
> >>> packaging) still doesn't work. Now the failure is:
> >>>
> >>> | error: Failed dependencies:
> >>> | libsdl-nativesdk is needed by qemu-nativesdk-0.15.1-r1.x86_64
> >>> NOTE: package meta-toolchain-gmae-1.0-r6: task do_populate_sdk:
> >>> Failed
> >> Sorry, I need to correct this above: It's actually rpm packaging(rpm
> >> did work fine with the slightly older commit 45987c5135) rather than
> >> ipk.
> >>
> >> If I use ipk packaging, I get the similar mkdir failure: mkdir: cannot
> >> create directory `/var/lib/opkg': Permission denied and, I finally got
> >> a libsdl failure, too: | Collected errors: | *
> >> satisfy_dependencies_for: Cannot satisfy the following | dependencies
> >> for task-sdk-host-nativesdk: | * libsdl-nativesdk * So I suppose
> >> the libsdl patch(" fix packaging") is suspicious.
> >>
> >> BTW, I use "MACHINE=qemux86".
> >
> > I have a suspicion this is a missing PR bump on qemu after the libsdl change.
> > Does rebuilding qemu-nativesdk help?
> Yeah, it does help (for rpm packaging)! Please make a patch to bump the PR. :-)
>
> BTW, with ipk, I still got the below issue:
> mkdir: cannot create directory `/var/lib/opkg': Permission denied
This is usually a non fatal error noise in the logs. I appreciate that
we need to fix it but if your build is failing its likely due to
something else.
Cheers,
Richard
prev parent reply other threads:[~2011-12-21 13:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 7:28 opkg still breaks meta-toolchain-gmae Cui, Dexuan
2011-12-21 8:51 ` Cui, Dexuan
2011-12-21 9:10 ` Richard Purdie
2011-12-21 9:51 ` Cui, Dexuan
2011-12-21 13:13 ` Richard Purdie [this message]
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=1324473215.16323.27.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=dexuan.cui@intel.com \
--cc=koen@dominion.thruhere.net \
--cc=martin.jansa@gmail.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.