On Tuesday, January 15, 2019 at 4:47:16 PM UTC+3, kuznetso...@gmail.com
wrote:
>
> Hello! Does anyone know how to compile go "hello world" binary for armv5
> processors? Mine setup fails all the time for armv5 and works on armv7.
>
> export TOOLCHAIN=$PWD/tools/
>
> export NDK=~/Library/Android/sdk/ndk-r16b/
>
> $NDK/build/tools/make_standalone_toolchain.py --arch arm --api 14
> --install-dir $TOOLCHAIN
>
> CC="$TOOLCHAIN/bin/arm-linux-androideabi-clang -march=armv5 -mfpu=vfpv2
> -mfloat-abi=soft -mno-thumb" CGO_ENABLED=1 GOOS=android GOARCH=arm GOARM=5
> go build main.go
>
>
> *main.go*
>
> package main
>
> import "fmt"
>
> func main() {
>
> fmt.Println("123")
>
> }
>
> I dig around a bit. And got answer from google ARMV5 is supported by
> Golang (https://github.com/golang/go/issues/29729) but it is still not
> working.
>
>
> How I understand golang creates binary blobs which linked into resulting
> binary. If we assume blobs are ok, and toolchain getting correct arguments
> to produce final binary file here should be no problems. But something is
> wrong. If we break build process step by step then we will see that last
> clang call producing '_cgo_.o' file size of 31072, but resulting final
> 'main' binary is 1957471 bytes. Who is making this final step and
> probably with incorrect arm archeticture flags?
>
>
>
I add scripts and 'go build' output into
gist: https://gist.github.com/axet/365dbd174b6d07b36ff566ea2828818f
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
