I build amd64 and i386 -current overnight using pkgsrc/sysutils/sysbuild via a cron job: ... $ crontab -l # $NetBSD: crontab,v 1.1 2012/07/25 12:20:08 jmmv Exp $ # crontab(5) file for the unprivileged sysbuild user.
PATH=/usr/pkg/bin:/usr/pkg/sbin:/usr/bin:/usr/sbin:/bin:/sbin SHELL=/bin/sh # Cheatsheet: minute hour day-of-month month day-of-week(0,7=Sun) @daily /usr/pkg/bin/sysbuild4cron -l "${HOME}/log" -- build ... Lately it breaks regularly, sometimes without any error message - in the morning the log ends halfway through, there are no processes running; on the other hand sometimes I get stuff like this night: ... # compile huntd/expl.o /home/sysbuild/Sysbuild/amd64/tools/bin/x86_64--netbsd-gcc -O2 -std=gnu99 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wpoi nter-arith -Wno-sign-compare -Wno-traditional -Wa,--fatal-warnings -Wreturn-type -Wswitch -Wshadow -Wcast-qual -Wwrite-strings -Wextra -Wno-unused-parameter -Wno-sign-compare -Wold-style-definition -Wsign-compare -Wformat=2 -Wno-format-zero-length -We rror -DRANDOM -DREFLECT -DMONITOR -DOOZE -DFLY -DVOLCANO -DBOOTS -DOTTO -DINTERNET -DLOG -DHUNTD=\"/usr/games/huntd\" --sys root=/home/sysbuild/Sysbuild/amd64/destdir -c /home/sysbuild/src/games/hunt/huntd/expl.c sh: Cannot vfork *** [expl.o] Error code 2 ... Looks like some limits have been changed recently - if I run interactively as the same sysbuild user, it completes without any problem (as it did yesterday afternoon). (the first system I tend to upgrade after successful build is the build host itseld, so ATM it is running: [log] uname -a NetBSD support6.delcam.local 6.99.28 NetBSD 6.99.28 (MINE) #37: Tue Dec 10 16:02:16 GMT 2013 root@support6.delcam.local:/root/a64/compile/MINE amd64 (MINE is XEN3_DOMU with a single line change - the root is on xbd1a (don't ask why). I'll try overnight to double the memory to see if it will make difference. Chavdar On 13 December 2013 12:30, Thomas Mueller <mueller6...@bellsouth.net> wrote: >> Since -current had some "hard times" in the last few weeks, and maybe >> not everyone is aware of this site: > >> http://releng.netbsd.org/cgi-bin/builds.cgi > >> shows the status of the last autobuilds. We already had one working >> -current (HEAD) build this week, yay! > >> As you can see there, the stable branches rarely fail to build. When >> they do, it either is a spurious problem of the autobuild system (e.g. >> running out of disk space), or a broken pullup, that will usualy be >> fixed within a few hours. > >> If you try to build one of the stable branches locally (from clean >> source trees and empty obj dir), and fail, this either is a clear >> failure in the "tools" phase (e.g. when you build on some host system >> that hasn't been tested lately), in this case: file a PR. >> Or: you are passing some "strange" options to build.sh, e.g. an inconsistent >> or not supported mixture of MK...=YES/NO flags. You should not fiddle with >> those flags normally, unless you clearly understand all implications and >> are willing to fix the fallout. > >> Martin > >> I still don't understand what you're trying to do, or why you're >> apparently surprised it doesn't work. > > -- >> David A. Holland >> dholl...@netbsd.org > > I've been following that website consistently for many months. > > Most of the time, even recently, HEAD built successfully for amd64 and i386. > > I keep getting Internal compiler error, segmentation fault when using base > gcc, > without any strange or fancy stuff in build.sh command. > > Possibly with gcc not being upgraded while mpc, mpfr and gmp have been (?), > something is out of sync? But I was able to build lang/clang and also gcc48 > and gcc-aux from pkgsrc, so I thought maybe not rebuild base gcc. > > But there was another suggestion to put -std=c++0x or -std=gnu++0x , and I > wanted to know where to do that for build.sh . > > I updated NetBSD 6.1_STABLE on other computer, and for the first time, was > successful booting on MSI Z77 MPOWER motherboard. Maybe the result of five > months of improvements? > > Tom > -- ----