Comment 1:

That's surprising.  My only theory is that make is reading some
system config file and overriding the path you've specified.
You might try tracing make to see what it is reading and see
where it is looking for quietgcc.
cd $GOROOT/src/lib9
strace -f -v -e execve,open -s 1024 make _p9dir.o
This will show every call to execve and open, which
will show what make is trying to execute as well as
what files it opened.

Owner changed to r...@golang.org.

Status changed to WaitingForReply.

Comment 2 by ulrich.hobelmann:

Thanks for the pointer!  I'm now a happy owner of an 8g executable.
[...]
[pid 17927] execve("~/install/go/bin/quietgcc", ["quietgcc", "-ggdb", "-I/home/u
lli/go/include", "-O2", "-fno-inline", "-c", "/home/ulli/go/src/lib9/_p9dir.c"]
[...]
= -1 ENOENT (No such file or directory)
It seems that the execve() call does not use the full path with ~ expanded to the
value of $HOME.  Since it is (I presume) "make" that makes the system call, there
probably is no bug in "go".
Replacing the ~/install/go/bin entry in my PATH with the full, explicit path solved
the problem.  (Yet I've never needed to do that until now.)  $GOBIN has always
pointed to the explicit path value, which again I interpret as this not being a "go"
specific problem.
Anyway, the install instructions should probably mention that $PATH always needs to
include the full path, so others will not encounter the same problem.  Whom should I
email for that?

Comment 3 by ulrich.hobelmann:

Um, and how do I close this bug now?

Comment 4:

Glad you found the problem.  We'll look at warning about this in the documentation.

Status changed to Retracted.

Comment 5 by nerocrux:

ulrich.hobelmann,
Sorry for bothering
I have encountered this problem exactly as you do and I still cannot figure out how
to solve this problem...
[Replacing the ~/install/go/bin entry in my PATH with the full, explicit path solved
the problem.]
I'm new to linux and I wonder if you can tell me how exactly you solved the problem.
Thanks in advance.
nerocrux

Comment 6:

> [Replacing the ~/install/go/bin entry in my PATH with the full, explicit
> path solved
> the problem.]
> I'm new to linux and I wonder if you can tell me how exactly you solved the
> problem.
The problem in this bug was that the original poster used
PATH=$PATH:~/install/go/bin
instead of
PATH=$PATH:/home/you/install/go/bin
(or whatever the home directory is).  You apparently
do need to spell out the home directory instead of 
using the ~ syntax.  The latter is not a real file name,
just a shorthand often but not always interpreted by the shell.
The shell will probably meet you halfway if you want to
write $HOME/install/go/bin instead.

Comment 7:

CL https://golang.org/cl/118310043 mentions this issue.