Automated report: NetBSD-current/i386 build failure

2018-08-18 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 2018.08.18.09.00.28. An extract from the build.sh output follows: --- dependall-libexec --- /tmp/bracket/build/2

usbdevices.config

2018-08-18 Thread Patrick Welche
With the introduction of usbdevices.config, the old procedure of "copy GENERIC to NEWCOMPUTER and comment out what isn't needed" doesn't really work any more. What's the thinking on The New Way(tm)? Cheers, Patrick

Re: usbdevices.config

2018-08-18 Thread Michael van Elst
pr...@cam.ac.uk (Patrick Welche) writes: >With the introduction of usbdevices.config, the old procedure of "copy >GENERIC to NEWCOMPUTER and comment out what isn't needed" doesn't really >work any more. What's the thinking on The New Way(tm)? It stopped working for some platforms a long time ago

Re: usbdevices.config

2018-08-18 Thread Rhialto
On Sat 18 Aug 2018 at 11:51:20 -, Michael van Elst wrote: > pr...@cam.ac.uk (Patrick Welche) writes: > > >With the introduction of usbdevices.config, the old procedure of "copy > >GENERIC to NEWCOMPUTER and comment out what isn't needed" doesn't really > >work any more. What's the thinking on

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

2018-08-18 Thread Andreas Gustafsson
The NetBSD Test Fixture wrote: > --- dependall-libexec --- > /tmp/bracket/build/2018.08.18.09.00.28-i386/destdir/usr/lib/libssl.so: > undefined reference to `conf_ssl_get' > /tmp/bracket/build/2018.08.18.09.00.28-i386/destdir/lib/libcrypto.so: > undefined reference to `conf_add_ssl_mo

Re: usbdevices.config

2018-08-18 Thread Michael van Elst
rhia...@falu.nl (Rhialto) writes: >adv*at pci? dev ? function ?# AdvanSys 1200[A,B], 9xx[U,UA] >SCSI >to >no adv*at pci? # dev ? function ?# AdvanSys 1200[A,B], 9xx[U,UA] >SCSI It's usually enough to write: no adv unless you want to keep the driver and just drop its PC

Re: usbdevices.config

2018-08-18 Thread Patrick Welche
On Sat, Aug 18, 2018 at 03:15:21PM -, Michael van Elst wrote: > So for me, stripping a copy of GENERIC ended in more work for each update > than using no phrases. I would cp GENERIC MYCOMPUTER and comment out the lines I didn't want when bring the new box into service, and then ident MYCOMPU

Automated report: NetBSD-current/i386 build success

2018-08-18 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: 2018.08.18.17.37.25 kre src/crypto/external/bsd/openssl/lib/libcrypto/crypto.map,v 1.2 Log files can be found at: http://releng.NetBSD.org/b5reports/

daily CVS update output

2018-08-18 Thread NetBSD source update
Updating src tree: P src/bin/sh/mknodenames.sh P src/crypto/external/bsd/openssl/dist/.gitignore P src/crypto/external/bsd/openssl/dist/.travis.yml P src/crypto/external/bsd/openssl/dist/CHANGES P src/crypto/external/bsd/openssl/dist/CONTRIBUTING P src/crypto/external/bsd/openssl/dist/Configure P

Re: Redoing the code in /bin/sh to handle the issues in PR bin/48875

2018-08-18 Thread J. Lewis Muir
On 08/18, Robert Elz wrote: > Does this actually help, or is all this text just making it less likely that > the average script writer will ever read any of it? I see your point. Yes, this seems too long. Maybe it would be more appropriate in the POSIX sh shell book you were planning to write.