local builds break "devel/gobject-introspection" et al.

2016-08-02 Thread John D. Baker
I've been beating my head against the wall that is pkg/51266 trying to figure out what's broken for me but apparently no-one else. I seem to have hit upon a pattern, sort of: Start with the host OS installed from a TNF snapshot of -current for either i386 or amd64 and no packages installed.

daily CVS update output

2016-08-02 Thread NetBSD source update
Updating src tree: P src/crypto/external/bsd/openssh/bin/ssh/Makefile P src/crypto/external/bsd/openssh/dist/PROTOCOL P src/crypto/external/bsd/openssh/dist/PROTOCOL.agent P src/crypto/external/bsd/openssh/dist/PROTOCOL.certkeys P src/crypto/external/bsd/openssh/dist/PROTOCOL.chacha20poly1305 P

Re: drmkms panic

2016-08-02 Thread coypu
On Tue, Aug 02, 2016 at 07:04:14PM +, co...@sdf.org wrote: > On Tue, Aug 02, 2016 at 08:58:56PM +0200, Stefan Hertenberger wrote: > > Hello, > > > > i hope this dump's are more useful, latest sources compiled with debug > > symbols. > > > > https://www.alarum.de/netbsd/netbsd.2.gz > >

Re: drmkms panic

2016-08-02 Thread Swift Griggs
On Tue, 2 Aug 2016, co...@sdf.org wrote: > The problem is pretty obvious. netbsd kmem_alloc doesn't like allocating > zero-sized things, whereas linux kmalloc does. Please, forgive my ignorance, I'm just asking out of curiosity. However, if kmalloc() isn't available at all what happened during

Re: drmkms panic

2016-08-02 Thread coypu
On Tue, Aug 02, 2016 at 08:58:56PM +0200, Stefan Hertenberger wrote: > Hello, > > i hope this dump's are more useful, latest sources compiled with debug > symbols. > > https://www.alarum.de/netbsd/netbsd.2.gz > https://www.alarum.de/netbsd/netbsd.2.core.gz > > the kernel with debug symbols, not

drmkms panic

2016-08-02 Thread Stefan Hertenberger
Hello, i hope this dump's are more useful, latest sources compiled with debug symbols. https://www.alarum.de/netbsd/netbsd.2.gz https://www.alarum.de/netbsd/netbsd.2.core.gz the kernel with debug symbols, not sure this is needed https://www.alarum.de/netbsd/netbsd.gdb.gz regards, Stefan

Automated report: NetBSD-current/i386 build success

2016-08-02 Thread NetBSD Test Fixture
The NetBSD-current/i386 build is working again. The following commits were made between the last failed build and the successful build: 2016.08.02.14.54.03 jakllsch src/distrib/sets/lists/base/shl.mi,v 1.779 2016.08.02.14.54.03 jakllsch src/distrib/sets/lists/debug/shl.mi,v 1.139 Log

Automated report: NetBSD-current/i386 build failure

2016-08-02 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 2016.08.02.14.21.53. An extract from the build.sh output follows: postinstall fixes failed: