On Tuesday 21 Feb 2017 16:31:31 Walter Dnes wrote: > 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
Perhaps I do not understand ... why should the chrooted system need to use different flags? Does it have a purpose other than building binpkg for the Atom? > 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". Well, yes if the the chroot is used to other things and it is not meant to merely duplicate a build environment for the Atom, but on more powerful hardware. I use a chroot on a modern 64bit PC with 8 cores and 16GB RAM, to build 32bit binaries for a really old 32bit Pentium 4 PC. The CFLAGS in the chroot are: CFLAGS="-march=prescott -O2 -pipe -fomit-frame-pointer" while the host OS is nothing of the sort. This set up has served me nicely without an NFS, because the host OS is not always on when the Pentium 4 PC is in use. I use rsync/cp for moving the built binaries over to the old PC before I install them there. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
