This seems to be a common issue where people confuse problems building Go 
programs with problems building Go because they do an in-place upgrade from the 
prepackaged source, causing go build to mix, say, 1.5 and 1.6 files that are 
not compatible.

https://github.com/andlabs/ui/issues/185
https://github.com/andlabs/ui/issues/190 (unconfirmed)
http://stackoverflow.com/questions/39064285/go-project-build-failed-lfstackpack-redeclared-in-this-block
https://github.com/jmoiron/sqlx/issues/203

Is it possible to have a check for this situation in the build scripts, or 
would that be too hard to do right?

-- 
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 golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to