Containers: Prepare for GCC5 to GCC switch#529
Open
apop5 wants to merge 2 commits intomicrosoft:mainfrom
Open
Conversation
EDK2 is moving towards depreciating the GCC5 toolchain in favor of the GCC tool chain. To prepare for this, create exports for both GCC5 and GCC to allow container builds to use either.
makubacki
approved these changes
Feb 25, 2026
Member
|
@apop5, I assume you successfully built with |
Contributor
Author
Yes, in testing sbsa, this was the only change required from the container. (I manually set it in an interactive container image and verified builds) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
EDK2 is moving towards depreciating the GCC5 toolchain in favor of the GCC tool chain.
To prepare for this, create exports for both GCC5 and GCC to allow container builds to use either.