summaryrefslogtreecommitdiffstats
path: root/package
diff options
context:
space:
mode:
authorRomain Naour <romain.naour@smile.fr>2019-01-16 22:39:21 +0100
committerPeter Korsgaard <peter@korsgaard.com>2019-01-17 09:56:49 +0100
commitd3245ce4258f4f5e5230e976862a0fd40fdd1890 (patch)
treedf9e067a7e0f4395aae2f47a818c884069ffce95 /package
parent96d90ae4e782559c78ae48de5230a9e3a8a08964 (diff)
downloadbuildroot-d3245ce4258f4f5e5230e976862a0fd40fdd1890.tar.gz
buildroot-d3245ce4258f4f5e5230e976862a0fd40fdd1890.zip
package/llvm: set the path to llvm-config
While building llvm for the target (x86_64), the build failed due to path poisoning (-I/usr/include/libxml2) while building NATIVE tools (i.e for the host). The llvm package tries to build a tool for the host with the cross-compiler which doesn't work when the paranoid toolchain wrapper (BR2_COMPILER_PARANOID_UNSAFE_PATH) is enabled. We know that llvm (target) needs llvm-tablegen and llvm-config built by host-llvm, but only LLVM_TABLEGEN is provided by llvm.mk. Adding LLVM_CONFIG_PATH=$(HOST_DIR)/bin/llvm-config for llvm (target) fixes the path poisoining issue since llvm doesn't build the NATIVE variant. Signed-off-by: Romain Naour <romain.naour@smile.fr> Cc: Valentin Korenblit <valentinkorenblit@gmail.com> Cc: Matthew Weber <matthew.weber@rockwellcollins.com> Tested-by: Matthew Weber <matthew.weber@rockwellcollins.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Diffstat (limited to 'package')
-rw-r--r--package/llvm/llvm.mk3
1 files changed, 3 insertions, 0 deletions
diff --git a/package/llvm/llvm.mk b/package/llvm/llvm.mk
index f33ec11fbf..952f678eee 100644
--- a/package/llvm/llvm.mk
+++ b/package/llvm/llvm.mk
@@ -57,6 +57,9 @@ endif
# Use native llvm-tblgen from host-llvm (needed for cross-compilation)
LLVM_CONF_OPTS += -DLLVM_TABLEGEN=$(HOST_DIR)/bin/llvm-tblgen
+# Use native llvm-config from host-llvm (needed for cross-compilation)
+LLVM_CONF_OPTS += -DLLVM_CONFIG_PATH=$(HOST_DIR)/bin/llvm-config
+
# BUILD_SHARED_LIBS has a misleading name. It is in fact an option for
# LLVM developers to build all LLVM libraries as separate shared libraries.
# For normal use of LLVM, it is recommended to build a single
OpenPOWER on IntegriCloud