Some message fixes

[Peter Eisentraut]

I have found a couple of messages (AC_MSG_*) that were spelled or worded
inconsistently.  Please use the attached patch if you agree.

I general, I have used the "lower case, no period" rule when it seemed
consistent with the other messages.

A couple of specific comments:

-test -z "$CC" && AC_MSG_ERROR([no acceptable cc found in \$PATH])
+test -z "$CC" && AC_MSG_ERROR([no acceptable C compiler found in \$PATH])

This is more clear because you're not necessarily looking for a compiler
called "cc".

-    *)  AC_MSG_ERROR([expected an absolute path for --$ac_var: $ac_val]);;
+    *)  AC_MSG_ERROR([expected an absolute directory name for --$ac_var: 
$ac_val]);;

See GNU Coding Standards for the reserved meaning of "path".  It's kind of
annoying, but it's good to be precise.

-[AC_MSG_CHECKING([for executable suffix])
+[AC_MSG_CHECKING([for suffix of executables])

It's not the suffix that's executable.

- [AC_MSG_ERROR([cannot compute EXEEXT: cannot compile and link])])
+ [AC_MSG_ERROR([cannot compute suffix of executables: cannot compile and 
link])])

Just to be consistent with the "checking..." message that precedes it.

-- 
Peter Eisentraut   address@hidden

msg-patch
Description: Patch