================
@@ -47,6 +47,14 @@ if(${LLVM_NATIVE_ARCH} MATCHES
"^(AArch64|Hexagon|Sparc|SystemZ)$")
set(RUN_PYTHON_TESTS FALSE)
endif()
+# Tests will fail if cross-compiling for a different target, as tests will try
+# to use the host Python3_EXECUTABLE and make FFI calls to functions in target
+# libraries.
+if(CMAKE_CROSS_COMPILING)
----------------
Endilll wrote:
Do I understand correctly that you don't have this kind of problem with
"regular" tests in `clang/test`? If so, I think it'd be novel to say that tests
for entire components are second-class citizens simply because said components
are written in Python. As far as commitments go, I think our default here is to
support all kinds of tests.
That said, I understand that complexity is there (it appears that nothing is
easy in cross-compiling), and what you described doesn't seem to be too
convoluted, given the inherent complexity of the problem. We can leave this out
of scope of this PR, but I'd expect that claiming official support for
cross-compiling environments is going to be blocked on this.
https://github.com/llvm/llvm-project/pull/111657
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
