Skip to content

Conversation

@rjodinchr
Copy link
Contributor

When building llvm from a subdirectory (like clspv does) CMAKE_BINARY_DIR is at the top of the build directory.

When building runtimes (libclc for example), the build fails looking for clang (through find_package looking at LLVM_BINARY_DIR with NO_DEFAULT_PATH & NO_CMAKE_FIND_ROOT_PATH) because clang is not in LLVM_BINARY_DIR.

Fix that issue by setting clang_cmake_builddir the same way we set llvm_cmake_builddir from LLVM_BINARY_DIR.

For default llvm build (using llvm as the main cmake project), it should not change anything.

@llvmbot llvmbot added the clang Clang issues not falling into any other category label Aug 28, 2025
@llvmbot
Copy link
Member

llvmbot commented Aug 28, 2025

@llvm/pr-subscribers-clang

Author: Romaric Jodin (rjodinchr)

Changes

When building llvm from a subdirectory (like clspv does) CMAKE_BINARY_DIR is at the top of the build directory.

When building runtimes (libclc for example), the build fails looking for clang (through find_package looking at LLVM_BINARY_DIR with NO_DEFAULT_PATH & NO_CMAKE_FIND_ROOT_PATH) because clang is not in LLVM_BINARY_DIR.

Fix that issue by setting clang_cmake_builddir the same way we set llvm_cmake_builddir from LLVM_BINARY_DIR.

For default llvm build (using llvm as the main cmake project), it should not change anything.


Full diff: https://github.com/llvm/llvm-project/pull/155844.diff

1 Files Affected:

  • (modified) clang/cmake/modules/CMakeLists.txt (+3-4)
diff --git a/clang/cmake/modules/CMakeLists.txt b/clang/cmake/modules/CMakeLists.txt
index d2d68121371bf..b3b4a74f6d470 100644
--- a/clang/cmake/modules/CMakeLists.txt
+++ b/clang/cmake/modules/CMakeLists.txt
@@ -8,15 +8,14 @@ include(FindPrefixFromConfig)
 # the usual CMake convention seems to be ${Project}Targets.cmake.
 set(CLANG_INSTALL_PACKAGE_DIR "${CMAKE_INSTALL_PACKAGEDIR}/clang" CACHE STRING
   "Path for CMake subdirectory for Clang (defaults to '${CMAKE_INSTALL_PACKAGEDIR}/clang')")
-# CMAKE_INSTALL_PACKAGEDIR might be absolute, so don't reuse below.
-set(clang_cmake_builddir "${CMAKE_BINARY_DIR}/lib${LLVM_LIBDIR_SUFFIX}/cmake/clang")
 
 # Keep this in sync with llvm/cmake/CMakeLists.txt!
 set(LLVM_INSTALL_PACKAGE_DIR "${CMAKE_INSTALL_PACKAGEDIR}/llvm" CACHE STRING
   "Path for CMake subdirectory for LLVM (defaults to '${CMAKE_INSTALL_PACKAGEDIR}/llvm')")
 # CMAKE_INSTALL_PACKAGEDIR might be absolute, so don't reuse below.
-string(REPLACE "${CMAKE_CFG_INTDIR}" "." llvm_cmake_builddir "${LLVM_LIBRARY_DIR}")
-set(llvm_cmake_builddir "${llvm_cmake_builddir}/cmake/llvm")
+string(REPLACE "${CMAKE_CFG_INTDIR}" "." llvm_builddir "${LLVM_LIBRARY_DIR}")
+set( llvm_cmake_builddir "${llvm_builddir}/cmake/llvm")
+set(clang_cmake_builddir "${llvm_builddir}/cmake/clang")
 
 get_property(CLANG_EXPORTS GLOBAL PROPERTY CLANG_EXPORTS)
 export(TARGETS ${CLANG_EXPORTS} FILE ${clang_cmake_builddir}/ClangTargets.cmake)

@rjodinchr
Copy link
Contributor Author

@frasercrmck please take a look

@rjodinchr rjodinchr changed the title [clang] clang_cmake_builddir [clang] fix clang_cmake_builddir Aug 28, 2025
When building llvm from a subdirectory (like clspv does)
`CMAKE_BINARY_DIR` is at the top of the build directory.

