From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Elvis Dowson <elvis.dowson@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: ERROR: Task 7 (/tool/yocto/poky/meta/recipes-core/meta/meta-toolchain.bb, do_populate_sdk) failed with exit code '1'
Date: Mon, 30 Jul 2012 18:18:52 +0100 [thread overview]
Message-ID: <12219656.pCAnqchrzT@helios> (raw)
In-Reply-To: <02EF9496-6BB6-473A-8C55-0BB42CA96FFC@gmail.com>
On Monday 30 July 2012 21:08:54 Elvis Dowson wrote:
> Hi Paul,
>
> On Jul 30, 2012, at 8:58 PM, Paul Eggleton wrote:
> > This is my fault - I'll put together a patch right now. As a workaround
> > you
> > can "bitbake rpmresolve-native" first and you won't get the error anymore.
>
> Thanks for the workaround! It worked.
>
> It would be good if all changes to the master were run through an automated
> build test on an internal git repository, prior to being pushed out to the
> public git repository. This way, you would be able to ensure that breaks in
> the build do not get propagated to all users.
FYI, we do do this already for most significant changes, and it was done for
this one. The trouble with this specific issue is, if you happened to build a
normal image prior to building meta-toolchain or indeed any other user of
do_populate_sdk, the error will not occur because rpmresolve-native would
already have been built; hence why this was missed.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-07-30 17:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-30 16:43 ERROR: Task 7 (/tool/yocto/poky/meta/recipes-core/meta/meta-toolchain.bb, do_populate_sdk) failed with exit code '1' Elvis Dowson
2012-07-30 16:48 ` Martin Jansa
2012-07-30 16:55 ` Elvis Dowson
2012-07-30 16:58 ` Paul Eggleton
2012-07-30 17:08 ` Elvis Dowson
2012-07-30 17:18 ` Paul Eggleton [this message]
2012-07-30 19:52 ` Elvis Dowson
2012-07-30 22:56 ` Paul Eggleton
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=12219656.pCAnqchrzT@helios \
--to=paul.eggleton@linux.intel.com \
--cc=elvis.dowson@gmail.com \
--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.