daily CVS update output
Updating src tree: P src/external/cddl/osnet/dist/uts/common/fs/zfs/dnode.c P src/external/cddl/osnet/dist/uts/common/fs/zfs/zfs_vnops.c P src/lib/libnpf/Makefile P src/lib/npf/mod.mk P src/libexec/identd/Makefile P src/sys/arch/arm/arm32/bus_dma.c P src/sys/compat/linux/common/linux_misc.c P src/sys/compat/linux/common/linux_socket.c P src/sys/compat/linux/common/linux_socket.h P src/sys/dev/pci/pcidevs P src/sys/dev/pci/pcidevs.h P src/sys/dev/pci/pcidevs_data.h P src/sys/dev/sdmmc/sdmmcdevs P src/sys/dev/sdmmc/sdmmcdevs.h P src/sys/dev/usb/usbdi.c P src/usr.bin/audiocfg/audiocfg.1 P src/usr.bin/audiocfg/audiodev.c P src/usr.bin/audiocfg/audiodev.h P src/usr.bin/audiocfg/dtmf.c P src/usr.bin/audiocfg/main.c P src/usr.sbin/npf/npfctl/Makefile P src/usr.sbin/npf/npfd/Makefile Updating xsrc tree: Killing core files: Updating file list: -rw-rw-r-- 1 srcmastr netbsd 43165135 Aug 25 03:04 ls-lRA.gz
Re: amd64 build failed: constructor priorities from 0 to 100 are reserved
On 24.08.2019 10:08, Thomas Klausner wrote: > On Sat, Aug 24, 2019 at 08:49:59AM +0200, Thomas Klausner wrote: >> On Fri, Aug 23, 2019 at 04:19:25PM +0200, Kamil Rytarowski wrote: >>> I will try to reproduce and fix it. >> >> I saw you committed a fix, I'll test it now. > > I now see > > --- install-tsan_cxx-m64 --- > x86_64--netbsd-install: libclang_rt.tsan_cxx-x86_64.a.syms: stat: No such > file or directory > > Thomas > I will try to reproduce and fix. signature.asc Description: OpenPGP digital signature
Re: amd64 build failed: constructor priorities from 0 to 100 are reserved
On Sat, Aug 24, 2019 at 08:49:59AM +0200, Thomas Klausner wrote: > On Fri, Aug 23, 2019 at 04:19:25PM +0200, Kamil Rytarowski wrote: > > I will try to reproduce and fix it. > > I saw you committed a fix, I'll test it now. I now see --- install-tsan_cxx-m64 --- x86_64--netbsd-install: libclang_rt.tsan_cxx-x86_64.a.syms: stat: No such file or directory Thomas
Re: Can't set volume options during install?
On Sat, Aug 24, 2019 at 07:56:16AM +0700, Robert Elz wrote: > | Besides, only disklabel provides storage for this data, > > Huh? What is being discussed here? I assumed it was the makefs > parameters that get used (and yes, two of those do get inserted in > the a bsd disklabel, though I have never been sure why - does anything > actually use those values?) The old code even showed the values very prominently (and this part was not generalizable). I'll do something about it, but maybe differently than suggested yesterday and only "volatile", i.e. not even saving the settings for disklabel partitioned disks. I'll send an update with details when done. Martin
