[go-nuts] Cross compiling sers (with CGO) to Android

I am trying to cross compile the sers library from github.com/distributed/sers to arm64 android. I have an Android SDK on my computer and I point $AR, $CC, $CXX and so on to the relevant programs. In a checkout of the sers library (git clone https://github.com/distributed/sers.git) I run

[go-nuts] Re: Cross compiling sers (with CGO) to Android

This is embarassing, but setting GOOS=android fixed the issue. I was under the impression that android builds were only supported with an addition to the toolchain. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group

[go-nuts] Fail build on missing dependencies

Consider the following scenario. I commit a version of my project and I'm happy with the dependencies and their versions that are listed in my go.mod file. I push my code to the central repo and the CI starts to build the project with go get or go install. Because the CI builds for a GOOS/GOARCH

[go-nuts] Re: Fail build on missing dependencies

Thank you for your overview and the links. Using -mod=readonly together with go install indeed does what I want. -- 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

[go-nuts] Re: Porting Go to New Platforms

Hi Efraim You can take a binary built for linux/386, copy it to a QNX system and run it. The QNX loader will load and execute these binaries. Of course the program will not get very far during its execution, I think it crashes at the first "int $0x80" instruction, which is to be expected. This

[go-nuts] Thread local error information when wrapping lib with cgo

I am currently wrapping a proprietary library with cgo. About error reporting, the library documentation says "Every function that can fail returns at least boolean or pointer value that can be used to detect error state (false and NULL means error, every other value means success). If such er

Re: [go-nuts] Thread local error information when wrapping lib with cgo

Thanks for the clarification. I suppose internal UnlockOSThread does not override the runtime.LockOSThread by my code from the outside? Not really. On error you could malloc a buffer, copy in the string, > and return the buffer to Go. In Go you could copy the buffer into Go > memory and C.fre