When building runtimes (libclc for example), the build fails looking
for clang (through `find_package` looking at `LLVM_BINARY_DIR` with
`NO_DEFAULT_PATH` & `NO_CMAKE_FIND_ROOT_PATH`) because clang is not in
`LLVM_BINARY_DIR`.

Fix that issue by setting `clang_cmake_builddir` the same way we set
`llvm_cmake_builddir` from `LLVM_BINARY_DIR`.

For default llvm build (using llvm as the main cmake project), it
should not change anything.
@rjodinchr rjodinchr force-pushed the pr/clang-cmake-builddir branch from 420b284 to bc8040d Compare August 28, 2025 14:30
Copy link
Contributor

@Keenuts Keenuts left a comment

Choose a reason for hiding this comment

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

Looks ok to me. So far seems like even on main, setting -DLLVM_LIBDIR_SUFFIX seem to have the same effect so seems like this is ok
Adding @kwk in case I'm missing something

@Keenuts Keenuts requested a review from kwk September 1, 2025 12:39
@kwk
Copy link
Contributor

kwk commented Sep 1, 2025

Looks ok to me. So far seems like even on main, setting -DLLVM_LIBDIR_SUFFIX has no effect so seems like this is ok Adding @kwk in case I'm missing something

@Keenuts am I really the person you had in mind when asking for a review?

@Keenuts
Copy link
Contributor

Keenuts commented Sep 1, 2025

@Keenuts am I really the person you had in mind when asking for a review?

Was searching for somebody who could double-check, saw you were part of the release status team, so guessed maybe you were familiar with the importants bits around those build directories bits? Do you know a better contact point?

@kwk
Copy link
Contributor

kwk commented Sep 1, 2025

@Keenuts am I really the person you had in mind when asking for a review?

Was searching for somebody who could double-check, saw you were part of the release status team, so guessed maybe you were familiar with the importants bits around those build directories bits? Do you know a better contact point?

Ah I see. @tru and @tstellar are probably more familiar with these bits.

@kwk kwk requested review from tru and tstellar and removed request for kwk September 1, 2025 15:10
Copy link
Contributor

@frasercrmck frasercrmck left a comment

Choose a reason for hiding this comment

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

I don't feel able to approve, I'm afraid.

@Keenuts
Copy link
Contributor

Keenuts commented Sep 8, 2025

@tstellar would you be the one to review the build files?

Copy link
Collaborator

@tstellar tstellar left a comment

Choose a reason for hiding this comment

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

LGTM. This seems OK to me since it's not going to affect most people's configuration.

@Keenuts Keenuts merged commit 61664b6 into llvm:main Sep 12, 2025
9 checks passed
@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 12, 2025

LLVM Buildbot has detected a new failure on builder openmp-s390x-linux running on systemz-1 while building clang at step 6 "test-openmp".

Full details are available at: https://lab.llvm.org/buildbot/#/builders/88/builds/16017

Here is the relevant piece of the build log for the reference
Step 6 (test-openmp) failure: test (failure)
******************** TEST 'libomp :: tasking/issue-94260-2.c' FAILED ********************
Exit Code: -11

