cmd/go: Windows 10 causes "GOPATH entry is relative" error due to extraneous semicolon #21928
Comments
|
Are you sure there aren't 5 entries in the dialog box on the right hand
side?
…On Tue, Sep 19, 2017 at 11:32 AM, Oliver Janik ***@***.***> wrote:
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
1.9
Does this issue reproduce with the latest release?
yes, freshly downloaded windows installer
What operating system and processor architecture are you using (go env)?
Windows 10 64 bit
What did you do?
C:\Users\Oliver>go env
go: GOPATH entry is relative; must be absolute path: "".
For more details see: 'go help gopath'
C:\Users\Oliver>echo %GOPATH%
C:\gopath;D:\work;D:\temp;
What did you expect to see?
normal go env output
What did you see instead?
an error
The issue seems to be the trailing semicolon. However that is what the env
variable dialog in win 10 produces and I think go should deal with it.
[image: image]
<https://user-images.githubusercontent.com/2280140/30571933-26d0a78e-9d2e-11e7-9bdd-db1c011b566c.png>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#21928>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAcA5icHTjP-OXn9VXCy1OIRxE6VGV2ks5sjxmzgaJpZM4PbvJg>
.
|
|
Yes I'm sure. Should be easy to replicate for anyone with Win 10. |
|
Thanks for confirming. It's pretty bad that windows terminates a list with
an empty atom. On unix terminating a PATH list with a : is very bad as it
is sometimes interpreted as ".", ie PATH=/bin:/usr/bin: (not trailing
colon) is the same as PATH=/bin:/usr/bin:.
…On Tue, Sep 19, 2017 at 12:24 PM, Oliver Janik ***@***.***> wrote:
Yes I'm sure. Should be easy to replicate for anyone with Win 10.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#21928 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAAcAyryCAbhskiKMOS6ZFy0ti9HMd3vks5sjyXigaJpZM4PbvJg>
.
|
|
It's application specific, Windows does not enforce or follow a standard. Here's part of my
|
|
cc @cznic @alexbrainman I know we've had the discussion before about |
davecheney
added
ExpertNeeded
NeedsInvestigation
|
I can reproduce the issue on my Windows 10. And I agree that we should fix it.
Windows always check your current directory first even before looking at the PATH. But we are talking about GOPATH here. I think we should ignore blank elements of GOPATH. We should ignore elements consisting of spaces only. What do you think? Alex |
mdempsky
changed the title
|
@alexbrainman yes, you're right. I think
|
|
@davecheney I do not see how path elements like " " are different from "". What do you propose to do with path elements like " "? Alex |
|
" " is a mistake. For the record I consider "" as mistake, but the chances of windows 10 fixing their buggy tool are close to zero, so I guess we have to live with it.
… On 20 Sep 2017, at 11:23, Alex Brainman ***@***.***> wrote:
@davecheney I do not see how path elements like " " are different from "". What do you propose to do with path elements like " "?
Alex
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
I think the both should be ignored as below works. path-list is candidates for the PATHs. |
|
Mattn, as Alex pointed out, we are no discussing PATH, but GOPATH. The rules for searching for a binary do not apply.
… On 20 Sep 2017, at 11:44, mattn ***@***.***> wrote:
I think the both should be ignored as below works. path-list is candidates for the PATHs.
C:\>set PATH=; ;%PATH%
C:\>some-command.exe
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
SGTM. Thanks for explaining. Alex |
|
Change https://golang.org/cl/65151 mentions this issue: |
|
Workaround: In Windows 10 control panel "Edit environment variable" dialog select the "Edit text..." button and delete the trailing semicolon. (Took me a while to work out how to do this so I thought others might like to know.) |
|
Thanks! |
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version)?1.9
Does this issue reproduce with the latest release?
yes, freshly downloaded windows installer
What operating system and processor architecture are you using (
go env)?Windows 10 64 bit
What did you do?
What did you expect to see?
normal go env output
What did you see instead?
an error
The issue seems to be the trailing semicolon. However that is what the env variable dialog in win 10 produces and I think go should deal with it.
The text was updated successfully, but these errors were encountered: