Comment 1:

Please try
$ rm -Rf $GOROOT/pkg $GOROOT/bin
$ all.bash

Comment 2:

I did this:
#!/bin/bash
set -xe
export GOPATH=`pwd`
rm -Rf $GOROOT/pkg $GOROOT/bin
cd $GOROOT/src
./make.bash
cd $GOPATH
rm -rf $GOROOT/pkg/linux_amd64_race
go install -v -race ./...
same issue.

Comment 3:

The script says:
go install: no install location for directory /.../gopath/src/foo outside GOPATH

Comment 4:

OK, I am able to reproduce it by copying foo to code.google.com/p/foo

Comment 5:

The workaround is to type:
$ go install -race -v ./...
again

Comment 6:

Mmm... strange. Here's my script and build log. Where do our setups differ?

Attachments:

1. build.log (3181 bytes)
2. build.sh (193 bytes)

Comment 7:

Thanks, I found the workaround.

Comment 8:

The same happens with normal (non -race) build, if you don't preinstall syscall.
$ go install [-race] std
fixes it in both cases.
So this is low-priority bug in cmd/go. Normal uses who have all preinstalled packages
should not hit it.

Comment 9:

Labels changed: added priority-later, go1.2maybe, removed priority-triage.

Status changed to Accepted.

Comment 10:

This bug leads to other fun.
Steps to reproduce:
1. Know about this bug
2. Sometimes run go install -race std before doing a race build of your command
3. Some days after that, run gofmt over all your source code
4. Be confused about why gofmt takes minutes instead of seconds
Turns out go install -race std installed a race-enabled gofmt. Maybe a tweak somewhere
will save a few people the confusion I've been experiencing.

Comment 11:

This issue was closed by revision b0a1b82.

Status changed to Fixed.