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 23:56:31 +0100 [thread overview]
Message-ID: <18409278.lgfylsICqB@helios> (raw)
In-Reply-To: <3BC10996-751B-4657-8F1D-848C0FD88C88@gmail.com>
On Monday 30 July 2012 23:52:18 Elvis Dowson wrote:
> On Jul 30, 2012, at 9:18 PM, Paul Eggleton wrote:
> > 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.
>
> Ah, I see. I normally alway build meta-toolchain, so that I get the cross
> compiler built first, before trying to build core-image-minimal.
I'm guessing you already know this, but you can just build core-image-minimal
without building meta-toolchain and the cross compiler will be built
automatically (and since meta-toolchain builds a bunch of other things it will
take less time overall). Of course, you may actually need the output of meta-
toolchain, in which case you're getting something for the extra build time;
but in that case it still does not matter which order you build them in.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2012-07-30 22:56 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
2012-07-30 19:52 ` Elvis Dowson
2012-07-30 22:56 ` Paul Eggleton [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=18409278.lgfylsICqB@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.