There is an updated pull request by q66 against master on the void-packages repository https://github.com/void-ppc/void-packages go-bootstrap https://github.com/void-linux/void-packages/pull/16287 go: add a binary bootstrap package (1.12 series for now) and switch the compiler to it from 1.4 This adds a `go1.12-bootstrap` package newly used instead of `go1.4-bootstrap` to bootstrap the main Go compiler. The reason for this is to allow bootstrapping on platforms the ancient codebase does not support, particularly `ppc64le` and `aarch64`. The new bootstrap package can technically run on all the targets that are in the intersection of what the official compiler supports and what Void supports. ~~There is a problem that the official binaries require glibc (just its dynamic linker, the libc itself and libpthread). In order to deal with that on musl, fetch a binary copy of glibc from Debian (which is reproducibly built, so it should be trustable) and patch the official binaries so that they use the newly bundled libc and dynamic linker. This allows the compiler to execute in a musl system, and build the proper target compiler (which will use the musl dynamic linker and libc, of course).~~ ~~I chose the approach after evaluating all other choices, including `gcompat` and `gccgo`; in the end this was the only thing that truly and reliably worked.~~ I used gcompat to be able to run the compiler. In order for that to work, gcompat needs to be updated and patched, as in https://github.com/void-linux/void-packages/pull/16320. We still need to use patchelf to patch out the `lib64` requirement. The second part of this patchset switches the `go` package to use the new 1.12 bootstrap. Since 1.12, `GOCACHE` must be not set when bootstrapping, so that line was removed. I also added new `broken` lines to disable the package on big endian PowerPC systems (ppc64 BE support uses incorrect ABI and requires POWER8 hardware, making it not safely distributable; 32-bit ppc was just never supported at all). Additionally, I also added a `broken` when cross-building on the same architecture to a different libc (e.g. `x86_64` to `x86_64-musl`). This is because the build system does not account for this scenario and just does not cross build; this creates a package without failing but the contained compiler is just a compiler for the host system and will not function on the target. So at least until this problem is taken care of, disable it in order to not silently build broken packages. If this is accepted, we can drop the `go1.4-bootstrap` package afterwards. @the-maldridge @nilium A patch file from https://github.com/void-linux/void-packages/pull/16287.patch is attached