At this point, let's wait for 1.6.

I figured as much.

CL https://golang.org/cl/13772 mentions this issue.

I'm still hitting this issue with musl-1.1.12, and go-1.5.2, bootstrapping from go-1.4.3.

# os/user
os/user/lookup_unix.go:70: cannot use C.ulong(bufSize) (type C.ulong) as type C.size_t in argument to _Cfunc__CMalloc
os/user/lookup_unix.go:83: cannot use C.ulong(bufSize) (type C.ulong) as type C.size_t in argument to _Cfunc_mygetpwnam_r
os/user/lookup_unix.go:98: cannot use C.ulong(bufSize) (type C.ulong) as type C.size_t in argument to _Cfunc_mygetpwuid_r

It'll be in Go 1.6. 1.5.x is only for critical things, not nice to haves.

What @somasis is reporting looks like a separate issue to me.

I should have said, I actually patched go-1.5.2 with the commit related to this issue, and still hit that error.

@somasis Have you tried tip (latest development version)?

@Thomasdezeeuw Yes, I get the same error.

# os/user
os/user/lookup_unix.go:67: cannot use C.ulong(bufSize) (type C.ulong) as type C.size_t in argument to _Cfunc__CMalloc
os/user/lookup_unix.go:80: cannot use C.ulong(bufSize) (type C.ulong) as type C.size_t in argument to _Cfunc_mygetpwnam_r
os/user/lookup_unix.go:95: cannot use C.ulong(bufSize) (type C.ulong) as type C.size_t in argument to _Cfunc_mygetpwuid_r

I managed to get the latest git master to build with CGO_ENABLED=0 passed to the final ./make.bash. That doesn't sound like the right solution, though.

...which then fails to build programs such as syncthing, because of the exact same error.

@somasis the compile errors you pasted are unrelated to this issue and are possibly a bug in cgo. If there isn't a similar issue already filed, you should file a new one. In fact, they may rely on another fix that was already applied to 1.6; you may as well try with the betas or with master first.

Is this still an issue in Go 1.6? I'm hearing concerns about musl in Gentoo [1].

[1] https://bugs.gentoo.org/show_bug.cgi?id=575510#C1

@williamh This issue is closed as fixed in 1.6. Please take any questions about it to a forum; see https://golang.org/wiki/Questions . Thanks.