[oe] [PATCH] image.bbclass: reorder do_rootfs

Denys Dmytriyenko denis at denix.org
Wed Apr 22 03:26:38 UTC 2009


On Tue, Apr 21, 2009 at 02:55:19PM -0700, Tom Rini wrote:
> On Tue, Apr 21, 2009 at 02:37:31PM -0700, Tom Rini wrote:
> > On Tue, Apr 21, 2009 at 11:05:55PM +0200, Koen Kooi wrote:
> > > On 21-04-09 22:41, Tom Rini wrote:
> > >> On Mon, Mar 30, 2009 at 11:59:57AM +0400, Roman I Khimov wrote:
> > >>
> > >>> Places do_rootfs function before do_install in image creation process.
> > >>>
> > >>> This change allows multiimage builds, when one image depends on another (before
> > >>> that second image creation raced with do_rootfs for the first one) and uses
> > >>> it for some purpose.
> > >>>
> > >>> Multiimage builds are useful in situations like creating an installer image
> > >>> with initramfs (built in OE) and an image of the target FS (also built in OE)
> > >>> or for building virtualized system images to be placed on target FS.
> > >>
> > >> So, the problem we have happen is that opkg (or dpkg or ...) gets into a
> > >> race because>1 image are trying to muck around in ${TMPDIR}/rootfs,
> > >
> > > No, there's a lockfile for that, otherwise 'bitbake foo-image bar-image'  
> > > wouldn't work (it didn't for a long time).
> > 
> > My snapshot is slighlty stale, but with BB_NUMBER_THREADS >1 it doesn't.
> > Lemme go fire up a build real quick in my current checkout tho..
> 
> OK, old snapshot on my end then.

Not sure how old your snapshot should be for it not to work - multiple images 
on a single bitbake command line worked for a very long time...

-- 
Denys




More information about the Openembedded-devel mailing list