Re: Automated report: NetBSD-current/i386 build failure

2016-07-16 Thread Paul Goyette
Actually this should already be fixed by src/sys/net/bpf.c,v 1.202 On Sun, 17 Jul 2016, NetBSD Test Fixture wrote: 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

Re: Automated report: NetBSD-current/i386 build failure

2016-07-16 Thread Paul Goyette
It's mine - I'm working on it ... On Sun, 17 Jul 2016, NetBSD Test Fixture wrote: 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.07.17.02.02.01. An extract

daily CVS update output

2016-07-16 Thread NetBSD source update
Updating src tree: P src/external/cddl/osnet/dev/fbt/fbt.c P src/external/cddl/osnet/dev/sdt/sdt.c P src/external/cddl/osnet/dist/uts/common/dtrace/dtrace.c P src/lib/libc/arch/hppa/gen/__setjmp14.S P src/lib/libpthread/pthread_mutex.c P src/sys/arch/amd64/amd64/machdep.c P

Re: current build failure automated messages

2016-07-16 Thread Andreas Gustafsson
Robert Elz wrote: > From time to time there are messages to current-users about > build failures (the messages are generally useful even if sometimes > the content - just what failed - can be most obscure ... but that's > not the point of this message.) > > I was wondering if it would be possible

current build failure automated messages

2016-07-16 Thread Robert Elz
>From time to time there are messages to current-users about build failures (the messages are generally useful even if sometimes the content - just what failed - can be most obscure ... but that's not the point of this message.) I was wondering if it would be possible to also send "build now