On Tue, Feb 21, 2017 at 06:02:24AM +0000, Mick wrote > You'll need to run in 32bit mode when chrooting of course: > > linux32 chroot /mnt/Atom_Build_env /bin/bash > source /etc/profile > export PS1="(Atom_Build) $PS1"
I'm already doing something similar with a 32-bit CentOS 6 chroot on a 64-bit no-multilib Gentoo host. No need to reboot. I previously used a QEMU VM. It has disadvantages... - you need dedicated extra space on the disk image for a safety margin - the VM needs its own 5 gigabytes of swap space - the VM has overhead. Building Pale Moon from source took 35 minutes in the VM. In the chroot, it gets done in 22 or 23 minutes. To repeat, the basic question I'm asking is how do I set up a "dual mode" in the chroot so that... - when the chroot is updating *ITSELF* it builds stuff "-march=native" and with its own CPU_FLAGS_X86, etc - when the chroot is building for the Atom, it uses "-march=bonnell" and the Atom's CPU_FLAGS_X86 and stashes binaries in /usr/portage/packages Right now, I think the easiest approach is to go with 2 versions of make.conf, and a wrapper script that copies in the appropriate one before launching "emerge". -- Walter Dnes <waltd...@waltdnes.org> I don't run "desktop environments"; I run useful applications
