What example are you taking about? Please show us your code.

It sounds like your code was wrong, and that you fixed it. So I'm not sure what concrete step the Go project should take.

What example are you taking about? Please show us your code.

It sounds like your code was wrong, and that you fixed it. So I'm not sure what concrete step the Go project should take.

Hi!
Sorry, I was not clear here. The code I tested was this: https://github.com/golang/go/wiki/cgo#calling-go-functions-from-c

Regarding your question: No, I did not make any changes to this particular code.

The undefined reference to 'ACFunction' error message is exactly what I'd expect given that you're compiling the foo.go file but not the foo.c one.

Specify the package instead of a single file and things will work.

The undefined reference to ACFunction'` error message is exactly what I'd expect given that you're compiling the foo.go file but not the foo.c one.

Specify the package instead of a single file and things will work.

Well, go build doesn't throw an error, but I can't find an executable...?

master@thesis:~/go/src/gocallback$ ll
total 16
drwxrwxr-x 2 master master 4096 Okt 29 19:42 ./
drwxrwxr-x 3 master master 4096 Okt 29 19:42 ../
-rw-rw-r-- 1 master master   92 Okt 29 19:42 foo.c
-rw-rw-r-- 1 master master  207 Okt 29 19:42 foo.go
master@thesis:~/go/src/gocallback$ go build gocallback
master@thesis:~/go/src/gocallback$ ll
total 16
drwxrwxr-x 2 master master 4096 Okt 29 19:42 ./
drwxrwxr-x 3 master master 4096 Okt 29 19:42 ../
-rw-rw-r-- 1 master master   92 Okt 29 19:42 foo.c
-rw-rw-r-- 1 master master  207 Okt 29 19:42 foo.go
master@thesis:~/go/src/gocallback$ go run gocallback
go run: no go files listed
master@thesis:~/go/src/gocallback$ go run gocallback ./
go run: no go files listed
master@thesis:~/go/src/gocallback$ go run gocallback ./foo.go
go run: no go files listed
master@thesis:~/go/src/gocallback$ go run package gocallback
go run: no go files listed

Calling go build of a package doesn't produce anything in the current directory, as documented at https://golang.org/cmd/go/#hdr-Compile_packages_and_dependencies . The fact that go build succeeded tells you that all is well. If you want to actually use the package, you need to write a main package somewhere else.

It doesn't sound like there is anything for the Go project to change here, so I'm going to close this issue. Please comment if you disagree.