blob: 80c40a4742d7d3871afbcbf06c89bf69cd29c3da [file] [log] [blame]
Patrick Williamsd8c66bc2016-06-20 12:57:21 -05001libffi's configure assumes that cross-compiled builds are complicated and
2introduces convoluted path manipulation involving gcc search paths to the
3install paths, resulting in paths like -L/usr/lib/../lib/ appearing in
4libffi.pc. When pkg-config is then used to obtain the linker flags for libffi
5it can't tell that this path is on the default search path and returns
6$SYSROOT/usr/lib/../lib which then gets written all over the target sysroot.
7This then means the sstate can't be shared and triggers QA errors.
8
9As this block is generally pointless, disable it.
10
11Upstream-Status: Inappropriate
12Signed-off-by: Ross Burton <ross.burton@intel.com>
13
Brad Bishop316dfdd2018-06-25 12:45:53 -040014Index: libffi-3.2.1/configure.ac
15===================================================================
16--- libffi-3.2.1.orig/configure.ac
17+++ libffi-3.2.1/configure.ac
18@@ -592,7 +592,7 @@ AC_ARG_ENABLE(purify-safety,
19
Patrick Williamsd8c66bc2016-06-20 12:57:21 -050020 # These variables are only ever used when we cross-build to X86_WIN32.
21 # And we only support this with GCC, so...
22-if test "x$GCC" = "xyes"; then
23+if false; then
24 if test -n "$with_cross_host" &&
Brad Bishop316dfdd2018-06-25 12:45:53 -040025 test x"$with_cross_host" != x"no"; then
26 toolexecdir="${exec_prefix}"/'$(target_alias)'