Yes, without setting GOROOT was how I initially ran into this problem. I 
double checked with printenv GOROOT to make sure it wasn't set.

I've wiped and reinstalled both my go installation (Archlinux package go 
1.9.4) and GOPATH to the same result.

I tried to isolate the problem further by using go build instead of gb. The 
issue is only present with gb so I will post a GitHub issue about that.

Thanks for taking the time to respond.

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 
For more options, visit

Reply via email to