[PATCH v2 wayland-protocols] configure.ac: Don't use AC_CANONICAL_* macro calls

Jussi Kukkonen jussi.kukkonen at intel.com
Thu Feb 18 14:03:35 UTC 2016

Check autoconfs $cross_compiling instead as AC_CANONICAL_HOST call
will fail if the host cpu is not recognised (which can happen when
e.g. Yocto builds for "allarch").

Signed-off-by: Jussi Kukkonen <jussi.kukkonen at intel.com>
 configure.ac | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/configure.ac b/configure.ac
index 90cce42..6d9bc0e 100644
--- a/configure.ac
+++ b/configure.ac
@@ -15,13 +15,10 @@ AC_CONFIG_MACRO_DIR([m4])
 AC_SUBST([WAYLAND_PROTOCOLS_VERSION], [wayland_protocols_version])
 AC_ARG_VAR([wayland_scanner], [The wayland-scanner executable])
 AC_PATH_PROG([wayland_scanner], [wayland-scanner])
 if test x$wayland_scanner = x; then
-        if test x$host = x$build; then
+        if test "x$cross_compiling" != "xyes"; then
                 PKG_CHECK_MODULES(WAYLAND_SCANNER, [wayland-scanner])
                 wayland_scanner=`$PKG_CONFIG --variable=wayland_scanner wayland-scanner`

More information about the wayland-devel mailing list