Re: [gentoo-embedded] Emerging into SYSROOT causes packages to install in host system

[Ned Ludd]

On Mon, 2008-04-28 at 05:45 -0400, Mike Frysinger wrote:
> On Sunday 27 April 2008, Dave Bender wrote:
> >   I am attempting to cross compile x86 packages on an x86_64 host. In
> > particular, when I attempt to emerge baselayout-2 into my SYSROOT path,
> > emerge wants to emerge baselayout-2 into my host system. PORTAGE_CONFIGROOT
> > is also set to the SYSROOT, so I do not understand why for example,
> > package.mask on my host system is taken into account at all when emerge
> > determines dependencies.
> > I am following the instructions in Chapter 5 of the Embedded Gentoo
> > Handbook to the letter and do not understand why this behaviour is
> > occurring.
>
> please post the exact commands as well as resulting output.  us guessing at
> what exactly you're doing simply causes confusion and wastes yours and our
> time.

Mike, actually I think I know the bug he is hitting.
If portage sees that you have a dep not installed on / even if you pass
ROOT=/somedir SYSCONFIG=/usr/$CTARGET ARCH=arm CHOST=arm-something
emerge -pvq someapp ; you will get 
[ebuild N ] app-foo/bar 
[ebuild N ] app-foo/bar $ROOT

So if you are using a wrapper and blindly start merging.. Cross compiled
shit will end up on / despite you not asking for it. Zac says this is
current expected behavior but I'd outright call it the most fscked up
portage behavior ever along with the recent INSTALL_MASK= no longer
working when using -K

-- 
gentoo-embedded@l.g.o mailing list