New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

x/tools/cmd/godoc: not work with symbolic links #7093

gopherbot opened this Issue Jan 10, 2014 · 2 comments


None yet
5 participants

gopherbot commented Jan 10, 2014

by laf163:

What steps will reproduce the problem?
If possible, include a link to a program on
1.ln -s ~/project/xxx $GOPATH/src/xxx
2.go install xxx
3.godoc -http=:6060

What is the expected output?
visit http://x.x.x.x:6060/pkg can find the package xxx.

What do you see instead?
not found.

Which compiler are you using (5g, 6g, 8g, gccgo)?

Which operating system are you using?
centos6.4 amd64

Which version are you using?  (run 'go version')
$ go version
go version go1.2 linux/amd64

Please provide any additional information below.
rm $GOPATH/src/xxx and copy ~/project/xxx to $GOPATH/src, work properly.

This comment has been minimized.


minux commented Jan 11, 2014

Comment 1:

in general, cmd/go and godoc both can't handle symlinks well.
avoid using symlinks if you can.

Labels changed: added repo-tools, release-none.

@gopherbot gopherbot added new labels Jan 11, 2014

@bradfitz bradfitz removed the new label Dec 18, 2014

@rsc rsc added this to the Unplanned milestone Apr 10, 2015

@rsc rsc removed the release-none label Apr 10, 2015

@rsc rsc changed the title from not work with symbolic links to x/tools/cmd/godoc: not work with symbolic links Apr 14, 2015

@rsc rsc removed the repo-tools label Apr 14, 2015


This comment has been minimized.

brianolson commented Nov 18, 2015

This is important to me. I already have a place in my filesystem where I do checkouts of things I'm working on, and I'd like to do the following:
mkdir ${GOPATH}/src/myserver.tld
cd ${GOPATH}/src/myserver.tld
ln -s ${HOME}/my/usual/path/to/my/project .

I'd like to then see the documentation for the thing I'm working on in my godoc server.
I have a fix written for this, it's a small change to

The above symlink already works for building! I can use this just fine as
import "myserver.tld/project"

Given that, it's incongruous that godoc doesn't also work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment