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

Jump to bottom

go: unknown environment setting GO111MODULE=ON in windows 10 #35321

Closed
binuedwin opened this issue Nov 3, 2019 · 8 comments
Closed

go: unknown environment setting GO111MODULE=ON in windows 10 #35321

binuedwin opened this issue Nov 3, 2019 · 8 comments
Labels
WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.

Comments

@binuedwin
Copy link

What version of Go are you using (go version)?

$ go version

Does this issue reproduce with the latest release?

What operating system and processor architecture are you using (go env)?

go env Output
$ go env

What did you do?

What did you expect to see?

What did you see instead?

Hi team,

I tried installing go in my windows and tried setting Go111Module=On. after doing this getting error.
a command used go env -w GO111MODULE=ON
go: unknown environment setting GO111MODULE=ON

After trying to uninstall and reinstall go also getting the same error.

Thanks,
Binu
@mvdan
Copy link
Member

mvdan commented Nov 3, 2019

Why are you using the uppercase "on"? The docs all say GO111MODULE=on.

@mvdan mvdan added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Nov 3, 2019
@binuedwin
Copy link
Author

binuedwin commented Nov 4, 2019 via email

@Rolln-dev
Copy link

Rolln-dev commented Nov 7, 2019 •
edited

I accidentally typed go env -w GO111MODULE=1 and now can't run the go command at all. Gives me an go: unknown environment setting GO111MODULE=1 error which is expected. But how can I fix this?

On Windows host.

@Rolln-dev
Copy link

Rolln-dev commented Nov 7, 2019 •
edited

Figured it out. Manually set the system environment variable using set GO111MODULE=on and now things are back to normal.

@oiooj
Copy link
Member

oiooj commented Nov 13, 2019

@rollnthndr Your issue fixed in Go1.14, see #34880.

@dylankb dylankb mentioned this issue Dec 15, 2019
Closed
@ALTree
Copy link
Member

ALTree commented Jan 16, 2020

This is a dup of #34880 which is fixed on tip, closing here.

@ALTree ALTree closed this as completed Jan 16, 2020
@ahhzaky
Copy link

ahhzaky commented Sep 17, 2020

how to activate GO111MODULE = "on"? on windows10

@davecheney
Copy link
Contributor

Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only.

For asking questions, see:

@golang golang locked as resolved and limited conversation to collaborators Sep 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@davecheney @oiooj @mvdan @ALTree @Rolln-dev @binuedwin @ahhzaky