Files
poky/meta/recipes-support/libffi/libffi/not-win32.patch
Ross Burton aa0c57f6a5 libffi: refresh patches
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.

Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450).  This is obviously bad.

We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.

(From OE-Core rev: 7ae4ce08071c02beaf09675c2c1ed70617b797dd)

Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-03-09 09:17:02 -08:00

27 lines
1.1 KiB
Diff

libffi's configure assumes that cross-compiled builds are complicated and
introduces convoluted path manipulation involving gcc search paths to the
install paths, resulting in paths like -L/usr/lib/../lib/ appearing in
libffi.pc. When pkg-config is then used to obtain the linker flags for libffi
it can't tell that this path is on the default search path and returns
$SYSROOT/usr/lib/../lib which then gets written all over the target sysroot.
This then means the sstate can't be shared and triggers QA errors.
As this block is generally pointless, disable it.
Upstream-Status: Inappropriate
Signed-off-by: Ross Burton <ross.burton@intel.com>
Index: libffi-3.2.1/configure.ac
===================================================================
--- libffi-3.2.1.orig/configure.ac
+++ libffi-3.2.1/configure.ac
@@ -592,7 +592,7 @@ AC_ARG_ENABLE(purify-safety,
# These variables are only ever used when we cross-build to X86_WIN32.
# And we only support this with GCC, so...
-if test "x$GCC" = "xyes"; then
+if false; then
if test -n "$with_cross_host" &&
test x"$with_cross_host" != x"no"; then
toolexecdir="${exec_prefix}"/'$(target_alias)'