On Mon, 20 Feb 2017 18:34:47 -0500, Walter Dnes wrote: > Reading https://wiki.gentoo.org/wiki/Binary_package_guide still leaves > me uncertain. I have an ancient 32-bit Atom netbook. I've installed > uclibc-ng Gentoo on it. Building big packages on it is a pain. I can > do an identical install in a QEMU VM, and distcc into it. But that > doesn't catch all compiling work. > > What I'd like to do is build binaries in a chroot on my desktop, > assuming a 32-bit uclibc-ng chroot on a 64-bit glibc host is possible. > Because the cpus are different, I would need to use different CFLAGS > (and CXXFLAGS) variables for when the host updates its own files, versus > when it builds files for the netbook.
If the chroot is identical to your netbooks's install in terms of *FLAGS, USE, @world etc, then yes. I used to do it this way when I had an Atom netbook. I even build for a low memory 486 system in the same way. > Finally, is it possible for the client (the netbook) to notify the > host that it needs certain packages built? I plan to run with > "--getbinpkgonly" on the netbook. You don't need to if the systems are the same. Set both systems to use the same $PKGDIR, set FEATURES=buildpkg in the chroot and do a world update. Then do the same update on the netbook but with -K. I used a script to control this that basically synced world and most of /etc/portage before entering the chroot, although I later switched to using containers as they make life so much easier. Oh, and you don't need a package server, just export PKGDIR via NFS and mount it on the netbook. -- Neil Bothwick Artificial Intelligence usually beats real stupidity.
pgpA1Z4f_R6U4.pgp
Description: OpenPGP digital signature
