Hi Reuben, > The test for whether to use valgrind runs: > > /bin/bash -c 'exit 0' > > This looks pretty harmless; unfortunately, bash itself causes problems:
I'd suggest that you change m4/valgrind-tests.m4 to use the AC_CACHE_CHECK macro instead of "lone" AC_MSG_CHECKING and AC_MSG_RESULT invocations. Then you have an cache variable that you set as an environment variable in order to override the result of this test, e.g. $ env gl_cv_use_valgrind=yes ./configure Remember, nowadays that the autoconf cache is disabled by default, the major benefit of AC_CACHE_CHECK is that it provides the user a way to selectively override configure test results. Bruno
