-current build failure in compiler_rt/dist/lib/msan/msan_interceptors.cc

2019-10-22 Thread Thomas Klausner
Hi! Yesterday evening's current with: build.sh -j 32 -x -V MKDEBUG=yes -V MKDEBUGLIB=yes -V MKLLVM=yes -T /usr/obj/tools.gcc -m amd64 -O /usr/obj/src.amd64 -D /usr/obj/amd64.gcc.20191022 -R /usr/obj/amd64.gcc.20191022.release distribution gives me: --- msan_interceptors.o --- In file

daily CVS update output

2019-10-22 Thread NetBSD source update
Updating src tree: P src/distrib/sets/lists/xcomp/mi U src/distrib/sets/lists/xetc/md.x68k P src/distrib/sets/lists/xetc/mi P src/share/mk/bsd.own.mk P src/sys/arch/arm/dts/socfpga_cyclone5_de0_nano_soc.dts P src/sys/arch/arm/imx/fdt/imx6_platform.c P src/sys/dev/ic/ssdfb.c P

Converting termcap entries to terminfo entries

2019-10-22 Thread Brian Buhrow
hello. I'm in the process of building NetBSD-9.0 systems in an effort to consider upgrading from my fleet of NetBSD-5.2 systems to NetBSD-9. As a long time window(1) user, I have a termcap entry for the window terminal type that I use on systems that I ssh into from window(1) panes. It

heads-up: planned changes in nvmm

2019-10-22 Thread Maxime Villard
[I am not subscribed to this list, so if you want to answer, make sure to CC me.] I will soon commit a set of changes in NVMM, which will require a full rebuild and reinstallation of: the kernel NVMM driver, the libnvmm API, the libnvmm ATF tests, and the qemu-nvmm package if you're using it.

Re: Tar extract behaviour changed

2019-10-22 Thread Joerg Sonnenberger
On Tue, Oct 22, 2019 at 08:00:35PM +0200, Christian Groessler wrote: > "tar" had an option to delete files which it is about to extract before > extraction. Wouldn't this solve the "symlink" issue at hand? What am I > missing? See the SECURITY section in the man page. Both -U and -P are ways to

Re: Tar extract behaviour changed

2019-10-22 Thread Christian Groessler
On 2019-10-22 17:43, Robert Elz wrote: Date:Tue, 22 Oct 2019 14:33:27 - (UTC) From:chris...@astron.com (Christos Zoulas) Message-ID: | Well, one of the use cases is when we don't have enough disk space in the | same partition, so that will not work

Re: Failure to build current tools amd64

2019-10-22 Thread Riccardo Mottola
Hi! Update: it was an update build that did not work. Retrying without -u and waiting for some time... succeeded. I hate that :) Riccardo Riccardo Mottola wrote: Hi all! I did update CVS yesterday and started a nice build from tools, but it fails with: (upgrade unprivileged build)

undefined reference in system library on netbsd-9/sparc

2019-10-22 Thread John D. Baker
Building "sysutils/apcupsd" on NetBSD/sparc-9.0_BETA fails linking with: [...] LDsrc/apcupsd ld: /usr/lib/libsupc++.a(eh_throw.o):(.text+0x78): undefined reference to `__gnu_cxx::__exchange_and_add(int volatile*, int)' I have an old binary package from the last time I built apcupsd on

Re: Tar extract behaviour changed

2019-10-22 Thread Robert Elz
Date:Tue, 22 Oct 2019 14:33:27 - (UTC) From:chris...@astron.com (Christos Zoulas) Message-ID: | Well, one of the use cases is when we don't have enough disk space in the | same partition, so that will not work out. No, I meant symlinks in the archive, not

Re: Tar extract behaviour changed

2019-10-22 Thread Christos Zoulas
In article <19306.1571753...@jinx.noi.kre.to>, Robert Elz wrote: >Date:Tue, 22 Oct 2019 14:27:39 +0200 >From:Joerg Sonnenberger >Message-ID: <20191022122739.ga86...@bec.de> > > | Extraction of entries in streamable formats happens in isolation. The > | archiver

Re: Tar extract behaviour changed

2019-10-22 Thread Joerg Sonnenberger
On Tue, Oct 22, 2019 at 07:26:05AM +0200, Martin Husemann wrote: > On Tue, Oct 22, 2019 at 06:37:44AM +0700, Robert Elz wrote: > > Date:Mon, 21 Oct 2019 21:20:25 +0200 > > From:Joerg Sonnenberger > > Message-ID: <20191021192025.ga33...@bec.de> > > > > | That said,

Re: Tar extract behaviour changed

2019-10-22 Thread Christos Zoulas
In article <20191022052605.ga...@mail.duskware.de>, Martin Husemann wrote: >On Tue, Oct 22, 2019 at 06:37:44AM +0700, Robert Elz wrote: >> Date:Mon, 21 Oct 2019 21:20:25 +0200 >> From:Joerg Sonnenberger >> Message-ID: <20191021192025.ga33...@bec.de> >> >> | That

Re: -current panics on boot in atabus_alloc_drives()

2019-10-22 Thread Christos Zoulas
Thanks, looks like some drivers probe channels without holding the channel lock. Should be easy to fix. christos > On Oct 22, 2019, at 3:56 AM, Andreas Gustafsson wrote: > > Christos, > > Both i386 and amd64 are failing to install on the testbed due to the > install kernel panicing on boot.

-current panics on boot in atabus_alloc_drives()

2019-10-22 Thread Andreas Gustafsson
Christos, Both i386 and amd64 are failing to install on the testbed due to the install kernel panicing on boot. The amd64 console log contains a backtrace: [ 1.0264751] panic: lock error: Mutex: mutex_vector_exit,742: exiting unheld spin mutex: lock 0xc83161f0 cpu 0 lwp

Re: Tar extract behaviour changed

2019-10-22 Thread J. Hannken-Illjes
-- J. Hannken-Illjes - hann...@eis.cs.tu-bs.de - TU Braunschweig > On 22. Oct 2019, at 07:26, Martin Husemann wrote: > > The current state silently breaks existing valid setups ("valid" of course > in my view, as I personally ran into one that I created myself). It breaks chrooted services,

Failure to build current tools amd64

2019-10-22 Thread Riccardo Mottola
Hi all! I did update CVS yesterday and started a nice build from tools, but it fails with: (upgrade unprivileged build) ./build.sh -U -u tools [...] c++ -fno-PIE -c  -DIN_GCC_FRONTEND -O -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE   -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall