[oe] multiple DISTRO's in tmp

Richard Purdie rpurdie at rpsys.net
Fri Dec 11 11:33:02 UTC 2009


On Fri, 2009-12-11 at 11:29 +0100, Frans Meulenbroeks wrote:
> 2009/12/11 Phil Blundell <philb at gnu.org>:
> > On Fri, 2009-12-11 at 09:39 +0100, Frans Meulenbroeks wrote:
> >> However, I was wondering: wouldn't it be nice to allow multiple
> >> distro's in one tmp dir (so that e.g. if they share the same version
> >> of a recipe (like m4-native or os), this does not need to be
> >> recompiled?
> >
> > Even if the (PN, PV) tuple is the same for two DISTROs it doesn't
> > necessarily follow that the resulting packages will be the same.  They
> > might have selected different compilers, configuration options, or
> > versions of depended-on packages.  Or they might have a different
> > filesystem layout, or any number of other things.
> >
> > So, practically speaking, no: it isn't going to be feasible to make
> > multiple DISTROs coexist in a single TMPDIR.  This is a case where you
> > do need to create a separate TMPDIR.
> 
> I understand that. Then again it *is* possible for multiple machines
> in the same distro to co-exist, even though the machine config file
> could change some flags.
> 
> Rethinking it, I would expect that if things can be shared it would be
> in the native area (and perhaps some things in cross).
> 
> Actually just bumped into this because my tmp dir for angstrom was
> about 18 GB and ofc I didn't have sufficient free space for another
> tree (and also not really enough patience to wait out a build of the
> cross tools).
> 
> Since my main goal was a small filesystem for initramfs, maybe it
> would be better to make a recipe for a small package (e.g.
> minimal_console_image.bb)

Phil is right, its not intended to be able to share multiple DISTROs in
the same TMPDIR and it never will be. Yes, in some cases its possible
things might match but knowing when they do and when they don't is
difficult to tell.

You need separate tmp directories I'm afraid.

Cheers,

Richard






More information about the Openembedded-devel mailing list