Command Output (stdout):
--
# RUN: at line 1
/home/uweigand/sandbox/buildbot/openmp-s390x-linux/llvm.build/./bin/clang -fopenmp   -I /home/uweigand/sandbox/buildbot/openmp-s390x-linux/llvm.build/runtimes/runtimes-bins/openmp/runtime/src -I /home/uweigand/sandbox/buildbot/openmp-s390x-linux/llvm.src/openmp/runtime/test -L /home/uweigand/sandbox/buildbot/openmp-s390x-linux/llvm.build/runtimes/runtimes-bins/openmp/runtime/src  -fno-omit-frame-pointer -mbackchain -I /home/uweigand/sandbox/buildbot/openmp-s390x-linux/llvm.src/openmp/runtime/test/ompt /home/uweigand/sandbox/buildbot/openmp-s390x-linux/llvm.src/openmp/runtime/test/tasking/issue-94260-2.c -o /home/uweigand/sandbox/buildbot/openmp-s390x-linux/llvm.build/runtimes/runtimes-bins/openmp/runtime/test/tasking/Output/issue-94260-2.c.tmp -lm -latomic && /home/uweigand/sandbox/buildbot/openmp-s390x-linux/llvm.build/runtimes/runtimes-bins/openmp/runtime/test/tasking/Output/issue-94260-2.c.tmp
# executed command: /home/uweigand/sandbox/buildbot/openmp-s390x-linux/llvm.build/./bin/clang -fopenmp -I /home/uweigand/sandbox/buildbot/openmp-s390x-linux/llvm.build/runtimes/runtimes-bins/openmp/runtime/src -I /home/uweigand/sandbox/buildbot/openmp-s390x-linux/llvm.src/openmp/runtime/test -L /home/uweigand/sandbox/buildbot/openmp-s390x-linux/llvm.build/runtimes/runtimes-bins/openmp/runtime/src -fno-omit-frame-pointer -mbackchain -I /home/uweigand/sandbox/buildbot/openmp-s390x-linux/llvm.src/openmp/runtime/test/ompt /home/uweigand/sandbox/buildbot/openmp-s390x-linux/llvm.src/openmp/runtime/test/tasking/issue-94260-2.c -o /home/uweigand/sandbox/buildbot/openmp-s390x-linux/llvm.build/runtimes/runtimes-bins/openmp/runtime/test/tasking/Output/issue-94260-2.c.tmp -lm -latomic
# executed command: /home/uweigand/sandbox/buildbot/openmp-s390x-linux/llvm.build/runtimes/runtimes-bins/openmp/runtime/test/tasking/Output/issue-94260-2.c.tmp
# note: command had no output on stdout or stderr
# error: command failed with exit status: -11

--

********************


@llvm-ci
Copy link
Collaborator

llvm-ci commented Sep 12, 2025

LLVM Buildbot has detected a new failure on builder clang-ppc64le-linux-test-suite running on ppc64le-clang-test-suite while building clang at step 6 "test-build-unified-tree-check-all".

Full details are available at: https://lab.llvm.org/buildbot/#/builders/95/builds/18194

Here is the relevant piece of the build log for the reference
Step 6 (test-build-unified-tree-check-all) failure: test (failure)
******************** TEST 'SanitizerCommon-asan-powerpc64le-Linux :: Linux/getpwnam_r_invalid_user.cpp' FAILED ********************
Exit Code: 134

