Go 1.4.3 / Arm V6 - Segfault about golang-armbuilds

[nsteinmetz]

It works with gvm:

pi@raspberrypi:~ $ gvm install go1.4.3
Downloading Go source...
Installing go1.4.3...
 * Compiling...
go1.4.3 successfully installed!
pi@raspberrypi:~ $ gvm use go1.4.3 --default
Now using version go1.4.3
pi@raspberrypi:~ $ gvm pkgset create influxdb
pi@raspberrypi:~ $ gvm pkgset use influxdb
Now using version go1.4.3@influxdb
pi@raspberrypi:~ $ go get github.com/tools/godep
pi@raspberrypi:~ $

[DieterReuter]

@nsteinmetz thanks for this report. I have to check it once again in detail. It was compiled on ARMv7 and maybe I missed something.
Maybe I have to change the build step, and have to compile it within an ARMv6 Docker container - just to make sure, that all OS and gcc libraries are truly ARMv6.

With gvm you compiled it directly on your RPi1 on an ARMv6 environment.

[nsteinmetz]

I know that I compiled locally with gvm, I was trying to use your prebuild binary version to skip this long step ;-)

Comparison was just to check that is was not a raspberry issue.

Let me know if you need me to run some test once you update your building chain (or if you want me to build it on my rpi.)

[DieterReuter]

Not a problem, I do have some Pi's here. So I can run the tests locally and pretty fast too.

[DieterReuter]

Maybe I'll try to build Go with some extra gcc flags -march=armv6 - just a first idea now. More details on gcc options for ARM can be found here https://gcc.gnu.org/onlinedocs/gcc/ARM-Options.html.

[DieterReuter]

In the meantime I just did ran a complete ARMv6 build natively on a Raspberry Pi 1 board, but without the tests. This resolves the issues on ARMv6 for now and everybody can use the pre-compiled binary tarballs.