| Issue |
52910
|
| Summary |
[openmp] build wrongly picking up AMDGCN target on linux for 13.0.1-rc1
|
| Labels |
new issue
|
| Assignees |
|
| Reporter |
h-vetinari
|
Trying to build openmp 13.0.1-rc1 for [conda-forge](https://github.com/conda-forge/openmp-feedstock/pull/55), during the config phase, it seems AMDGCN is wrongly activated, despite clang-tools not being available.
```
-- LIBOMPTARGET: Building offloading runtime library libomptarget.
-- LIBOMPTARGET: Not building aarch64 offloading plugin: machine not found in the system.
-- LIBOMPTARGET: Not building AMDGPU plugin: LIBELF not found
-- LIBOMPTARGET: Not building CUDA offloading plugin: libelf dependency not found.
-- LIBOMPTARGET: Not building PPC64 offloading plugin: machine not found in the system.
-- LIBOMPTARGET: Not building PPC64le offloading plugin: machine not found in the system.
-- LIBOMPTARGET: Not building nec-aurora plugin: libveo or libveosinfo not found.
-- LIBOMPTARGET: Not building x86_64 offloading plugin: libelf dependency not found.
-- LIBOMPTARGET: Building AMDGCN device RTL. Using clang: CLANG_TOOL-NOTFOUND
-- LIBOMPTARGET: Not building NVPTX deviceRTL by default on CUDA free system.
-- LIBOMPTARGET: Not building NVPTX deviceRTL by default on CUDA free system.
-- LIBOMPTARGET: Building the llvm-omp-device-info tool
```
This later leads to a build-error.
Given the solitary "Building AMDGCN [...]" in a sea of "Not building [...]", I'm thinking there's something off here with the detection.
![]()
_______________________________________________
llvm-bugs mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
