You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What did you do?
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
$ go get golang.org/x/mobile/cmd/gomobile
$ gomobile init
$ go get -d golang.org/x/mobile/example/basic
$ gomobile build -target=android golang.org/x/mobile/example/basic
What did you expect to see?
Build should complete without error messages.
What did you see instead?
gomobile: /home/nick/go/pkg/gomobile/android-ndk-r12/x86/bin/i686-linux-android-nm /tmp/gomobile-work-840948909/lib/x86/libbasic.so: fork/exec /home/nick/go/pkg/gomobile/android-ndk-r12/x86/bin/i686-linux-android-nm: no such file or directory
Comment: there is no such a file indeed. But when I changed mobile/cmd/gomobile/init.go line 31 (var useStrippedNDK = true) to var useStrippedNDK = false, re-compiled, re-init and re-build sample, it was able to build it. And indeed i686-linux-android-nm is now in place.
The text was updated successfully, but these errors were encountered:
nikolay-turpitko
changed the title
x/mobile:
x/mobile: Unable to build basic sample with stripped NDK
Jul 4, 2016
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?What operating system and processor architecture are you using (
go env
)?What did you do?
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
What did you expect to see?
Build should complete without error messages.
What did you see instead?
Comment: there is no such a file indeed. But when I changed mobile/cmd/gomobile/init.go line 31 (
var useStrippedNDK = true
) tovar useStrippedNDK = false
, re-compiled, re-init and re-build sample, it was able to build it. And indeedi686-linux-android-nm
is now in place.The text was updated successfully, but these errors were encountered: