We should not quote the PKG_CONFIG setting as this deviates from the
canonical upstream behavior that gets integrated with all other build
systems, and deviates from how we treat all other toolchain variables
that we get from the environment.
Ultimately, the point is that it breaks passing custom flags directly
to pkg-config via the env var where this normally works elsewhere,
and it used to work in the past.
Signed-off-by: Mike Frysinger <vap...@gentoo.org>
---
v2
- rebased onto latest master
- people were happy with this in the previous thread:
http://permalink.gmane.org/gmane.comp.emulators.qemu/160198
configure | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/configure b/configure
index 95dc66b..9c14ab6 100755
--- a/configure
+++ b/configure
@@ -291,7 +291,7 @@ strip="${STRIP-${cross_prefix}strip}"
windres="${WINDRES-${cross_prefix}windres}"
pkg_config_exe="${PKG_CONFIG-${cross_prefix}pkg-config}"
query_pkg_config() {
- "${pkg_config_exe}" ${QEMU_PKG_CONFIG_FLAGS} "$@"
+ ${pkg_config_exe} ${QEMU_PKG_CONFIG_FLAGS} "$@"
}
pkg_config=query_pkg_config
sdl_config="${SDL_CONFIG-${cross_prefix}sdl-config}"
@@ -1424,7 +1424,7 @@ fi
##########################################
# pkg-config probe
-if ! has "$pkg_config_exe"; then
+if ! has $pkg_config_exe; then
error_exit "pkg-config binary '$pkg_config_exe' not found"
fi
--
1.8.2.1
