On Sat, Feb 07, 2026 at 10:53:06AM +0000, Stuart Henderson wrote: > > Build failures: 46
> I looked at some of these, obviously some are ports which don't work on > sparc64, but there are some which look like machine or OS problems, e.g. > > https://cranky.work/sparc64/2026-02-04/math/lapack.log > build stopped strangely, then when restarted with the same build dir > a .d file is corrupt I had two nodes kernel panic. This was going on one of the two nodes. > > https://cranky.work/sparc64/2026-02-04/net/ettercap,no_x11.log > -- Looking for strcasestr > CMake Error: Generator: execution of make failed. Make command was: > /usr/local/bin/ninja -v cmTC_49983 > -- Looking for strcasestr - not found > > https://cranky.work/sparc64/2026-02-04/net/ntp.log > config.status: creating ntpdate/Makefile > config.status: creating ntpdc/Makefile > awk: trying to access out of range field -2147483648 > input record number 1, file > source line number 316 > config.status: error: could not create ntpdc/Makefile Yeah. This is the classic sparc64 error I've been experiencing for years now. It also takes the form of mentions of NaN or perl crashing at a line of "Use X" where X is a normal perl version but has been munged into something even perl doesn't want to deal with. > > https://cranky.work/sparc64/2026-02-04/print/texlive/texmf.log > ===> Extracting for texlive-20250308-texmf > xz: (stdin): Compressed data is corrupt Yup. If I had caught it before it went out, one or more restarts might have gotten it to compile normally. > > https://cranky.work/sparc64/2026-02-04/sysutils/libvslvm.log > config.status: creating libvslvm.pc > awk: trying to access out of range field -2147483648 > input record number 1, file > source line number 364 > config.status: error: could not create libvslvm.pc Another error I'm betting comes from the same root cause is "panic: Unexpectedly didn't find a dot radix character in '-nan' at" some perl file --Kurt
