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.
The problem with cpp-linter-action is that they bring their own Python (via
actions/setup-python
), but fail to ensure that the dynamically-linked interpreter can find thelibpython3.xx.so
, either viaDT_RPATH
or withLD_LIBRARY_PATH
:The suggested fix is to have a matching version of libpython in the container, which... isn't optimal: the container (Debian) Python can have different patch release and build configuration.
Here I'm trying a different thing — run the same
setup-python
action but allow it to exportLD_LIBRARY_PATH
. And if that works, we can drop python3-pip/python3-venv packages from the debian dockerfile.