machines crashing during builds could also be a temperature problem as the drive, ram, network (in this case) and processor are all doing heavy lifting. if you launch a system monitor and try to compile on the laptops you can see why they are crashing, it should be in the logs as well.
mad.scientist.at.large (a good madscientist) -- 4. Nov 2017 13:30 by waltd...@waltdnes.org: > On Fri, Nov 03, 2017 at 06:54:49PM +0200, Lasse Pouru wrote >> I have a bunch of old laptops that large builds such as texlive >> and ghc fail on, I'm assuming because of insufficient memory and >> disk space. If I've understood correctly, with Distcc I could build >> everything on my main desktop PC and have the binaries transferred >> through network? How does this work, exactly, and is it a lot of >> work to set up? I currently have no networking devices besides a >> single modem/router, would something more be required? > > My experiences with booby traps... > > * on the "old laptops" do *NOT* set "-march=native". They'll dispatch > that flag to the compiler host, which will build "native" for the > compiler host... oops. Instead, specify the the exact arch on the > client. The compiler host will then build for that arch. How do you > figure out the client's arch, you ask? *ON THE CLIENT* (i.e. the old > laptop) run the command... > > gcc -c -Q -march=native --help=target | grep march= > > ...and stick the result into "-march=" on the client > > * 32-bit clients should have a 32-bit build host. If necessary, use a > 32-bit QEMU VM or a 32-bit chroot on a 64-bit host. > > -- > Walter Dnes <> waltd...@waltdnes.org> > > I don't run "desktop environments"; I run useful applications
