MaskRay added a comment. In D109977#3660734 <https://reviews.llvm.org/D109977#3660734>, @mgorny wrote:
> In D109977#3660006 <https://reviews.llvm.org/D109977#3660006>, @abrachet > wrote: > >> In D109977#3652467 <https://reviews.llvm.org/D109977#3652467>, @mgorny wrote: >> >>> Though I can reproduce it with much shorter: >>> >>> mkdir build >>> cd build >>> cmake ../clang -G Ninja >>> >>> (matching installed version of LLVM 15 must be on PATH) >> >> Are you sure it should be in PATH? I have added installed LLVM from ToT to a >> directory, put that in path yet CMake still finds >> /usr/lib/llvm-13/cmake/AddLLVM.cmake instead. I can't find any documentation >> on the standalone build, unfortunately. > > I'm sorry, what does "ToT" mean here? Also, what's `i`? Perhaps it's picking > it up from some other variable. In my case, it's finding the installed LLVM > 14 because that's the first PATH entry. Note that CMake looks into > `../lib*/cmake` and `../share/cmake` relative to PATH entries. FWICS it also > looks at `CMAKE_MODULE_PATH`. "Top of Trunk" (or tree?) which indicates the latest commit of origin/main . "Trunk" was a term inherited from the old subversion days. Debian installs different llvm packages to `/usr/lib/llvm-*`: % ls /usr/lib/llvm-* /usr/lib/llvm-11: bin/ build/ cmake@ include/ lib/ share/ /usr/lib/llvm-13: bin/ build/ cmake@ include/ lib/ share/ /usr/lib/llvm-9: bin/ build/ cmake@ include/ lib/ share/ For downstream reports (e.g. Debian, Gentoo), it is worth stripping the distribution specific knowledge so that a patch author doesn't need to install a particular distribution to reproduce an issue. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D109977/new/ https://reviews.llvm.org/D109977 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
