This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug go/64595] cgo installed into wrong directory
- From: "rguenther at suse dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 14 Jan 2015 13:33:36 +0000
- Subject: [Bug go/64595] cgo installed into wrong directory
- Auto-submitted: auto-generated
- References: <bug-64595-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64595
--- Comment #3 from rguenther at suse dot de <rguenther at suse dot de> ---
On Wed, 14 Jan 2015, ian at airs dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64595
>
> --- Comment #2 from Ian Lance Taylor <ian at airs dot com> ---
> Right, cgo is not run directly. It is run by the go tool. It is in effect an
> internal program like cc1.
Ah - the README didn't say that.
> The version suffix should be fine if libexecsubdir in libgo matches
> libexecsubdir in gotools, as the go tool will locate cgo via the variable
> theGccgoToolDir written to version.go by libgo/Makefile. I'll see if that
> works with --enable-versions-specific-runtime-libs.
Any example use that will end up executing cgo so I can check it out
locally?
> The docs are online at http://golang.org/cmd/{go,gofmt,cgo} which is where most
> people read them. The docs come from the program source
> (libgo/go/cmd/*/doc.go). The programs also have -help options. Would you like
> me to add small man pages that direct people to the web pages?
Yes, that would be convenient! (obviously cgo doesn't need a manpage
then)