This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug go/63731] Fallback to netgo does not work
- From: "boger at us dot ibm.com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 03 Dec 2014 18:38:57 +0000
- Subject: [Bug go/63731] Fallback to netgo does not work
- Auto-submitted: auto-generated
- References: <bug-63731-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63731
--- Comment #23 from boger at us dot ibm.com ---
If I look at this documentation: http://tip.golang.org/doc/go1.4#gocmd
It says this:
The behavior of the go build subcommand's -a flag has been changed for
non-development installations. For installations running a released
distribution, the -a flag will no longer rebuild the standard library and
commands, to avoid overwriting the installation's files.
When I read this it sounds like the previous behavior with the -a option was to
rebuild the packages and put the newly built packages into the installed
directories, including the standard library. If everyone who used 'go build'
with -a generated their own copy of the built packages and then threw them
away, how would the installation's files ever get overwritten?