cmd/go: go work causes go build to error when symlinks are involved #53343
Description
What version of Go are you using (go version)?
$ go version go version go1.18 darwin/arm64
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env GO111MODULE="" GOARCH="arm64" GOBIN="" GOCACHE="/Users/testy/Library/Caches/go-build" GOENV="/Users/testy/Library/Application Support/go/env" GOEXE="" GOEXPERIMENT="" GOFLAGS="" GOHOSTARCH="arm64" GOHOSTOS="darwin" GOINSECURE="" GOMODCACHE="/Users/testy/go/pkg/mod" GONOPROXY="" GONOSUMDB="" GOOS="darwin" GOPATH="/Users/testy/go" GOPRIVATE="" GOPROXY="https://proxy.golang.org,direct" GOROOT="/opt/homebrew/Cellar/go/1.18/libexec" GOSUMDB="sum.golang.org" GOTMPDIR="" GOTOOLDIR="/opt/homebrew/Cellar/go/1.18/libexec/pkg/tool/darwin_arm64" GOVCS="" GOVERSION="go1.18" GCCGO="gccgo" AR="ar" CC="clang" CXX="clang++" CGO_ENABLED="1" GOMOD="/Users/testy/tmp/x/lib1/lib2/go.mod" GOWORK="/Users/testy/tmp/x/go.work" CGO_CFLAGS="-g -O2" CGO_CPPFLAGS="" CGO_CXXFLAGS="-g -O2" CGO_FFLAGS="-g -O2" CGO_LDFLAGS="-g -O2" PKG_CONFIG="pkg-config" GOGCCFLAGS="-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/qr/4s_dq83s1lddgv10vn9591y80000gn/T/go-build3045518203=/tmp/go-build -gno-record-gcc-switches -fno-common"
What did you do?
`
mkdir bug
cd bug
mkdir lib1 lib2
cd lib1
go mod init bugsquash.com/lib1
ln -s ../lib2
cd ../lib2
go mod init bugsquash.com/lib2
mkdir -p internal/a
printf "package a\nfunc Foo() {}\n" > internal/a/foo.go
mkdir -p cmd/foo
printf 'package main\nimport "bugsquash.com/lib2/internal/a"\nfunc main() { a.Foo() }\n' > cmd/foo/foo.go
go build cmd/foo/foo.go # succeeds
cd ../lib1/lib2
go build cmd/foo/foo.go # succeeds
cd ../../
go work init
go work use ./lib2
cd lib1/lib2
go build cmd/foo/foo.go
fails with this message:
package command-line-arguments
cmd/foo/foo.go:2:8: use of internal package bugsquash.com/lib2/internal/a not allowed
cd ../../lib2
go build cmd/foo/foo.go # succeeds
cd ../
rm go.work
cd lib1/lib2
go build cmd/foo/foo.go # succeeds
`
What did you expect to see?
I expect go build to succeed in lib1/lib2 (lib2 is a symlink) even when using go.work. If I remove go.work it works.
What did you see instead?
package command-line-arguments cmd/foo/foo.go:2:8: use of internal package bugsquash.com/lib2/internal/a not allowed