ci: install patchelf in the sciter run-on-arch build#1
Merged
Conversation
The run-on-arch base image no longer ships patchelf, and build.py needs it to set the rpath when packaging the .deb. patchelf was already added to the flutter run-on-arch install block but missed on the sciter one, so the nightly sciter builds (x86_64 + armv7) failed with "patchelf: not found". Add it there too.
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
1 participant
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.
Fixes the nightly Linux sciter builds (x86_64 + armv7) which were failing with
patchelf: not found.The run-on-arch base image no longer ships patchelf preinstalled, and build.py uses it to set the rpath when packaging the .deb. patchelf was already added to the flutter run-on-arch install block but missed on the sciter one. This adds it there too.
Workflow-only change. Fork-local: our flutter-build.yml is already diverged (the DRM build deps), so this completes a partial fix on our side. Not an upstream issue in its current form (upstream's nightly fails elsewhere).