-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to Thomas Moulard on 4/13/2009 6:00 AM:
> About the "which" issue, Valgrind does not need an absolute path, it is just
> that I used to rely on the fact that my binaries are always in my PATH.
autotest can be made to guarantee that the binary under test IS in your
PATH. That's the point of the AUTOTEST_PATH special variable, which in
turn is set to default to the directory passed to AC_CONFIG_TESTDIR. From
the manual, note how you can use AUTOTEST_PATH to satisfy both 'make
check' and 'make installcheck':
check-local: atconfig atlocal $(TESTSUITE)
$(SHELL) '$(TESTSUITE)' $(TESTSUITEFLAGS)
installcheck-local: atconfig atlocal $(TESTSUITE)
$(SHELL) '$(TESTSUITE)' AUTOTEST_PATH='$(bindir)' \
$(TESTSUITEFLAGS)
- --
Don't work too hard, make some time for fun as well!
Eric Blake ebb9@xxxxxxx
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAknjKr0ACgkQ84KuGfSFAYBEogCgpjw+dKbGOFiqSFh1L1npaew9
/ocAnReOhwTXL0Qa7N1TMuvtDW+ux1Lo
=EHr/
-----END PGP SIGNATURE-----
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf
