Re: wm devices don't work under current amd64

2017-01-12 Thread Masanobu SAITOH
On 2016/11/28 17:16, Masanobu SAITOH wrote: Hello, Jarle. On 2016/11/27 0:45, Jarle Greipsland wrote: Masanobu SAITOH writes: Hi. On 2016/03/07 21:12, Tobias Nygren wrote: On Mon, 7 Mar 2016 20:57:02 +0900 Masanobu SAITOH wrote: One of the

Automated report: NetBSD-current/i386 build success

2017-01-12 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: 2017.01.13.03.01.09 kre src/tests/kernel/t_ptrace_wait.c,v 1.55 Log files can be found at:

daily CVS update output

2017-01-12 Thread NetBSD source update
Updating src tree: P src/crypto/external/bsd/openssl/lib/libcrypto/crypto.inc U src/external/broadcom/rpi-firmware/dist/bootcode.bin U src/external/broadcom/rpi-firmware/dist/fixup.dat U src/external/broadcom/rpi-firmware/dist/fixup_cd.dat U src/external/broadcom/rpi-firmware/dist/start.elf U

Re: -current MKTPM=1 build failure

2017-01-12 Thread Christos Zoulas
In article <03491b40-c370-dc50-af44-8a42d8e49...@spg.tu-darmstadt.de>, Hauke Fath wrote: >During a -current build with MKTPM=1, I have run into Go for it please! christosx > >[...] >--- tpm_nvread.o --- ># compile tpm_nvread/tpm_nvread.o

Automated report: NetBSD-current/i386 build failure

2017-01-12 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 2017.01.12.21.35.53. An extract from the build.sh output follows:

Re: -current MKTPM=1 build failure

2017-01-12 Thread coypu
Please put sys/stat.h first though. (as per share/misc/style) otherwise lgtm, xtos had to add dozens of these.

Automated report: NetBSD-current/i386 build success

2017-01-12 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: 2017.01.12.18.16.52 christos src/lib/libc/gen/syslog.c,v 1.58 2017.01.12.18.16.52 christos src/lib/libc/include/namespace.h,v 1.184

rnd entropy estimate running low?

2017-01-12 Thread Havard Eidnes
Hi, on a couple of arm boxes I have I've been observing the development of the entropy estimate, what "rndctl -s" calls "bits currently stored in pool" over time. I've also tried to read some of the code to understand the behaviour. If I understand correctly, randomness sources come in two

ODROID-C1 networking problems?

2017-01-12 Thread Havard Eidnes
Hi, I have a couple of ODROID C1 boxes. One of them appear to have intermittent networking problems, in particular with receiving packets. droid# uname -a NetBSD droid.urc.uninett.no 7.99.58 NetBSD 7.99.58 (ODROID-C1) #0: Thu Jan 12 10:12:54 CET 2017

Automated report: NetBSD-current/i386 build failure

2017-01-12 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 2017.01.12.17.19.17. An extract from the build.sh output follows: #define snprintf _snprintf ^ In file

-current MKTPM=1 build failure

2017-01-12 Thread Hauke Fath
During a -current build with MKTPM=1, I have run into [...] --- tpm_nvread.o --- # compile tpm_nvread/tpm_nvread.o /var/tmp/netbsd-builds/developer/amd64/tools/bin/x86_64--netbsd-gcc -O2 -fPIE-std=gnu99 -Werror --sysroot=/var/tmp/netbsd-builds/developer/amd64/destdi

Re: clang/llvm build failure

2017-01-12 Thread Joerg Sonnenberger
On Wed, Jan 11, 2017 at 04:11:24PM -0800, bch wrote: > [...] > x86_64--netbsd-gcc: error: > /usr/src/external/bsd/llvm/lib/libLLVMSupport/../../dist/llvm/lib/Support/ConvertUTF.c: > No such file or directory > x86_64--netbsd-gcc: fatal error: no input files > compilation terminated. > nbmkdep: