libxcb: 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: 4a3d8806d25e146be40eaf640bc6da8bdd1b6e05)

Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Ross Burton
2017-11-15 16:44:50 +00:00
committed by Richard Purdie
parent d2a270bf69
commit 709552d96a

View File

@@ -9,17 +9,17 @@ Upstream-Status: Inappropriate
Signed-off-by: Ross Burton <ross.burton@intel.com>
diff --git a/configure.ac b/configure.ac
index 6d7c9a5..22cceb9 100644
--- a/configure.ac
+++ b/configure.ac
@@ -21,7 +21,8 @@ AC_USE_SYSTEM_EXTENSIONS
AM_PATH_PYTHON([2.6])
Index: libxcb-1.12/configure.ac
===================================================================
--- libxcb-1.12.orig/configure.ac
+++ libxcb-1.12/configure.ac
@@ -36,7 +36,8 @@ if test x"$HAVE_DOT" = xno; then
AC_MSG_WARN([dot not found - doxygen targets will be skipped])
fi
-PKG_CHECK_MODULES(CHECK, [check >= 0.9.4], [HAVE_CHECK=yes], [HAVE_CHECK=no])
+dnl PKG_CHECK_MODULES(CHECK, [check >= 0.9.4], [HAVE_CHECK=yes], [HAVE_CHECK=no])
+HAVE_CHECK=no
AM_CONDITIONAL(HAVE_CHECK, test x$HAVE_CHECK = xyes)
AC_CONFIG_HEADERS([src/config.h])
XSLTPROC=no