2005-05-12 Paul Eggert <eggert@CS.UCLA.EDU>

Explanation for this subtle change:

	From: Paul Eggert <eggert@CS.UCLA.EDU>
	To: config-patches
	Subject: config.guess, config.sub misdiagnose write errors

	config.guess and config.sub sometimes mishandle write errors to
	stdout: they either ignore the errors, or output invalid
	diagnostics when they occur.  For a simple (albeit unrealistic)
	example, on my Solaris 8 (sparc) host, the command "config.guess
	>&-" exits with status 0; it should exit with status 1, due to the
	write failure.

	* config.guess: Don't exit with an explicit exit code of 0.
	* config.sub: Likewise.

config.sub

@@ -83,11 +83,11 @@ Try \`$me --help' for more information."
 while test $# -gt 0 ; do
   case $1 in
     --time-stamp | --time* | -t )
-       echo "$timestamp" ; exit 0 ;;
+       echo "$timestamp" ; exit ;;
     --version | -v )
-       echo "$version" ; exit 0 ;;
+       echo "$version" ; exit ;;
     --help | --h* | -h )
-       echo "$usage"; exit 0 ;;
+       echo "$usage"; exit ;;
     -- )     # Stop option processing
        shift; break ;;
     - )	# Use stdin as input.
@@ -99,7 +99,7 @@ while test $# -gt 0 ; do
     *local*)
        # First pass through any local machine types.
        echo $1
-       exit 0;;
+       exit ;;
 
     * )
        break ;;
@@ -1559,7 +1559,7 @@ case $basic_machine in
 esac
 
 echo $basic_machine$os
-exit 0
+exit
 
 # Local variables:
 # eval: (add-hook 'write-file-hooks 'time-stamp)