The main issue with getting it in essentially boils down to gccgo and upstream Go disagreeing on the GOARCH for mips64el (gccgo uses
"mipsn64"[0]), which makes bootstrapping difficult.
[0]: https://groups.google.com/d/topic/golang-nuts/waTy56I_KWQ/discussion
Are you saying that the patch is more complex than just
s/mipsn64/mips64el/ ? Or are you saying you do not want to maintain
such patch until upstream add an alias for mips64el ?
On 7 June 2017 at 02:23, Mathieu Malaterre <malat@debian.org> wrote:
Are you saying that the patch is more complex than just
s/mipsn64/mips64el/ ? Or are you saying you do not want to maintain
such patch until upstream add an alias for mips64el ?
Yes, the patch is more complex than simply adjusting the GOARCH values
from what I've seen -- the crux of the issue is that we need Go
available in order to build Go, and gccgo has been our simplest source
for doing so (especially since it makes backports easy to bootstrap
too), but this discrepancy between GOARCH in gccgo vs cgo causes build
issues when doing so.
In theory we should be able to do a cross-compiling bootstrap of
mips64el, but that increases the complexity level significantly as
well (if not in the packaging source, then in the upload procedure to
get all the right bits in place in the archive).
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 422 |
Nodes: | 16 (2 / 14) |
Uptime: | 196:50:45 |
Calls: | 8,951 |
Calls today: | 2 |
Files: | 13,352 |
Messages: | 5,992,477 |