https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63731
Ian Lance Taylor <ian at airs dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2014-11-21
Ever confirmed|0 |1
--- Comment #16 from Ian Lance Taylor <ian at airs dot com> ---
Gccgo and GCC act the same on glibc systems: if you choose static linking, DNS
lookups only work if the dynamic libraries are available.
The only difference between Go and C here is that the Go library happens to
have code that will work for some people some of the time. I don't want the
library to automatically fall back to the Go code in all cases, because in some
cases it will turn a possibly-explicable failure into a completely inexplicable
failure, and in a few cases it will turn a correct failure into an incorrect
success.
It's OK with me to make the go tool's -a option work with gccgo. It will only
work if people have the library sources available. If we do that, this issue
will be fixed. I don't know how hard that would be--it might be easy.
I don't know of another good way to fix this.
