Wrong GOROOT is used when go-licenses builds and runs on different environments #149
Comments
|
Same issue, here. |
|
As mentioned in the issue, a workaround is to set the GOROOT env when calling go licenses |
radhus
added a commit
to einride/sage
that referenced
this issue
Jan 4, 2023
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
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
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
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.
|
Are there any plans to fix this issue? 👀 |
13 tasks
SuperSandro2000
added a commit
to SuperSandro2000/nixpkgs
that referenced
this issue
Jan 11, 2024
|
Can someone post a working sample? I've the same issue when having global |
|
You need to set GOROOT to your local running go compiler |
|
Found simple workaround: > $(go env GOROOT)/bin/go run github.com/google/[email protected] save . --force --save_path=.go-licenses |
dtrudg
added a commit
to dtrudg/singularity
that referenced
this issue
Aug 27, 2024
If the go toolchain is downloaded due to installed version vs go.mod then we need to set GOROOT for go-licenses to run correctly. See: google/go-licenses#149
dtrudg
added a commit
to dtrudg/singularity
that referenced
this issue
Aug 27, 2024
Pick sylabs#3265 If the go toolchain is downloaded due to installed version vs go.mod then we need to set GOROOT for go-licenses to run correctly. See: google/go-licenses#149
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The text was updated successfully, but these errors were encountered: