Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: fix clang-tidy action #2948

Merged
merged 1 commit into from
Feb 21, 2024
Merged

ci: fix clang-tidy action #2948

merged 1 commit into from
Feb 21, 2024

Conversation

alebastr
Copy link
Contributor

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 the libpython3.xx.so, either via DT_RPATH or with LD_LIBRARY_PATH:

/__t/Python/3.11.8/x64/bin/python: error while loading shared libraries: libpython3.11.so.1.0: cannot open shared object file: No such file or directory

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 export LD_LIBRARY_PATH. And if that works, we can drop python3-pip/python3-venv packages from the debian dockerfile.

@Alexays Alexays merged commit 977c66e into Alexays:master Feb 21, 2024
9 of 10 checks passed
@Alexays
Copy link
Owner

Alexays commented Feb 21, 2024

Thanks!

@alebastr alebastr deleted the clang-tidy-fix branch February 21, 2024 12:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants