From 27b76ab0671089c47506615a796a261e993896a7 Mon Sep 17 00:00:00 2001 From: James <> Date: Sun, 17 Mar 2013 12:16:37 +0000 Subject: fish --- .../patches/100-disable_compat_cmd.patch | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 tools/pkg-config/patches/100-disable_compat_cmd.patch (limited to 'tools/pkg-config/patches/100-disable_compat_cmd.patch') diff --git a/tools/pkg-config/patches/100-disable_compat_cmd.patch b/tools/pkg-config/patches/100-disable_compat_cmd.patch new file mode 100644 index 0000000..9907840 --- /dev/null +++ b/tools/pkg-config/patches/100-disable_compat_cmd.patch @@ -0,0 +1,22 @@ +--- a/parse.c ++++ b/parse.c +@@ -1187,15 +1187,12 @@ try_command (const char *command) + Package * + get_compat_package (const char *name) + { +-#ifdef G_OS_WIN32 +- /* There has never been any of these legacy *-config scripts on +- * Windows as far as I know. No use trying to execute them, will +- * only confuse users to see the "blabla is not recognized as an +- * internal or external command, operable program or batch file" +- * messages. ++ /* ++ * We don't need this compatibility stuff on a system ++ * that is free of legacy stuff + */ + return NULL; +-#else ++#if 0 + + Package *pkg; + -- cgit v1.2.3