Time to upgrade up from 9.x?

[Havard Eidnes <he%NetBSD.org@localhost>]

Hi,

as you may know, I'm doing pkgsrc bulk builds for NetBSD/powerpc
on some of my own macppc hosts.  My trusty old 9.0 build system
took a nosedive a while ago, and I've not managed to resurrect
it.  However, I recently upgraded my 8.0 system (no longer
supported via pkgsrc) to 9.0 with the intention of doing bulk
builds for that combination.  At about the same time I started a
bulk build on my 10.0 bulk build system.

However, looking at the status now, the 9.0 system has come way
further, it's up to

[11665/28443] Starting build of  gcc7-7.5.0nb6

while my 10.0 system is at

[2342/28443] Starting build of  rust-1.81.0

The reason the 9.0 system has come this far appears to be that
some fairly central packages failed to build, causing cascading
indirect-failed bulk build failures.  Among them:

cmake:

===> Creating toolchain wrappers for cmake-3.31.1
ERROR: heimdal>=0.4e heimdal>=0.6 is not installed; can't buildlink files.
*** Error code 1

gcc10:

xg++: internal compiler error: Cputime limit exceeded signal terminated program cc1plus

I had a 2h CPU limit, and have since doubled that for the next
go-around.  But ... seriously?  On a 1.5GHz ppc host?

icu:

normalizer2impl.cpp:1844:1: internal compiler error: Segmentation fault

The cmake problem surely must be a problem on other 9.x systems,
no?

However, the icu problem appears to be more problematical.  Some
might say that I should use another compiler.  First off, setting
that up is ... complicated.  Secondly, that compiler typically
needs to be used for all other c++ programs which use icu too,
and that quickly comes to "all c++ programs", and this would
make this build deviate too far from the default for me to be
comfortable publishing the result.

So ... the question then pops up "What to do with 9.x powerpc
with respect to pkgsrc support?"  One way to avoid that problem
would be to plan for an upgrade to a 10.x OS release.  Both 10.0
and 10.1 have been released, and my 10.0 bulk build system has
not stumbled over any problems with these packages, and is
currently building rust 1.81.0, which is at least using cmake.

Regards,

- Håvard