On Fri, 1 Jan 2016 22:11:34 -0500, waltd...@waltdnes.org wrote: > I'm trying to run a distccserver in a 32-bit VM on a 64-bit host, for > the benefit of my ancient 32-bit-only netbook. Yeah, "it'll work" using > the native 64-bit host OS. But any stuff that links against 32-bit > libraries is going to be sent back to the netbook to compile locally. > That defeats the whole purpose of distcc. This is why I want the 32-bit > VM to compile for the 32-bit Atom. Here's the launch script for the > 32-bit VM on the i3 machine...
I used to take a different approach. Instead of a VM I used a chroot that was a clone of the netbook, except that make.conf in the chroot included buildpkg in FEATURES and the netbook's make.conf have --usepkg in DEFAULT_OPTs. PKGDIR was an NFS share accessible to both. Then I would simply emerge whatever I wanted in the chroot, then emerge it on the netbook. No messing around with distcc, which will always run some stuff on the local system, instead everything but unpacking the package tarballs was done in the VM. This approach meant that I could easily script the build process for several systems, including a 486 box was running at the time. I later switched to using systemd containers instead of chroots. -- Neil Bothwick Is it true that cannibals don't eat clowns because they taste funny?
pgpbgFNsCh0se.pgp
Description: OpenPGP digital signature
