Log message:
go119, go121: remove

go124 is the current version. go123 is still supported.

To build go124 from source, the chain is
go14 - go118 - go120 - go122 - go124

Thus, nothing needs go119 and go121.

agreed by maya@ on tech-pkg

Log message:
Update go123 to 1.23.8 and go124 to 1.24.2

These minor releases include 1 security fixes following the security policy:

-   net/http: request smuggling through invalid chunked data

    The net/http package accepted data in the chunked transfer encoding
    containing an invalid chunk-size line terminated by a bare LF.
    When used in conjunction with a server or proxy which incorrectly
    interprets a bare LF in a chunk extension as part of the extension,
    this could permit request smuggling.

    The net/http package now rejects chunk-size lines containing a bare LF.

    Thanks to Jeppe Bonde Weikop for reporting this issue.

    This is CVE-2025-22871 and Go issue https://go.dev/issue/71988.

View the release notes for more information.

Log message:
lang/go: Set GOMAXPROCS according to MAKE_JOBS.

Even though we set MAKE_JOBS_SAFE=no in go-module.mk (not really sure
why, wish we had a comment giving a reason!), golang itself may run
multiple threads internally up to the number of CPUs it finds unless
we sternly instruct it not to abuse resources it wasn't offered by
setting GOMAXPROCS.

Log message:
go123: update to 1.23.7 (security)

go1.23.7 (released 2025-03-04) includes security fixes to the net/http
package, as well as bug fixes to cgo, the compiler, and the reflect,
runtime, and syscall packages. See the Go 1.23.7 milestone on our issue
tracker for details.

Log message:
go124: update to 1.24.1 (security)

go1.24.1 (released 2025-03-04) includes security fixes to the net/http
package, as well as bug fixes to cgo, the compiler, the go command, and
the reflect, runtime, and syscall packages. See the Go 1.24.1 milestone
on our issue tracker for details.

Log message:
go: flip the default version to 1.24.

In a bulk build (bulk-test-go) on NetBSD-current/amd64, I found zero
packages with breakage. That's a first in a Go compiler update!

Log message:
go124: new package for 1.24.0, from wip.

The latest Go release, version 1.24, arrives six months after Go 1.23.
Most of its changes are in the implementation of the toolchain, runtime,
and libraries. As always, the release maintains the Go 1 promise of
compatibility. We expect almost all Go programs to continue to compile
and run as before.

Go 1.24 now fully supports generic type aliases: a type alias may be
parameterized like a defined type.

Go modules can now track executable dependencies using tool directives
in go.mod.

Several performance improvements to the runtime have decreased CPU
overheads by 2-3% on average across a suite of representative
benchmarks. Results may vary by application. These improvements include
a new builtin map implementation based on Swiss Tables, more efficient
memory allocation of small objects, and a new runtime-internal mutex
implementation.

Log message:
Update go122 to 1.22.12 and go123 to 1.23.6.

This is a security update but it only applies on the ppc64le platform.

These minor releases include 1 security fix following the security policy:

-   crypto/elliptic: timing sidechannel for P-256 on ppc64le

    Due to the usage of a variable time instruction in the assembly
    implementation of an internal function, a small number of bits of secret
    scalars are leaked on the ppc64le architecture. Due to the way this
    function is used, we do not believe this leakage is enough to allow
    recovery of the private key when P-256 is used in any well known
    protocols.

    This is CVE-2025-22866 and Go issue https://go.dev/issue/71383.

Log message:
lang/go: Add cross-build support.

This adds cross-build support for lang/go123 and for the Go-related
infrastructure in pkgsrc.  (We could do older versions of Go too with
a little more work.)

Noteworthy changes that are not conditional on USE_CROSS_COMPILE:

1. lang/go/version.mk is rearranged to be more data-driven than
   conditional-driven.  Making it data-driven makes it easier to
   define both GOARCH and GOHOSTARCH from the same tables when
   MACHINE_ARCH and NATIVE_MACHINE_ARCH are not the same.

   This is a likely source of broken edge cases.  I went through the
   old conditional logic and hand-checked all the conditions but I
   could have made a mistake.

2. go-module.mk and go-package.mk define GOPATH_BIN to be `bin' for
   native builds, and `bin/${GO_PLATFORM}' for cross builds -- this
   is the subdirectory of GOPATH where the Go toolchain puts binaries
   so that packages with custom do-install targets can avoid any need
   for USE_CROSS_COMPILE conditionals.

   The default do-install targets use pax slightly differently now to
   avoid the need for USE_CROSS_COMPILE conditionals.  I think the
   logic is equivalent for native builds but this is worth reviewing.

3. lang/go123 no longer depends on bash and Perl at runtime.  As far
   as I can tell, this was just a kludge to pacify check-interpreter
   complaints in the copy of the source code that Go ships under
   ${PREFIX}/go123/src.  We don't need to replace the interpreter at
   build-time -- most of these scripts are not run at all during the
   build, and the handful that remain (make.bash, run.bash) are run
   with ${BASH}.  Instead, we CHECK_INTERPRETER_SKIP them in the
   installed copy of the source code.

Proposed on tech-pkg:
https://mail-index.netbsd.org/tech-pkg/2025/01/19/msg030395.html

Log message:
lang/go/version.mk: Use ${TOOLBASE}, not ${PREFIX}, for GO.

This is the command used at compile-time to run the Go toolchain.

Preparation for cross-compiling golang packages.  No change for
native builds because in that case TOOLBASE and PREFIX are the same.