[all-commits] [llvm/llvm-project] 16de50: honor Python2_EXECUTABLE and Python3_EXECUTABLE wh...
Robert Underwood via All-commits
all-commits at lists.llvm.org
Tue Nov 17 15:49:38 PST 2020
Branch: refs/heads/master
Home: https://github.com/llvm/llvm-project
Commit: 16de50895e96adbe261a5ce2498366bda7b3fccd
https://github.com/llvm/llvm-project/commit/16de50895e96adbe261a5ce2498366bda7b3fccd
Author: Robert Underwood <rr.underwood94 at gmail.com>
Date: 2020-11-17 (Tue, 17 Nov 2020)
Changed paths:
M compiler-rt/cmake/Modules/AddCompilerRT.cmake
Log Message:
-----------
honor Python2_EXECUTABLE and Python3_EXECUTABLE when they are passed to cmake
CMake's find_package(Python3) and find_package(Python2) packages have a PYTHON_EXECUTABLE, Python2_EXECUTABLE, and Python3_EXECUTABLE cmake variables which control which version of python is built against. As far as I can tell, the rest of LLVM honors these variables. This can cause the build process to fail when if the automatically selected version of Python can't run due to modifications of LD_LIBRARY_PATH when using spack. The corresponding Spack issue is https://github.com/spack/spack/issues/19908. The corresponding LLVM issue is 48180
I believe an appropriate fix is to add the variables to the list of PASSTHROUGH_VARIABLES in cmake/Modules/AddCompilerRT.cmake, and this fixed compilation errors for me.
This bug affects distributions like Gentoo and package managers like Spack which allow for combinatorial versioning.
Reviewed By: Meinersbur
Differential Revision: https://reviews.llvm.org/D91536
More information about the All-commits
mailing list