Re: failure to build current on amd64

2020-01-08 Thread Riccardo Mottola
Hi Edgar, Edgar Pettijohn wrote: MKLLVM = NO MKLLVMRT = NO yet I think it is building it anyway Riccardo I built current yesterday no problem. I have tried the MKXXX=NO for lots of stuff and they always fail, so I'm not sure what the correct way to use them is. I think I was able to

userland build failure in libgomp

2020-01-08 Thread Riccardo Mottola
Hi, I updated again, did a new build of userland and now get an error in a different place. Seems the compiler doesn't like an attribute. It seems the compiler used is clang? But I have: MKLLVM = no HAVE_LLVM=no MKLLVMRT = no Riccardo # compile libgomp/oacc-init.o

Re: failure to build current on amd64

2020-01-08 Thread Edgar Pettijohn
On Jan 8, 2020 6:38 AM, Riccardo Mottola wrote: > > Hi! > > current fails do build userland for me: > > #   compile  libclangARCMigrate/Transforms.o > /usr/src/obj/tooldir.NetBSD-9.99.34-amd64/bin/x86_64--netbsd-c++ > -frandom-seed=dedfa0f2 -O2 -march=core2 -Werror -Wno-stringop-overflow >

daily CVS update output

2020-01-08 Thread NetBSD source update
Updating src tree: P src/distrib/utils/embedded/conf/rpi_inst.conf P src/doc/BRANCHES P src/external/bsd/tmux/dist/tmux.h P src/sbin/mount_procfs/mount_procfs.8 P src/share/mk/sys.mk P src/sys/arch/aarch64/aarch64/aarch64_machdep.c P src/sys/arch/aarch64/aarch64/cpuswitch.S P

Re: unable to boot amd64-uefi-install from USB stick on a MacBook2,1

2020-01-08 Thread Joerg Sonnenberger
On Wed, Jan 08, 2020 at 04:08:40PM -0800, Greg A. Woods wrote: > However in searching related things I just came across a reminder about > memory issues on this particular model of MacBook2,1. It originally > shipped with 2x1GB memory modules. At some point I upgraded it to 2x2GB > modules.

Re: unable to boot amd64-uefi-install from USB stick on a MacBook2,1

2020-01-08 Thread Greg A. Woods
At Wed, 11 Dec 2019 17:25:17 -0800, "Greg A. Woods" wrote: Subject: unable to boot amd64-uefi-install from USB stick on a MacBook2,1 > > However no matter which option I selected, including a "boot netbsd -vs" > from the boot prompt, would do anything more than load the kernel (I see > the

Automated report: NetBSD-current/i386 build failure

2020-01-08 Thread NetBSD Test Fixture
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 2020.01.08.18.47.43. An extract from the build.sh output follows: --- dependall-exec_aout --- ---

Re: panic on zpool create

2020-01-08 Thread David Brownlee
On Wed, 8 Jan 2020 at 02:51, Brian Buhrow wrote: > > hello David. I wonder if you're running into another manifestation > of kern/54724, which shows zfs corrupting kernel memory in NetBSD-9. I > show the problem having to do with xen, but I now believe the problem is > entirely with zfs

Re: CVS commit: pkgsrc/lang/nodejs

2020-01-08 Thread Joerg Sonnenberger
On Wed, Jan 08, 2020 at 04:04:31PM +0100, Adam wrote: > > Index: pkgsrc/lang/nodejs/patches/patch-deps_v8_src_zone_zone.h > > diff -u /dev/null > > pkgsrc/lang/nodejs/patches/patch-deps_v8_src_zone_zone.h:1.1 > > --- /dev/null Mon Jan 6 23:06:44 2020 > > +++

Re: CVS commit: pkgsrc/lang/nodejs

2020-01-08 Thread Adam
> Index: pkgsrc/lang/nodejs/patches/patch-deps_v8_src_zone_zone.h > diff -u /dev/null pkgsrc/lang/nodejs/patches/patch-deps_v8_src_zone_zone.h:1.1 > --- /dev/null Mon Jan 6 23:06:44 2020 > +++ pkgsrc/lang/nodejs/patches/patch-deps_v8_src_zone_zone.h Mon Jan 6 > 23:06:44 2020 > @@ -0,0 +1,18 @@

failure to build current on amd64

2020-01-08 Thread Riccardo Mottola
Hi! current fails do build userland for me: # compile libclangARCMigrate/Transforms.o /usr/src/obj/tooldir.NetBSD-9.99.34-amd64/bin/x86_64--netbsd-c++ -frandom-seed=dedfa0f2 -O2 -march=core2 -Werror -Wno-stringop-overflow -fPIE -march=core2 -std=c++14 -fno-rtti -fno-exceptions