-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to Matthew Woehlke on 3/8/2007 10:59 AM:
> Matthew Woehlke wrote:
>> Well, it seems to have gotten past lib/ anyway. Will report back with
>> how the test suite goes...
>
> Ok, 'make check results'... I got this:
>
> Checking ./012.macro_argu
> @ ../doc/m4.texinfo:1358: Origin of test
> ./012.macro_argu: status was 255, expected 1
Does your platform #define EXIT_FAILURE to 255 in <stdlib.h>? If so, what
exit status does /bin/false give? Should gnulib override EXIT_FAILURE to
be 1 for consistency, or honor weird platforms that choose some other
value (as is their right, according to POSIX) in which case I should teach
the M4 testsuite to allow the system's notion of EXIT_FAILURE? One of the
problems with setting EXIT_FAILURE to 255 is that it interferes with the
POSIX rules for how xargs behaves, if that is an argument for replacing
your unusual value with the more typical 1.
>
> 84-89 were skipped ("no changeword support")
You have to configure with --enable-changeword if you want this feature;
partly because it is obsolete and will not be supported in the eventual M4
2.0.
- --
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
iD8DBQFF8PUr84KuGfSFAYARAiPsAJ9bVg8EMrzXKN/97vuSimX6m3th9wCgtKSN
77OYN+PMR2Wl0ZpqFq8lMDA=
=qoBv
-----END PGP SIGNATURE-----
