Skip to content
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

cmd/cgo: misc/cgo/test fails if GOROOT is under GOPATH #3337

Closed
peterh opened this issue Mar 17, 2012 · 3 comments
Closed

cmd/cgo: misc/cgo/test fails if GOROOT is under GOPATH #3337

peterh opened this issue Mar 17, 2012 · 3 comments
Milestone

Comments

@peterh
Copy link

peterh commented Mar 17, 2012

On my machine, I keep all source files under ~/src. Setting GOPATH to ~ works well,
except the most recent weekly fails its tests unless I unset GOPATH first.

What steps will reproduce the problem?
1. export GOPATH=~
2. export GOROOT=~/src/go
3. cd ~/src/go/src
4. ./all.bash

What is the expected output?
All tests pass

What do you see instead?
After many lines,

# ../misc/cgo/test
can't load package: ~/src/go/misc/cgo/test/callback.go:14:2: local import
"./backdoor" in non-local package

Which operating system are you using?
Same results on both Mac OS 10.6 and Debian Stable

Which revision are you using?  (hg identify)
3cdba7b0650c weekly/weekly.2012-03-13
@dsymonds
Copy link
Contributor

Comment 1:

I don't know whether this is a supported configuration, but it doesn't seem crazy.

Labels changed: added priority-go1, toolbug, cgo, removed priority-triage.

Owner changed to @rsc.

@minux
Copy link
Member

minux commented Mar 19, 2012

Comment 2:

http://golang.org/cl/5852043/

Status changed to Started.

@minux
Copy link
Member

minux commented Mar 20, 2012

Comment 3:

This issue was closed by revision 23322ab.

Status changed to Fixed.

@rsc rsc added this to the Go1 milestone Apr 10, 2015
@rsc rsc removed the priority-go1 label Apr 10, 2015
@golang golang locked and limited conversation to collaborators Jun 24, 2016
@rsc rsc removed their assignment Jun 22, 2022
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants