fix: *golang: Set GOROOT_FINAL to use libdir #6388
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Merge Checklist
All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)
*-static
subpackages, etc.) have had theirRelease
tag incremented../cgmanifest.json
,./toolkit/scripts/toolchain/cgmanifest.json
,.github/workflows/cgmanifest.json
)./SPECS/LICENSES-AND-NOTICES/data/licenses.json
,./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md
,./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON
)*.signatures.json
filessudo make go-tidy-all
andsudo make go-test-coverage
passSummary
What does the PR accomplish, why was it needed?
Fix golang packages to set the compiled-in GOROOT correctly.
This is not causing problems under normal circumstances because shells are loading /etc/profile which has the correct GOROOT set.
However the go binary itself has an invalid GOROOT.
GOROOT_FINAL sets the compiled-in default GOROOT for the final go binary.
This was set to /usr/bin/go which causes the
go
command to error out (when /etc/profile is not loaded) because that is the binary path not the path of the final GOROOT.Change Log
golang
andmsft-golang
to have the correct final valueDoes this affect the toolchain?
NO
Associated issues
Test Methodology