Command Output (stderr):
--
/home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-test-suite/clang-ppc64le-test-suite/build/./bin/clang  --driver-mode=g++ -gline-tables-only -fsanitize=address  -m64 -fno-function-sections -funwind-tables  -I/home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-test-suite/clang-ppc64le-test-suite/llvm-project/compiler-rt/test -ldl -O0 -g /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-test-suite/clang-ppc64le-test-suite/llvm-project/compiler-rt/test/sanitizer_common/TestCases/Linux/getpwnam_r_invalid_user.cpp -o /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-test-suite/clang-ppc64le-test-suite/build/runtimes/runtimes-bins/compiler-rt/test/sanitizer_common/asan-powerpc64le-Linux/Linux/Output/getpwnam_r_invalid_user.cpp.tmp &&  /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-test-suite/clang-ppc64le-test-suite/build/runtimes/runtimes-bins/compiler-rt/test/sanitizer_common/asan-powerpc64le-Linux/Linux/Output/getpwnam_r_invalid_user.cpp.tmp # RUN: at line 2
+ /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-test-suite/clang-ppc64le-test-suite/build/./bin/clang --driver-mode=g++ -gline-tables-only -fsanitize=address -m64 -fno-function-sections -funwind-tables -I/home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-test-suite/clang-ppc64le-test-suite/llvm-project/compiler-rt/test -ldl -O0 -g /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-test-suite/clang-ppc64le-test-suite/llvm-project/compiler-rt/test/sanitizer_common/TestCases/Linux/getpwnam_r_invalid_user.cpp -o /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-test-suite/clang-ppc64le-test-suite/build/runtimes/runtimes-bins/compiler-rt/test/sanitizer_common/asan-powerpc64le-Linux/Linux/Output/getpwnam_r_invalid_user.cpp.tmp
+ /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-test-suite/clang-ppc64le-test-suite/build/runtimes/runtimes-bins/compiler-rt/test/sanitizer_common/asan-powerpc64le-Linux/Linux/Output/getpwnam_r_invalid_user.cpp.tmp
getpwnam_r_invalid_user.cpp.tmp: /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-test-suite/clang-ppc64le-test-suite/llvm-project/compiler-rt/test/sanitizer_common/TestCases/Linux/getpwnam_r_invalid_user.cpp:17: int main(): Assertion `res == 0 || res == ENOENT' failed.
/home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-test-suite/clang-ppc64le-test-suite/build/runtimes/runtimes-bins/compiler-rt/test/sanitizer_common/asan-powerpc64le-Linux/Linux/Output/getpwnam_r_invalid_user.cpp.script: line 1: 855875 Aborted                 /home/buildbots/llvm-external-buildbots/workers/ppc64le-clang-test-suite/clang-ppc64le-test-suite/build/runtimes/runtimes-bins/compiler-rt/test/sanitizer_common/asan-powerpc64le-Linux/Linux/Output/getpwnam_r_invalid_user.cpp.tmp

--

********************


@peterwaller-arm
Copy link
Contributor

peterwaller-arm commented Sep 15, 2025

Hi Folks, this results in .cmake files being written to the installation directory of LLVM. Is that intentional? If this is a system installation, this is not desirable, since it may be read-only, resulting in error messages of this form.

CMake Error: Could not open file for write in copy operation /nix/store/x63p9dancrmkihdqqvjri1pmmjab2hl4-llvm-22.0.0-git-2025-09-15-lib/lib/cmake/clang/ClangConfig.cmake.tmp
CMake Error: : System Error: No such file or directory
CMake Error at cmake/modules/CMakeLists.txt:31 (configure_file):
  configure_file Problem configuring file
>
CMake Error: Could not open file for write in copy operation /nix/store/x63p9dancrmkihdqqvjri1pmmjab2hl4-llvm-22.0.0-git-2025-09-15-lib/lib/cmake/clang/ClangConfigVersion.cmake.tmp
CMake Error: : System Error: No such file or directory
CMake Error at cmake/modules/CMakeLists.txt:35 (configure_file):
  configure_file Problem configuring file

This affects the nixpkgs build (likely others), and anywhere llvm is installed separately from clang, which is having to revert this patch to make the build work again: NixOS/nixpkgs#443041

Please could we entertain a revert and alternative solution?

@Keenuts
Copy link
Contributor

Keenuts commented Sep 15, 2025

(@rjodinchr FYI)

Hi, so to understand, is it when you do something like cmake -DCMAKE_INSTALL_DIR=some/privileged/location then this writes to the INSTALL_DIR when doing ninja -C build (so before the installation step?)

@peterwaller-arm
Copy link
Contributor

peterwaller-arm commented Sep 15, 2025

@Keenuts, no, the failing step is here (configure_file):

https://github.com/llvm/llvm-project/pull/155844/files#diff-62495e09a1db8772f9fa00287b8a845deb3f087649b1d0cf822e680dd83630aaR31-R38

which tries to write the config file during the cmake invocation.

@Keenuts
Copy link
Contributor

Keenuts commented Sep 15, 2025

@peterwaller-arm do you have a way to get/reproduce the cmake configuration command line?
This way we could check differences in practice and figure out what nixos and clspv require and find a common solution?

@peterwaller-arm
Copy link
Contributor

Here's the full set of cmake flags passed by the nix buildsystem. At a glance I suppose the problematic one is LLVM_DIR which points into an installation tree of LLVM, not a build tree.

-GNinja
-DCMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY=OFF
-DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON
-DCMAKE_BUILD_TYPE=Release
-DBUILD_TESTING=OFF
-DCMAKE_INSTALL_LOCALEDIR=/tmp/clangbuild/clang/outputs/lib/share/locale
-DCMAKE_INSTALL_LIBEXECDIR=/tmp/clangbuild/clang/outputs/lib/libexec
-DCMAKE_INSTALL_LIBDIR=/tmp/clangbuild/clang/outputs/lib/lib
-DCMAKE_INSTALL_DOCDIR=/tmp/clangbuild/clang/outputs/out/share/doc/Clang
-DCMAKE_INSTALL_INFODIR=/tmp/clangbuild/clang/outputs/out/share/info
-DCMAKE_INSTALL_MANDIR=/tmp/clangbuild/clang/outputs/out/share/man
-DCMAKE_INSTALL_INCLUDEDIR=/tmp/clangbuild/clang/outputs/dev/include
-DCMAKE_INSTALL_SBINDIR=/tmp/clangbuild/clang/outputs/out/sbin
-DCMAKE_INSTALL_BINDIR=/tmp/clangbuild/clang/outputs/out/bin
-DCMAKE_INSTALL_NAME_DIR=/tmp/clangbuild/clang/outputs/lib/lib
-DCMAKE_POLICY_DEFAULT_CMP0025=NEW
-DCMAKE_FIND_FRAMEWORK=LAST
-DCMAKE_STRIP=/nix/store/sf05r8srgh21m1804jvagbidggh05n08-gcc-wrapper-14.3.0/bin/strip
-DCMAKE_RANLIB=/nix/store/sf05r8srgh21m1804jvagbidggh05n08-gcc-wrapper-14.3.0/bin/ranlib
-DCMAKE_AR=/nix/store/sf05r8srgh21m1804jvagbidggh05n08-gcc-wrapper-14.3.0/bin/ar
-DCMAKE_C_COMPILER=gcc
-DCMAKE_CXX_COMPILER=g++
-DCMAKE_INSTALL_PREFIX=/tmp/clangbuild/clang/outputs/out
-DCLANG_INSTALL_PACKAGE_DIR:STRING=/tmp/clangbuild/clang/outputs/dev/lib/cmake/clang
-DCLANGD_BUILD_XPC:BOOL=FALSE
-DLLVM_ENABLE_RTTI:BOOL=TRUE
-DLLVM_TABLEGEN_EXE:STRING=/nix/store/397g98z1d143ij71gv9rmqkcdjpwsr81-llvm-tblgen-22.0.0-git-2025-09-15/bin/llvm-tblgen
-DCLANG_TABLEGEN:STRING=/nix/store/397g98z1d143ij71gv9rmqkcdjpwsr81-llvm-tblgen-22.0.0-git-2025-09-15/bin/clang-tblgen
-DCLANG_RESOURCE_DIR:STRING=/tmp/clangbuild/clang/outputs/lib/lib/clang/22
-DLLVM_INCLUDE_TESTS:BOOL=FALSE
-DCLANG_TIDY_CONFUSABLE_CHARS_GEN:STRING=/nix/store/397g98z1d143ij71gv9rmqkcdjpwsr81-llvm-tblgen-22.0.0-git-2025-09-15/bin/clang-tidy-confusable-chars-gen
-DLLVM_DIR:STRING=/nix/store/2mvq029g2inpa05fz8b51lhvxdwmxrhr-llvm-22.0.0-git-2025-09-15-dev/lib/cmake/llvm

@peterwaller-arm
Copy link
Contributor

peterwaller-arm commented Sep 15, 2025

At a glance I suppose the problematic one is LLVM_DIR which points into an installation tree of LLVM, not a build tree.

Not totally certain of this because it's actually pointing at the -dev/ output, whereas the problematic write location is actually in the -lib/ directory.

From the CMakeCache I have:

LLVM_BINARY_DIR:PATH=/nix/store/x63p9dancrmkihdqqvjri1pmmjab2hl4-llvm-22.0.0-git-2025-09-15-lib
LLVM_LIBRARY_DIR:PATH=/nix/store/x63p9dancrmkihdqqvjri1pmmjab2hl4-llvm-22.0.0-git-2025-09-15-lib/lib

which are installation trees.

These come via the installed cmake files:

/nix/store/2mvq029g2inpa05fz8b51lhvxdwmxrhr-llvm-22.0.0-git-2025-09-15-dev/lib/cmake/llvm $ rg x63p9dancrmkihdqqvjri1pmmjab2hl4
LLVMConfig.cmake
331:set(LLVM_LIBRARY_DIRS "/nix/store/x63p9dancrmkihdqqvjri1pmmjab2hl4-llvm-22.0.0-git-2025-09-15-lib/lib${LLVM_LIBDIR_SUFFIX}")
342:set(LLVM_LIBRARY_DIR "/nix/store/x63p9dancrmkihdqqvjri1pmmjab2hl4-llvm-22.0.0-git-2025-09-15-lib/lib${LLVM_LIBDIR_SUFFIX}")
348:set(LLVM_BINARY_DIR "/nix/store/x63p9dancrmkihdqqvjri1pmmjab2hl4-llvm-22.0.0-git-2025-09-15-lib")

@Keenuts
Copy link
Contributor

Keenuts commented Sep 15, 2025

Thanks, I can reproduce with the following steps:

$ cmake -Hllvm -GNinja -B/tmp/nix-llvm/ -DBUILD_TESTING=OFF \
  -DCLANGD_BUILD_XPC:BOOL=FALSE -DLLVM_ENABLE_RTTI:BOOL=TRUE \
  -DLLVM_INCLUDE_TESTS:BOOL=FALSE -DCMAKE_BUILD_TYPE=Debug \
  -DLLVM_OPTIMIZED_TABLEGEN=1 -DLLVM_ENABLE_LLD=1 \
  -DCMAKE_LINKER=lld-link -DLLVM_USE_SPLIT_DWARF=1 \
  -DCMAKE_INSTALL_PREFIX=/tmp/nix-llvm-install
$ ninja -C /tmp/nix-llvm install
$ chmod -R -w /tmp/nix-llvm-install
$ cmake -Hclang -GNinja -B/tmp/nix-clang/ -DBUILD_TESTING=OFF \
  -DCLANGD_BUILD_XPC:BOOL=FALSE -DLLVM_ENABLE_RTTI:BOOL=TRUE \
  -DLLVM_INCLUDE_TESTS:BOOL=FALSE -DCMAKE_BUILD_TYPE=Debug \
  -DLLVM_OPTIMIZED_TABLEGEN=1 -DLLVM_ENABLE_LLD=1 \
  -DCMAKE_LINKER=lld-link -DLLVM_USE_SPLIT_DWARF=1 \
  -DCMAKE_CXX_COMPILER=clang++-17 -DCMAKE_C_COMPILER=clang-17 \
  -DLLVM_DIR:STRING=/tmp/nix-llvm-install/lib/cmake/llvm \
  -DLLVM_LINK_LLVM_DYLIB=ON \
  -DCMAKE_INSTALL_PREFIX=/tmp/nix-clang-install
-- Building with -fPIC
-- Clang version: 22.0.0git
CMake Error: Could not open file for write in copy operation /tmp/nix-llvm-install/lib/cmake/clang/ClangConfig.cmake.tmp
CMake Error: : System Error: Permission denied
CMake Error at cmake/modules/CMakeLists.txt:31 (configure_file):
  configure_file Problem configuring file


CMake Error: Could not open file for write in copy operation /tmp/nix-llvm-install/lib/cmake/clang/ClangConfigVersion.cmake.tmp
CMake Error: : System Error: Permission denied
CMake Error at cmake/modules/CMakeLists.txt:35 (configure_file):
  configure_file Problem configuring file

Keenuts added a commit that referenced this pull request Sep 15, 2025
peterwaller-arm pushed a commit that referenced this pull request Sep 16, 2025
Reverts #155844

Romaric is OOO for the next 2 weeks and I don't have the context on the
other part (clspv) to propose a fix forward.
Reverting for now.
llvm-sync bot pushed a commit to arm/arm-toolchain that referenced this pull request Sep 16, 2025
Reverts llvm/llvm-project#155844

Romaric is OOO for the next 2 weeks and I don't have the context on the
other part (clspv) to propose a fix forward.
Reverting for now.
@rjodinchr rjodinchr deleted the pr/clang-cmake-builddir branch September 29, 2025 07:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

clang Clang issues not falling into any other category

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants