llvm: filter clang-ocl from the executables being probed (#47536)
This filters any selected executable ending with `-ocl` from the list of executables being probed as candidate for external `llvm` installations. I couldn't reproduce the entire issue, but with a simple script: ``` #!/bin/bash touch foo.o echo "clang version 10.0.0-4ubuntu1 " echo "Target: x86_64-pc-linux-gnu" echo "Thread model: posix" echo "InstalledDir: /usr/bin" exit 0 ``` I noticed the executable was still probed: ``` $ spack -d compiler find /tmp/ocl [ ... ] ==> [2024-11-11-08:38:41.933618] '/tmp/ocl/bin/clang-ocl' '--version' ``` and `foo.o` was left in the working directory. With this change, instead the executable is filtered out of the list on which we run `--version`, so `clang-ocl --version` is not run by Spack.
This commit is contained in:
parent
c4a5a996a5
commit
84d33fccce
@ -28,7 +28,7 @@ def filter_detected_exes(cls, prefix, exes_in_prefix):
|
||||
# Executables like lldb-vscode-X are daemon listening on some port and would hang Spack
|
||||
# during detection. clang-cl, clang-cpp, etc. are dev tools that we don't need to test
|
||||
reject = re.compile(
|
||||
r"-(vscode|cpp|cl|gpu|tidy|rename|scan-deps|format|refactor|offload|"
|
||||
r"-(vscode|cpp|cl|ocl|gpu|tidy|rename|scan-deps|format|refactor|offload|"
|
||||
r"check|query|doc|move|extdef|apply|reorder|change-namespace|"
|
||||
r"include-fixer|import-test|dap|server)"
|
||||
)
|
||||
|
Loading…
Reference in New Issue
Block a user