On Sun, Jun 14, 2026 at 02:05:59PM +0100, Jonathan Perkin wrote:
* On 2026-06-14 at 01:28 BST, Jonathan Perkin wrote:
> URL: https://reports.pkgci.org/SmartOS/upstream/trunk/20260613T194510Z/report.html
>
> Total: 29084 Platform: SmartOS 20260122T220528Z/x86_64
> Successful: 20528 Compiler: gcc-15.2.0
>
> Build Failures Breaks Maintainer
> ----------------------------------------------------------------------------
> netpbm-11.02.09nb8 1383 adam%NetBSD.org@localhost
> ghc-9.10.1nb7 641 pkgsrc-users%NetBSD.org@localhost
> python27-2.7.18nb22 246 pkgsrc-users%NetBSD.org@localhost
> pari-2.3.5nb33 243 pkgsrc-users%NetBSD.org@localhost
> ocaml-dune-3.23.1 169 pkgsrc-users%NetBSD.org@localhost
> SDL-1.2.15nb47 162 pkgsrc-users%NetBSD.org@localhost
> php56-5.6.40nb5 151 pkgsrc-users%NetBSD.org@localhost
> cyrus-sasl-2.1.28nb2 124 pkgsrc-users%NetBSD.org@localhost
> openjdk8-1.8.482nb2 107 pkgsrc-users%NetBSD.org@localhost
There doesn't seem to be a huge amount of interest in fixing up the GCC 15.x
issues exposed by these builds. Should I go back to GCC 14.x so that we
have higher package coverage for now?
Happy to go back to 15.x once NetBSD is closer to moving to it.
I'd prefer going back to GCC 14 for now, yes please.