From: Ming Liu <ming.liu@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] sstate: remove binutils-crosssdk from safe dependent list
Date: Wed, 8 Jan 2014 14:05:57 +0800 [thread overview]
Message-ID: <52CCEAC5.1090905@windriver.com> (raw)
In-Reply-To: <1389103082.6899.27.camel@ted>
On 01/07/2014 09:58 PM, Richard Purdie wrote:
> On Tue, 2014-01-07 at 16:13 +0800, Ming Liu wrote:
>> binutils-crosssdk is being depended by other packages like
>> gcc-crosssdk-initial, so it's not safe to be skipped when checking the
>> setscene dependencies in setscene_depvalid().
> Can you explain this change a bit more please?
>
> Personally, I think the code is right as it is, if the sstate object
> exists, it was already compiled and we don't ever need bintuils* so its
> a 'safe' dep and can be skipped?
Actually I am not very clear about why the binutils-crosssdk should be a
build time dependency, because based on my test, it's seems to being
required by gcc-crosssdk-initial at runtime, the steps:
bitbake nativesdk-eglibc-initial -c cleansstate
bitbake gcc-crosssdk-initial binutils-crosssdk -c clean
bitbake gcc-crosssdk-initial
bitbake nativesdk-eglibc-initial
the above will fail due to lacking binutils-crosssdk stuff in sysroot.
//Ming Liu
>
> Cheers,
>
> Richard
>
>
>
prev parent reply other threads:[~2014-01-08 6:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 8:13 [PATCH 1/2] sstate: add do_package to the noexec list in setscene_depvalid Ming Liu
2014-01-07 8:13 ` [PATCH 2/2] sstate: remove binutils-crosssdk from safe dependent list Ming Liu
2014-01-07 13:58 ` Richard Purdie
2014-01-08 6:05 ` Ming Liu [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=52CCEAC5.1090905@windriver.com \
--to=ming.liu@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox