Automated report: NetBSD-current/i386 build failure

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 2018.02.16.04.50.19. An extract from the build.sh output follows: postinstall-fix-obsolete_stand ===> . ---

daily CVS update output

Updating src tree: P src/external/gpl3/gcc.old/dist/libsanitizer/asan/asan_linux.cc P src/sys/arch/aarch64/include/mcontext.h P src/sys/arch/alpha/include/mcontext.h P src/sys/arch/amd64/include/mcontext.h P src/sys/arch/arm/include/mcontext.h P src/sys/arch/hppa/include/mcontext.h P

OpenSSL in ruby and packages

Hi, After update (but apparently I got yesterday a source too late so that I need to update again?) I am updating packages too and get for ruby 2.3.6: --- objspace_dump.o --- compiling objspace_dump.c --- ../../.ext/x86_64-netbsd/objspace.so --- linking shared-object objspace.so ---

Automated report: NetBSD-current/i386 build success

The NetBSD-current/i386 build is working again. The following commits were made between the last failed build and the successful build: 2018.02.15.19.02.06 christos src/external/gpl3/gcc.old/dist/libsanitizer/asan/asan_linux.cc,v 1.4 2018.02.15.19.05.10 uwe

Re: dhcpd

On Sat, Feb 10, 2018 at 04:56:31PM +, Patrick Welche wrote: > After updating to today's -current, my dhcpd fails to start, with: > > "Can't initialize context: failure" > > dhcpd.conf hasn't changed in a long time. Thoughts on what might have > changed? (Oddly ktrace seems to show

Automated report: NetBSD-current/i386 build failure

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 2018.02.15.15.53.57. An extract from the build.sh output follows:

Re: dhcpd, dig and new openssl

On Thu, Feb 15, 2018 at 10:49:44AM +, Robert Swindells wrote: > > Martin Husemann wrote: > >On Thu, Feb 15, 2018 at 08:57:16AM +, Robert Swindells wrote: > >> > > >> >(Am I the only one seeing this.) > >> > >> named and nslookup look to be broken too. > > > >Hasn't

Re: dhcpd, dig and new openssl

Hi, Martin Husemann wrote: Hasn't this been fixed yesterday or the day before? With the sources of yesterday I see: disc$ dig -h 15-Feb-2018 15:31:56.330 ENGINE_by_id failed (crypto failure) 15-Feb-2018 15:31:56.341 error:25070067:DSO support routines:DSO_load:could not load the shared

Re: dhcpd, dig and new openssl

Martin Husemann wrote: >On Thu, Feb 15, 2018 at 08:57:16AM +, Robert Swindells wrote: >> > >> >(Am I the only one seeing this.) >> >> named and nslookup look to be broken too. > >Hasn't this been fixed yesterday or the day before? Yes, ryoon fixed it yesterday. I had

Re: dhcpd, dig and new openssl

On Thu, Feb 15, 2018 at 08:57:16AM +, Robert Swindells wrote: > > > >(Am I the only one seeing this.) > > named and nslookup look to be broken too. Hasn't this been fixed yesterday or the day before? Martin

Re: dhcpd, dig and new openssl

Patrick Welche wrote: >Can any of you run > > dhcpd > dig -h > >successfully on a recent -current? > >(Am I the only one seeing this.) named and nslookup look to be broken too.

dhcpd, dig and new openssl

Can any of you run dhcpd dig -h successfully on a recent -current? (Am I the only one seeing this.) Cheers, Patrick