All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Xu, Dongxiao" <dongxiao.xu@intel.com>
To: Koen Kooi <koen@dominion.thruhere.net>,
	"poky-bounces@yoctoproject.org" <poky-bounces@yoctoproject.org>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: [PATCH 1/1] rm_work.bbclass: reserve 'image' folder when	remove WORKDIR
Date: Wed, 26 Jan 2011 16:43:12 +0800	[thread overview]
Message-ID: <D5AB6E638E5A3E4B8F4406B113A5A19A31D0CB5E@shsmsx501.ccr.corp.intel.com> (raw)
In-Reply-To: <E0264D9A-19E7-4EB3-AED5-EDEB6A4F30E0@dominion.thruhere.net>

Koen Kooi wrote:
> Op 26 jan 2011, om 07:30 heeft poky-bounces@yoctoproject.org het
> volgende geschreven: 
> 
>> From: Dongxiao Xu <dongxiao.xu@intel.com>
>> 
>> After the implementation of per machine sysroot, do_populate_sysroot
>> and do_package need to be re-run if we build two machines of one
>> architecture (in case that sstate prebuilt result could not be reused
>> for certain recipes). But if removing all the WORKDIR contents after
>> the first macine build, the second machine's do_populate_sysroot and
>> do_package will fail due to the missing of "image" directory.
>> 
>> Thus reserve 'image' folder when doing rm_work.
> 
> Wouldn't adding do_install to sstate be a better idea? OE was
> designed that it wouldn't depend on WORKDIR after building, so this
> patch is a step in the wrong direction.  

Hi Koen,

Thanks for your suggestions, however this may not help to solve this issue.

The senario of the above issue is, build one machine firstly, doing rm_work, and then try to build the second machine of the same architecture. Some certain recipe's prebuilt result could not be shared between machines.

After the first machine finishes the build, most contents in ${WORKDIR} has been removed by "rm_work". Prebuilt result could not be shared for certain recipes. For those recipes, the second machine finds that most of the recipe stamp files are already there (do_fetch, do_unpack, do_patch, ...) except do_populate_sysroot and do_package, which contains ${MACHINE} tag, thus it will try to re-run do_populate_sysroot and do_package, which relies on the existence of "image" directory.

So even we add the do_install in sstate, the above issue could not be solved because it is triggered when certain recipe's sstate prebuilt result could *not* be shared.

Thanks,
Dongxiao

> 
> regards,
> 
> Koen
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky



  reply	other threads:[~2011-01-26  8:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1296023140.git.dongxiao.xu@intel.com>
     [not found] ` <4da3cd3c9adebd3279b376a1f7aa2a0353484ecd.1296023140.git.dongxiao.xu@intel.com>
2011-01-26  8:23   ` [PATCH 1/1] rm_work.bbclass: reserve 'image' folder when remove WORKDIR Koen Kooi
2011-01-26  8:43     ` Xu, Dongxiao [this message]
2011-01-26 21:24   ` Richard Purdie
2011-01-27  6:15     ` Xu, Dongxiao

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=D5AB6E638E5A3E4B8F4406B113A5A19A31D0CB5E@shsmsx501.ccr.corp.intel.com \
    --to=dongxiao.xu@intel.com \
    --cc=koen@dominion.thruhere.net \
    --cc=poky-bounces@yoctoproject.org \
    --cc=poky@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.