All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Zhai, Edwin" <edwin.zhai@intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: multilib build failure with shadow-sysroot:do_populate_sysroot_setscene
Date: Tue, 06 Mar 2012 08:07:56 +0800	[thread overview]
Message-ID: <4F55555C.3060708@intel.com> (raw)
In-Reply-To: <1330702308.309.10.camel@ted>

On 03/02/2012 11:31 PM, Richard Purdie wrote:
> On Fri, 2012-03-02 at 14:33 +0800, Zhai, Edwin wrote:
>> RP,
>> I have image-sato multilib build failure with following error:
>>
>> "ERROR: Task do_package_setscene depends upon nonexistant task
>> /distro/edwin-working/poky/meta/recipes-extended/shadow/shadow-sysroot_4.1.4.3.bb:do_populate_sysroot_setscene
>> Summary: There was 1 ERROR message shown, returning a non-zero exit code."
>>
>> After removing "shadow-sysroot:do_populate_sysroot_setscene" from
>> USERADDSETSCENEDEPS in meta/classes/useradd.bbclass, I can pass the build.
>>
>> Why does it become nonexistant task in multilib building? Any possible fix for
>> it?
>
> Totally guessing but does replacing:
>
> shadow-sysroot:do_populate_sysroot_setscene
>
> with:
>
> ${MLPREFIX}shadow-sysroot:do_populate_sysroot_setscene
>
> work better?

RP,
It works. I'll send out this patch after test.
BTW, shouldn't it be extended automatically?

Thanks,
Edwin

>
> Cheers,
>
> Richard
>
>
>




      reply	other threads:[~2012-03-06  0:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-02  6:33 multilib build failure with shadow-sysroot:do_populate_sysroot_setscene Zhai, Edwin
2012-03-02 15:31 ` Richard Purdie
2012-03-06  0:07   ` Zhai, Edwin [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=4F55555C.3060708@intel.com \
    --to=edwin.zhai@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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.