Fix buildroot when launched from install script #1229
Draft
+23
−18
Conversation
This file contains 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
|
Hmm. Seems like the updated version of buildroot doesn't like being built as root, which happens when running the install script. The problem seems to be specific to building tar. |
|
Don't love a configuration option called Are there any alternatives? |
|
Not a fan of it either. It's what the error message mentioned, so I'm testing it as a starting point to see if it actually fixes the problem. Will see how it goes in the CI and then investigate other options. There was nothing immediately apparent though. |
|
Seems like with the new version of OpenSBI we need 1600000 instructions get to the OpenSBI banner instead of the previous 1400000. Updated regression-wally accordingly. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Generating buildroot worked when the makefile was launched directly but not when the install script called it. The issue was that
$WALLYwas not set.