The NetBSD-current/i386 build is working again.
The following commits were made between the last failed build and the
successful build:
2021.04.14.02.45.40 christos src/sys/kern/makesyscalls.sh,v 1.185
2021.04.14.02.45.58 christos src/sys/kern/systrace_args.c,v 1.47
2021.04.14.02.48.0
At Tue, 13 Apr 2021 18:20:39 -0700, "Greg A. Woods" wrote:
Subject: Re: one remaining mystery about the FreeBSD domU failure on NetBSD
XEN3_DOM0
>
> So "17" seems an odd number, but it is apparently because of "Need to
> alloc one extra page to account for possible mapping offset".
Nope, changin
Updating src tree:
P src/external/apache2/mDNSResponder/usr.sbin/mdnsd/Makefile
P src/external/bsd/ntp/bin/ntpdc/Makefile
P src/external/bsd/ntp/lib/libntp/Makefile
P src/external/bsd/tmux/usr.bin/tmux/Makefile
P src/external/cddl/osnet/Makefile.inc
P src/external/cddl/osnet/Makefile.zfs
P src/ex
At Sun, 11 Apr 2021 13:55:36 -0700, "Greg A. Woods" wrote:
Subject: Re: one remaining mystery about the FreeBSD domU failure on NetBSD
XEN3_DOM0
>
> Definitely writing to a FreeBSD domU filesystem, i.e. to a FreeBSD
> xbd(4) with a new filesystem created on it, is impossible.
So, having run out
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2021.04.13.22.46.13.
An extract from the build.sh output follows:
nbmake[5]: stopped in /tmp/build/2021.04.13.22.46.
