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: install clang dependencies directly from LLVM #5575

Merged
merged 1 commit into from
Jan 18, 2025

Conversation

EZoni
Copy link
Member

@EZoni EZoni commented Jan 17, 2025

I think this was a suggestion by @WeiqunZhang in the context of debugging the clang sanitizer issue currently addressed in #5492. I'm extracting all related changes from #5492 to implement and test the LLVM installation separately here.

This effectively unifies the CI scripts to install clang dependencies into one single script that reads the clang version number from the command line.

I think all CI checks should pass here as a prerequisite for debugging the clang sanitizer issue further in #5492.

@EZoni EZoni added the component: tests Tests and CI label Jan 17, 2025
Comment on lines -15 to -17
# This dependency file is currently used within a docker container,
# which does not come (among others) with wget, xz-utils, curl, git,
# ccache, and pkg-config pre-installed.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think what was stated in this comment is not valid since we removed the Ubuntu 23.10 container in #5474.

Copy link
Member

@ax3l ax3l left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM :)

@ax3l ax3l merged commit 1c8d21e into ECP-WarpX:development Jan 18, 2025
37 checks passed
export CXX=$(which clang++-17)
export CC=$(which clang-17)
# parse clang version number from command line
version_number=${1}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Saw too late.

You could make the script more robust by checking that the number of arguments are exactly one (or two?) (0 is the program/script name, 1 the first argument) and otherwise throw a helpful error message. In bash, the number of args is $#

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: tests Tests and CI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants