On 27/01/14 15:59, Nick Bowler wrote: > On 2014-01-27 15:50 +0100, Daniel Pocock wrote: >> On 27/01/14 14:27, Eric Blake wrote: > [...] >>> Stick this in your configure.ac: >>> >>> m4_pattern_forbid([PKG_*]) >>> >>> then anyone running autoconf on your package without the pkg-config m4 >>> modules installed will get an earlier error at autoconf time flagging >>> the unexpanded macro, rather than a late error at configure execution of >>> a shell syntax error or unfound command. >> I tried adding that just under AM_INIT_AUTOMAKE >> https://github.com/resiprocate/resiprocate/blob/master/configure.ac >> >> autoreconf now fails even if pkg-config is present, here is the output: >> >> $ autoreconf -fi > [...] >> configure:1477: error: possibly undefined macro: PKGS >> If this token and others are legitimate, please use m4_pattern_allow. >> See the Autoconf documentation. >> configure:16327: error: possibly undefined macro: ac_cv_env_PKG_CONFIG_set >> configure:16333: error: possibly undefined macro: ac_cv_path_PKG_CONFIG >> configure:16371: error: possibly undefined macro: ac_pt_PKG_CONFIG >> configure:16376: error: possibly undefined macro: >> ac_cv_path_ac_pt_PKG_CONFIG >> configure:16508: error: possibly undefined macro: DEPS_PYTHON_PKG_ERRORS >> autoreconf: /usr/bin/autoconf failed with exit status: 1 > m4_pattern_forbid([^PKG_]) should work a bit better (untested). Thanks, that appears to work _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx https://lists.gnu.org/mailman/listinfo/autoconf
