Automated report: NetBSD-current/i386 build failure
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 2019.10.10.23.37.13. An extract from the build.sh output follows: # compile MONOLITHIC/ar5112.o /tmp/bracket/build/2019.10.10.23.37.13-i386/tools/bin/i486--netbsdelf-gcc -msoft-float -mno-mmx -mno-sse -mno-avx -mindirect-branch=thunk -mindirect-branch-register -ffreestanding -fno-zero-initialized-in-bss -fno-delete-null-pointer-checks -O2 -fno-omit-frame-pointer -fstack-protector -Wstack-protector --param ssp-buffer-size=1 -fno-strict-aliasing -fno-common -std=gnu99 -Werror -Wall -Wno-main -Wno-format-zero-length -Wpointer-arith -Wmissing-prototypes -Wstrict-prototypes -Wold-style-definition -Wswitch -Wshadow -Wcast-qual -Wwrite-strings -Wno-unreachable-code -Wno-pointer-sign -Wno-attributes -Wextra -Wno-unused-parameter -Wold-style-definition -Wno-sign-compare --sysroot=/tmp/bracket/build/2019.10.10.23.37.13-i386/destdir -Di386 -I. -I/tmp/bracket/build/2019.10.10.23.37.13-i386/src/sys/external/bsd/acpica/dist -I/tmp/bracket/build/2019.10.10.23.37.13-i386/src/sys/external/bsd/libnv/dist -I/tmp/bracket/build/2019.10.10.23.37.13-i386/src/sys/../common/lib/libx86emu -I/tmp/bra cket/build/2019.10.10.23.37.13-i386/src/sys/../common/lib/libc/misc -I/tmp/bracket/build/2019.10.10.23.37.13-i386/src/sys/../common/include -I/tmp/bracket/build/2019.10.10.23.37.13-i386/src/sys/arch -I/tmp/bracket/build/2019.10.10.23.37.13-i386/src/sys -nostdinc -DCOMPAT_UTILS -DDIAGNOSTIC -DCOMPAT_44 -D_KERNEL -D_KERNEL_OPT -std=gnu99 -I/tmp/bracket/build/2019.10.10.23.37.13-i386/src/sys/lib/libkern/../../../common/lib/libc/quad -I/tmp/bracket/build/2019.10.10.23.37.13-i386/src/sys/lib/libkern/../../../common/lib/libc/string -I/tmp/bracket/build/2019.10.10.23.37.13-i386/src/sys/lib/libkern/../../../common/lib/libc/arch/i386/string -D_FORTIFY_SOURCE=2 -I/tmp/bracket/build/2019.10.10.23.37.13-i386/src/sys/external/isc/atheros_hal/dist -I/tmp/bracket/build/2019.10.10.23.37.13-i386/src/sys/external/isc/atheros_hal/ic -I/tmp/bracket/build/2019.10.10.23.37.13-i386/src/sys/external/bsd/common/include -I/tmp/bracket/build/2019.10.10.23.37.13-i386/src/sys/external/bsd/common/include -I/tmp/ bracket/build/2019.10.10.23.37.13-i386/src/sys/external/bsd/drm2/include -I/tmp/bracket/build/2019.10.10.23.37.13-i386/src/sys/external/bsd/drm2/include -I/tmp/bracket/build/2019.10.10.23.37.13-i386/src/sys/external/bsd/drm2/include/drm -I/tmp/bracket/build/2019.10.10.23.37.13-i386/src/sys/external/bsd/common/include -I/tmp/bracket/build/2019.10.10.23.37.13-i386/src/sys/external/bsd/drm2/dist/include -I/tmp/bracket/build/2019.10.10.23.37.13-i386/src/sys/external/bsd/drm2/dist/include/drm -I/tmp/bracket/build/2019.10.10.23.37.13-i386/src/sys/external/bsd/drm2/dist/uapi -I/tmp/bracket/build/2019.10.10.23.37.13-i386/src/sys/external/bsd/drm2/dist -D__KERNEL__ -DCONFIG_BACKLIGHT_CLASS_DEVICE=0 -DCONFIG_BACKLIGHT_CLASS_DEVICE_MODULE=0 -DCONFIG_DRM_FBDEV_EMULATION=1 -DCONFIG_FB=0 -I/tmp/bracket/build/2019.10.10.23.37.13-i386/src/sys/../common/include -I/tmp/bracket/build/2019.10.10.23.37.13-i386/src/sys/external/bsd/libnv/dist -I/tmp/bracket/build/2019.10.10.23.37.13-i386/src/sys/external /bsd/drm2/i915drm -I/tmp/bracket/build/2019.10.10.23.37.13-i386/src/sys/external/bsd/drm2/dist/drm/i915 -DCONFIG_DRM_I915_FBDEV=1 -DCONFIG_DRM_I915_PRELIMINARY_HW_SUPPORT=0 -DCONFIG_DRM_FBDEV_EMULATION=1 -I/tmp/bracket/build/2019.10.10.23.37.13-i386/src/sys/external/bsd/drm2/include/radeon -I/tmp/bracket/build/2019.10.10.23.37.13-i386/src/sys/external/bsd/drm2/radeon -I/tmp/bracket/build/2019.10.10.23.37.13-i386/src/sys/external/bsd/drm2/dist/drm/amd/include -I/tmp/bracket/build/2019.10.10.23.37.13-i386/src/sys/external/bsd/drm2/dist/drm/radeon -I/tmp/bracket/build/2019.10.10.23.37.13-i386/src/sys/external/bsd/drm2/dist/drm/nouveau -I/tmp/bracket/build/2019.10.10.23.37.13-i386/src/sys/external/bsd/drm2/dist/drm/nouveau/include -I/tmp/bracket/build/2019.10.10.23.37.13-i386/src/sys/external/bsd/drm2/dist/drm/nouveau/include/nvkm -I/tmp/bracket/build/2019.10.10.23.37.13-i386/src/sys/external/bsd/drm2/dist/drm/nouveau/nvkm -I/tmp/bracket/build/2019.10.10.23.37.13-i386/src/sys/external/b sd/drm2/nouveau -DCONFIG_NOUVEAU_DEBUG=5 -DCONFIG_NOUVEAU_DEBUG_DEFAULT=3 -I/tmp/bracket/build/2019.10.10.23.37.13-i386/src/sys/external/bsd/acpica/dist/include -c /tmp/bracket/build/2019.10.10.23.37.13-i386/src/sys/external/isc/atheros_hal/dist/ar5212/ar5112.c -o ar5112.o --- kern-GENERIC --- /tmp/bracket/build/2019.10.10.23.37.13-i386/tools/bin/nbctfconvert -g -L VERSION ar5210_reset.o --- ar5210_xmit.o --- # compile GENERIC/ar5210_xmit.o /tmp/bracket/build/2019.10.10.23.37.13-i386/tools/bin/i486--netbsdelf-gcc -msoft-float -mno-mmx -mno-sse -mno-avx -mindirect-branch=thunk -mindirect-branch-register
daily CVS update output
Updating src tree: P src/doc/3RDPARTY P src/external/bsd/ipf/dist/man/ipf.5 P src/lib/libc/net/Makefile.inc P src/lib/libc/resolv/Makefile.inc P src/lib/libc/rpc/Makefile.inc P src/sys/arch/x86/pci/if_vmx.c P src/sys/dev/pci/if_iwn.c P src/sys/dev/pcmcia/if_malo_pcmcia.c P src/sys/dev/raidframe/raidframevar.h P src/sys/dev/raidframe/rf_callback.c P src/sys/dev/raidframe/rf_callback.h P src/sys/dev/raidframe/rf_copyback.c P src/sys/dev/raidframe/rf_dag.h P src/sys/dev/raidframe/rf_dagdegrd.c P src/sys/dev/raidframe/rf_dagdegrd.h P src/sys/dev/raidframe/rf_dagdegwr.c P src/sys/dev/raidframe/rf_dagdegwr.h P src/sys/dev/raidframe/rf_dagffrd.c P src/sys/dev/raidframe/rf_dagffwr.c P src/sys/dev/raidframe/rf_dagffwr.h P src/sys/dev/raidframe/rf_dagfuncs.c P src/sys/dev/raidframe/rf_dagfuncs.h P src/sys/dev/raidframe/rf_dagutils.c P src/sys/dev/raidframe/rf_dagutils.h P src/sys/dev/raidframe/rf_desc.h P src/sys/dev/raidframe/rf_diskqueue.c P src/sys/dev/raidframe/rf_diskqueue.h P src/sys/dev/raidframe/rf_driver.c P src/sys/dev/raidframe/rf_engine.c P src/sys/dev/raidframe/rf_engine.h P src/sys/dev/raidframe/rf_evenodd_dagfuncs.c P src/sys/dev/raidframe/rf_evenodd_dagfuncs.h P src/sys/dev/raidframe/rf_evenodd_dags.c P src/sys/dev/raidframe/rf_netbsd.h P src/sys/dev/raidframe/rf_paritylog.c P src/sys/dev/raidframe/rf_paritylog.h P src/sys/dev/raidframe/rf_paritylogDiskMgr.c P src/sys/dev/raidframe/rf_paritylogDiskMgr.h P src/sys/dev/raidframe/rf_parityloggingdags.c P src/sys/dev/raidframe/rf_parityloggingdags.h P src/sys/dev/raidframe/rf_parityscan.c P src/sys/dev/raidframe/rf_parityscan.h P src/sys/dev/raidframe/rf_pq.c P src/sys/dev/raidframe/rf_pq.h P src/sys/dev/raidframe/rf_psstatus.c P src/sys/dev/raidframe/rf_psstatus.h P src/sys/dev/raidframe/rf_raid.h P src/sys/dev/raidframe/rf_raid1.c P src/sys/dev/raidframe/rf_reconbuffer.c P src/sys/dev/raidframe/rf_reconstruct.c P src/sys/dev/raidframe/rf_reconstruct.h P src/sys/dev/raidframe/rf_states.c P src/sys/dev/raidframe/rf_states.h P src/sys/dev/raidframe/rf_stripelocks.h P src/sys/dev/usb/if_urtwn.c P src/sys/kern/subr_asan.c P src/sys/sys/systm.h Updating xsrc tree: Killing core files: Updating file list: -rw-rw-r-- 1 srcmastr netbsd 42067337 Oct 11 03:03 ls-lRA.gz
Re: Can I use pkg_src to upgrade to current?
On Wed, Oct 09, 2019 at 06:18:16PM -0400, nottobay wrote:
> I'm new to BSD in general and coming from Linux. I tried pulling the
> binaries using the installer and it isn't working for me. Can I use pkg src
> to upgrade in place from release to current or do I have to build
> everything?
One thing to note about netbsd vs. a typical linux distro, is that
there's a separation between the "base" system and the package system.
The base system in netbsd is not managed via packages, it's a set of
tarballs to unpack in /.
You can get -current binaries in
https://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/
If you are on an amd64 system, fetch an updated kernel and modules at:
https://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/latest/amd64/binary/kernel/netbsd-GENERIC.gz
https://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/latest/amd64/binary/sets/modules.tar.xz
cp /netbsd /onetbsd for backup reasons
gunzip netbsd-GENERIC.gz; cp netbsd-GENERIC /netbsd
cd /; tar xJpf /path/to/modules.tar.xz
reboot, make sure the new kernel works.
Download the rest of the files in:
https://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/latest/amd64/binary/sets/
Unpack all of them in / ('tar xJpf') except etc.tar.xz. That one will
overwrite the passwords file.
Automated report: NetBSD-current/i386 build success
The NetBSD-current/i386 build is working again. The following commits were made between the last failed build and the successful build: 2019.10.10.08.37.16 kre src/lib/libc/net/Makefile.inc,v 1.90 2019.10.10.08.37.16 kre src/lib/libc/resolv/Makefile.inc,v 1.7 2019.10.10.08.37.16 kre src/lib/libc/rpc/Makefile.inc,v 1.25 2019.10.10.08.55.08 knakahara src/sys/arch/x86/pci/if_vmx.c,v 1.51 Log files can be found at: http://releng.NetBSD.org/b5reports/i386/commits-2019.10.html#2019.10.10.08.55.08
Re: Booting UEFI from GPT partition, how to denote the wedge?
from nottobay: > I'm new to BSD in general and coming from Linux. I tried pulling the > binaries using the installer and it isn't working for me. Can I use pkg src > to upgrade in place from release to current or do I have to build > everything? What do you have now? Did you install the release version? You can download, using cvs, the current src tree, and build the system using build.sh , and install over your release installation if desired. Tom
