Fails to build snapd on ppc64el

[Michael Vogt]

The builds of snapd git master (and 2.28~rc1) fail on ppc64el in zesty (only there) with the following error message:

/tmp/go-build312455947/github.com/snapcore/snapd/cmd/snap-seccomp/_test/snap-seccomp.test: error while loading shared libraries: R_PPC64_ADDR16_HA re115ff6af8 for symbol `’ out of range
exit status 127

One full build log is here: https://launchpad.net/~snappy-dev/+archive/ubuntu/edge/+build/133381271

Michael Hudson-Doyle pointed me to https://go-review.googlesource.com/c/go/+/33106 which is the upstream fix for this bug. This fix is included in the 1.8 series of golang. To unblock snapd in 17.04 I would like to backport/SRU the fix for golang.

This is also a problem for other packages using go in 17.04, e.g. https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1711935 and for our users who develop on go1.7.

[Test case]
1. build snapd on ppc64el with golang 1.7
2. observe that it fails to build with R_PPC64_ADDR16_HA out of range errors
3. update to the fixed golang 1.7
4. verify that the build works with that

[Regression potential]
- medium, its a change in the way the linker is called. However given that this is the default in go1.8 the risk seems ok.

[Michael Hudson-Doyle (mwhudson)]

Speaking as the golang maintainer, this is definitely a change we want, and it's a backport from the upstream compiler that is the default in artful. Even if binaries with TEXTREL execute correctly (which they should) it is better to not have text relocations...

[Brian Murray (brian-murray)]

Hello Michael, or anyone else affected,

Accepted golang-1.7 into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/golang-1.7/1.7.4-2ubuntu1.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-zesty to verification-done-zesty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-zesty. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!