-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to John Gatewood Ham on 10/8/2005 2:07 PM:
> GNU m4 people,
> 
> When invoking m4 if you specify a file that does not exist
> the return code when exiting is still 0 but you have an error
> message.  The man page shows that you will exit with 0
> only if there are no errors.  I am using version 1.4.3
> compiled from source.

This is indeed a bug in 1.4.3, contrary to POSIX (which requires that if a
program output diagnostic information to stderr, it fail with a nonzero
exit status).

> 
> "EXIT STATUS
>        The following exit values shall be returned:
> 
>         0     Successful completion.
> 
>        >0     An error occurred"

A missing (or unreadable) input file counts as an error, and m4 should be
patched to return 1 in that case.

> The README file says send bugs to [EMAIL PROTECTED],
> but the web page here http://www.seindal.dk/rene/gnu/feedback.htm
> says send them to [email protected]
> 
> I sent it to both places to be sure.  I hope at least one
> of the addresses was the correct place to send this bug report.

bug-m4 is probably the best m4-specific list (and the one where I saw this
mail), but <bug-gnu-utils AT gnu DOT org> is also well read.  The
prep.ai.mit.edu domain is a holdover from historical past, although it may
still forward properly.  In any case, you did the right thing in reporting
it.  Just be aware that the official m4 maintainer is currently occupied
with trying to get libtool 2.0 ready to release, so it may be a while
before a patch to m4 is provided (unless you can volunteer to help
contribute one).

- --
Life is short - so eat dessert first!

Eric Blake             [EMAIL PROTECTED]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDSHJl84KuGfSFAYARAlaTAKDXiPKWfoNj0hpeDKs6iS+lk8/YCQCgpmNY
7BKmqYDDRBa7rmNqnXxsjnU=
=OMRy
-----END PGP SIGNATURE-----


_______________________________________________
Bug-m4 mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-m4

Reply via email to