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.

Sign up for GitHub

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

Wrong GOROOT is used when go-licenses builds and runs on different environments #149

Open
jingyuanliang opened this issue Sep 14, 2022 · 3 comments
Open

Wrong GOROOT is used when go-licenses builds and runs on different environments #149

jingyuanliang opened this issue Sep 14, 2022 · 3 comments

Comments

@jingyuanliang
Copy link
Contributor

jingyuanliang commented Sep 14, 2022 •
edited

Unless a GOROOT is explicitly set, it uses the GOROOT from the build environment, which can be not reflecting the execution environment. See discussions in golang/go#51473.
@krutztq
Copy link

krutztq commented Oct 25, 2022

Same issue, here.

@Bobgy
Copy link
Collaborator

Bobgy commented Dec 7, 2022

As mentioned in the issue, a workaround is to set the GOROOT env when calling go licenses

@jingyuanliang jingyuanliang mentioned this issue Dec 20, 2022
Merged
radhus added a commit to einride/sage that referenced this issue Jan 4, 2023
@radhus
fix(go-licences): fix running on macOS when Go is upgraded
3f157a6 
Running go-licenses breaks after upgrading Go through Homebrew, as the
GOROOT path on the machine no longer matches the one used to build
go-licenses.

As a workaround, explicitly set GOROOT.

See google/go-licenses#149 for reference.
radhus added a commit to einride/sage that referenced this issue Jan 4, 2023
@radhus
fix(go-licences): fix running on macOS when Go is upgraded
35a67ce 
Running go-licenses breaks after upgrading Go through Homebrew, as the
GOROOT path on the machine no longer matches the one used to build
go-licenses.

As a workaround, explicitly set GOROOT.

See google/go-licenses#149 for reference.
@radhus radhus mentioned this issue Jan 4, 2023
Merged
radhus added a commit to einride/sage that referenced this issue Jan 4, 2023
@radhus
fix(go-licences): fix running on macOS when Go is upgraded
d0f1f51 
Running go-licenses breaks after upgrading Go through Homebrew, as the
GOROOT path on the machine no longer matches the one used to build
go-licenses.

As a workaround, explicitly set GOROOT.

See google/go-licenses#149 for reference.
radhus added a commit to einride/sage that referenced this issue Jan 4, 2023
@radhus
fix(go-licences): fix running on macOS when Go is upgraded
247f6bd 
Running go-licenses breaks after upgrading Go through Homebrew, as the
GOROOT path on the machine no longer matches the one used to build
go-licenses.

As a workaround, explicitly set GOROOT.

See google/go-licenses#149 for reference.
@Bobgy Bobgy mentioned this issue Mar 9, 2023
Closed
@SuperSandro2000
Copy link

Are there any plans to fix this issue? 👀

SuperSandro2000 added a commit to SuperSandro2000/nixpkgs that referenced this issue Jan 8, 2024
@SuperSandro2000
go-licenses: fix returning empty output when GOROOT differs from buil…
fbd2c89 
…t environment

see google/go-licenses#149
SuperSandro2000 added a commit to SuperSandro2000/nixpkgs that referenced this issue Jan 8, 2024
@SuperSandro2000
go-licenses: fix returning empty output when GOROOT differs from buil…
1552dd7 
…t environment

see google/go-licenses#149
@SuperSandro2000 SuperSandro2000 mentioned this issue Jan 8, 2024
Merged
13 tasks
SuperSandro2000 added a commit to SuperSandro2000/nixpkgs that referenced this issue Jan 9, 2024
@SuperSandro2000
go-licenses: fix returning empty output when GOROOT differs from buil…
39ac0e8 
…t environment

see google/go-licenses#149
SuperSandro2000 added a commit to SuperSandro2000/nixpkgs that referenced this issue Jan 10, 2024
@SuperSandro2000
go-licenses: fix returning empty output when GOROOT differs from buil…
39f88bc 
…t environment

see google/go-licenses#149
SuperSandro2000 added a commit to SuperSandro2000/nixpkgs that referenced this issue Jan 10, 2024
@SuperSandro2000
go-licenses: fix returning empty output when GOROOT differs from buil…
ed75e3f 
…t environment

see google/go-licenses#149
SuperSandro2000 added a commit to SuperSandro2000/nixpkgs that referenced this issue Jan 11, 2024
@SuperSandro2000
go-licenses: fix returning empty output when GOROOT differs from buil…
a0c07c0 
…t environment

see google/go-licenses#149
SuperSandro2000 added a commit to SuperSandro2000/nixpkgs that referenced this issue Jan 11, 2024
@SuperSandro2000
go-licenses: fix returning empty output when GOROOT differs from buil…
ea633d6 
…t environment

see google/go-licenses#149
SuperSandro2000 added a commit to SuperSandro2000/nixpkgs that referenced this issue Jan 14, 2024
@SuperSandro2000
go-licenses: fix returning empty output when GOROOT differs from buil…
e7ea30b 
…t environment

see google/go-licenses#149
SuperSandro2000 added a commit to SuperSandro2000/nixpkgs that referenced this issue Jan 14, 2024
@SuperSandro2000
go-licenses: fix returning empty output when GOROOT differs from buil…
f4d7a87 
…t environment

see google/go-licenses#149
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@Bobgy @SuperSandro2000 @krutztq @jingyuanliang