-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Ralf Wildenhues on 11/17/2007 5:34 AM: > Here we go with complete write failure checking in status.m4 for > everything not going to stderr or config.log. For auditing purposes, > I inspected the configure and config.status scripts of test 116 > (AC_CONFIG_FILES, HEADERS, LINKS and COMMANDS) manually, and for testing > purposes, I basically negated the output status of every writing command > (one at a time) to ensure that it provokes a test failure somewhere, and > that error output is sensible. I added tests to the suite for code > paths which apparently weren't exercised before.
Looks good to me. Thanks for spending the time on this. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHPuOD84KuGfSFAYARAkDyAJ97sRaPvOqJimCGNTiVCT8RWMhQIACgyQx5 /y3Z/O/+6VA4rFcqt47K9us= =Qhmk -----END PGP SIGNATURE-----
