Re: current danger?

[Patrick Welche <prlw1%cam.ac.uk@localhost>]

On Fri, Mar 31, 2017 at 02:48:16PM +0100, Patrick Welche wrote:
> My -current/amd64 box is now toast:
> 
> - cvs update this morning 31 Mar 2017
> - boot with new kernel
> - sh build -E
> 
> build fails with something (from memory) along the lines of
> libc.so: unable to add symbol
> while running configure tests somewhere under external/gpl3 - binutils?
> 
> - cvs update -> the message I posted earlier
> - cvs diff -urHEAD doesn't turn anything up
> 
> compile helloworld.c gives unable to add symbol error
> 
> reboot machine:  panic on start as iwn0 can't read its firmware from /
> same for netbsd.old
> Can't disable iwn via boot -c as have usb keyboard
> 
> 
> Guessing: general filesystem corruption? (fancy M2 ssd chip)
> 
> (setting up netbooting...)

netbooted
fsck'd
copied vintage libc.so.12.206 -> /lib
booted netbsd.old (which should go with said libc)
try to compile hello world:
/usr/lib/libc.so: error adding symbols: File format not recognized

which file?

P