[poky] [PATCH 1/1] rm_work.bbclass: reserve 'image' folder when remove WORKDIR

Xu, Dongxiao dongxiao.xu at intel.com
Wed Jan 26 00:43:12 PST 2011


Koen Kooi wrote:
> Op 26 jan 2011, om 07:30 heeft poky-bounces at yoctoproject.org het
> volgende geschreven: 
> 
>> From: Dongxiao Xu <dongxiao.xu at 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 at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky




More information about the poky mailing list