There was an issue during an update and another version of a patch was
introduced by mistake. GOPROXY, GOSUMDB and the baseline ISA for PPC64
were modified by this change.
This commit overrides the "bad" patch with the "good" one. And also
deletes an old unused patch.
Related: RHEL-34085
Related: RHEL-32658
Commit b3c52a9 (Set the baselines for AMD64 and PPC64LE, 2024-04-10)
When the baselines where added go.env was not included so the change was
not really applied. This should fix it.
Related: RHEL-32658
Related: RHEL-32660
Related: RHEL-34008
Related: RHEL-34236
- Update bundled-deps.sh to generate a proper output.
- Add 0001-Modify-go.env.patch that modifies the go.env file to change GOPROXY, GOSUMDB, and GOTOOLCHAIN settings.
- Delete 0002-syscall-expose-IfInfomsg.X__ifi_pad-on-s390x.patch.
```
Error:
Problem: package golang-race-1.19.7-1.fc37.x86_64 requires golang = 1.19.7-1.fc37, but none of the providers can be installed
- golang-1.19.7-1.fc37.x86_64 does not belong to a distupgrade repository
- problem with installed package golang-race-1.19.7-1.fc37.x86_64
```
The Go runtime silently chose the gold linker on arm and aarch64 build
targets to work around a binutils bug.
That bug was from 2016, and has been fixed in binutils for a while. But
the Go workaround was still in place.
The workaround to choose gold was supposed to error out during the
configure phase if gold wasn't found - but that doesn't happen.
This leads to builds on aarch64 failing if attempting to compile without
gold.
Just removing the special condition in the Go source code:
https://go-review.googlesource.com/c/go/+/391115/
works, but that patch is unlikely to be merged upstream.
A patch fixing the build is more likely to be merged:
https://go-review.googlesource.com/c/go/+/366279/
which updates the linker selection to use gold only if available.
References to this bug in upstream Go and Binutils:
https://github.com/golang/go/issues/22040https://sourceware.org/bugzilla/show_bug.cgi?id=19962
Including the likely-to-be-merged patch here.
