On Mon, Feb 09, 2026 at 03:28:40AM -0500, Kurt Mosiejczuk wrote: > 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.
Could you please share the panics you see. sparc64 has been very stable for me lately but I stopped using NFS and this helped a lot. I think there are still bugs lurking in the pmap code of sparc64 which we need to track down. > > > 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. Hmm. I never hit such an error in my bulks. Is awk using floating point internally? > > > 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 Is this a sparc64 only issue? -- :wq Claudio
