diff options
author | Massimiliano Culpo <massimiliano.culpo@gmail.com> | 2024-11-11 13:05:01 +0100 |
---|---|---|
committer | GitHub <noreply@github.com> | 2024-11-11 05:05:01 -0700 |
commit | 84d33fccce5d4395091b63a2aa8a1ee61ecbc5af (patch) | |
tree | b20f78f637ab5028239c3743fd918820fc68f9b6 /SECURITY.md | |
parent | c4a5a996a54b0e9385c9311aea0efbe6df00de28 (diff) | |
download | spack-84d33fccce5d4395091b63a2aa8a1ee61ecbc5af.tar.gz spack-84d33fccce5d4395091b63a2aa8a1ee61ecbc5af.tar.bz2 spack-84d33fccce5d4395091b63a2aa8a1ee61ecbc5af.tar.xz spack-84d33fccce5d4395091b63a2aa8a1ee61ecbc5af.zip |
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.
Diffstat (limited to 'SECURITY.md')
0 files changed, 0 insertions, 0 deletions