So I was just reminded that I do still have a Xen server that's still
running the 8.99.32 kernel and Xen-4.11. I had not been testing on it
because it still of course has the vnd(4) CHS size bug (and because it's
also hosting my $HOME and /usr/src and I don't want to crash it), and I
had not
hi folks.
i've switched the alpha, amd64, sparc*, riscv*, ia64, and vax ports
have all been switched to GCC 10.
please send-pr or send email here about problems you encounter.
thanks.
.mrg.
Updating src tree:
P src/distrib/sets/lists/comp/mi
P src/external/bsd/top/dist/machine/m_netbsd.c
P src/external/gpl3/gcc/README.gcc10
P src/share/man/man9/Makefile
P src/share/misc/acronyms
P src/share/misc/acronyms.comp
P src/sys/arch/aarch64/aarch64/pmap.c
P src/sys/dev/cardbus/cardslot.c
P
The NetBSD-current/i386 build is working again.
The following commits were made between the last failed build and the
successful build:
2021.04.17.00.02.19 christos src/usr.bin/shlock/shlock.c,v 1.15
2021.04.17.00.05.31 mrg src/sys/kern/subr_evcnt.c,v 1.17
Logs can be found at:
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.16.22.41.12.
An extract from the build.sh output follows:
nbmake[7]: stopped in
At Fri, 16 Apr 2021 11:44:08 +0100, David Brownlee wrote:
Subject: Re: one remaining mystery about the FreeBSD domU failure on NetBSD
XEN3_DOM0
>
> On Fri, 16 Apr 2021 at 08:41, Greg A. Woods wrote:
>
> > What else is different? What am I missing? What could be different in
> > NetBSD current
The NetBSD-current/i386 build is working again.
The following commits were made between the last failed build and the
successful build:
2021.04.16.18.31.28 christos src/usr.bin/printf/printf.c,v 1.52
Logs can be found at:
Christos has committed a fix
On Fri, 16 Apr 2021, Chavdar Ivanov wrote:
#metoo
On Fri, 16 Apr 2021 at 19:22, Paul Goyette wrote:
With $SRCDIR updated on 2021-04-16 at 18:08:17 UTC I am seeing
...
# compile csh/printf.o
/build/netbsd-local/tools/x86_64/amd64/bin/x86_64--netbsd-gcc -O2
#metoo
On Fri, 16 Apr 2021 at 19:22, Paul Goyette wrote:
>
> With $SRCDIR updated on 2021-04-16 at 18:08:17 UTC I am seeing
>
> ...
> # compile csh/printf.o
> /build/netbsd-local/tools/x86_64/amd64/bin/x86_64--netbsd-gcc -O2 -fPIE -g
> -std=gnu99-Wall -Wstrict-prototypes
With $SRCDIR updated on 2021-04-16 at 18:08:17 UTC I am seeing
...
# compile csh/printf.o
/build/netbsd-local/tools/x86_64/amd64/bin/x86_64--netbsd-gcc -O2 -fPIE -g
-std=gnu99-Wall -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith
-Wno-sign-compare -Wsystem-headers
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.16.15.10.18.
An extract from the build.sh output follows:
--- dependall-share ---
nbmake[4]: stopped in
On Fri, 16 Apr 2021 at 08:41, Greg A. Woods wrote:
> What else is different? What am I missing? What could be different in
> NetBSD current that could cause a FreeBSD domU to (mis)behave this way?
> Could the fault still be in the FreeBSD drivers -- I don't see how as
> the same root problem
So I wrote a little awk script so that I could write 512-byte blocks
with varying values of bytes. (Awk is the only decent programming
language on the FreeBSD mini-memstick.img which I could think of that
would do something close to what I wanted it to do. I could have
combined awk+sh+dd and
13 matches
Mail list logo
