Reducing "badness" for TeX

[Pavel Roskin]

Hello!

Some of the examples in the manual were too long and caused warnings while
generating autoconf.dvi. I have examined them all. I could rewrite them to
avoid "badness". I only did it when I could put a better text. Also some
typos around have been fixed.

The INSTALL file will be rebuilt and committed too.

ChangeLog:
        * doc/install.texi: Minor changes to eliminate TeX warnings.
        * doc/autoconf.texi: Likewise. Typo fixes.

Regards,
Pavel Roskin

_______________________
Index: doc/autoconf.texi
--- doc/autoconf.texi   Fri Nov 17 12:27:15 2000
+++ doc/autoconf.texi   Thu Nov 23 18:42:10 2000
@@ -1037,11 +1037,11 @@

 @example
 /tmp % ace -Wcross
-configure.in:8: warning: AC_TRY_RUN called without default to allow \
-cross compiling
+configure.in:8: warning: AC_TRY_RUN called without default \
+to allow cross compiling
 /tmp % ace -Wcross,error
-configure.in:8: error: AC_TRY_RUN called without default to allow \
-cross compiling
+configure.in:8: error: AC_TRY_RUN called without default \
+to allow cross compiling
 acgeneral.m4:3044: AC_TRY_RUN is expanded from...
 configure.in:2: INNER is expanded from...
 configure.in:5: OUTTER is expanded from...
@@ -1518,7 +1518,7 @@

 This section describes the common behavior of the four standard
 instantiating macros: @code{AC_CONFIG_FILES}, @code{AC_CONFIG_HEADERS},
-macro @code{AC_CONFIG_COMMANDS}, and @code{AC_CONFIG_LINKS}.  They all
address@hidden and @code{AC_CONFIG_LINKS}.  They all
 have this prototype:

 @c Can't use @ovar here, Texinfo 4.0 goes lunatic and emits something
@@ -1910,9 +1910,9 @@
 current value of @code{prefix}.

 A corollary is that you should not use these variables but in
-Makefiles.  For instance instead of trying to resolve the dependencies
-of @code{datadir} upon @code{prefix} and using
address@hidden(DATADIR, "$datadir")}, you should add
+Makefiles.  For instance, instead of trying evaluate @code{datadir}
+in @file{configure} and hardcoding it in Makefiles using
+e.g. @samp{AC_DEFINE_UNQUOTED(DATADIR, "$datadir")}, you should add
 @samp{-DDATADIR="$(datadir)"} to your @code{CFLAGS}.

 Similarly you should not rely on @code{AC_OUTPUT_FILES} to replace
@@ -3906,7 +3906,7 @@

 @example
 AC_CHECK_MEMBER(struct passwd.pw_gecos,,
-                [AC_MSG_ERROR([We need `struct passwd.pw_gecos'!])],
+                [AC_MSG_ERROR([We need `passwd.pw_gecos'!])],
                 [#include <pwd.h>])
 @end example

@@ -4581,7 +4581,7 @@
 options to the output variable @code{CC}.  Define
 @code{_FILE_OFFSET_BITS} and @code{_LARGE_FILES} if necessary.

-The user can disable large-file support by configuring with the
+Large-file support can be disabled by configuring with the
 @option{--disable-largefile} option.

 If you use this macro, check that your program works even when
@@ -5223,7 +5223,7 @@

 @example
 $ uname -a
-SunOS shelby.Stanford.EDU 5.7 Generic_106541-10 sun4u sparc SUNW,Ultra-1
+SunOS shelby 5.7 Generic_106541-10 sun4u sparc SUNW,Ultra-1
 $ echo $(echo blah)
 syntax error: `(' unexpected
 @end example
@@ -5320,9 +5320,14 @@
 @end example

 Therefore a portable solution to neutralize @samp{CDPATH} is
address@hidden@address@hidden:}.  Note that since @command{zsh}
-support @command{unset}, you may unset @samp{CDPATH} using @samp{:} as a
-fall back, see @ref{Limitations of Builtins}.
+
address@hidden
address@hidden@}:
address@hidden example
+
+Note that since @command{zsh} supports @command{unset}, you may unset
address@hidden using @samp{:} as a fallback, see
address@hidden of Builtins}.

 @item LANG
 @itemx LC_ALL
@@ -8012,10 +8017,11 @@
 @example
 transform = @@program_transform_name@@
 install: all
-        $(INSTALL_PROGRAM) myprog $(bindir)/`echo myprog|sed '$(transform)'`
+        $(INSTALL_PROGRAM) myprog $(bindir)/`echo myprog | \
+          sed '$(transform)'`

 uninstall:
-        rm -f $(bindir)/`echo myprog|sed '$(transform)'`
+        rm -f $(bindir)/`echo myprog | sed '$(transform)'`
 @end example

 @noindent
@@ -8025,12 +8031,13 @@
 PROGRAMS = cp ls rm
 install:
         for p in $(PROGRAMS); do \
-          $(INSTALL_PROGRAM) $$p $(bindir)/`echo $$p|sed '$(transform)'`; \
+          $(INSTALL_PROGRAM) $$p $(bindir)/`echo $$p | \
+            sed '$(transform)'`; \
         done

 uninstall:
         for p in $(PROGRAMS); do \
-          rm -f $(bindir)/`echo $$p|sed '$(transform)'`; \
+          rm -f $(bindir)/`echo $$p | sed '$(transform)'`; \
         done
 @end example

@@ -8495,10 +8502,10 @@
 canonical system types.  @xref{Canonicalizing}, for details about the
 variables this macro sets.

-The user is encouraged to explicitly use either
address@hidden, or @code{AC_CANONICAL_HOST}, or
address@hidden, depending on her needs.  Using
address@hidden is enough to run the three macros.
+The user is encouraged to use either @code{AC_CANONICAL_BUILD}, or
address@hidden, or @code{AC_CANONICAL_TARGET}, depending on
+the needs.  Using @code{AC_CANONICAL_TARGET} is enough to run the two
+other macros.
 @end defmac

 @defmac AC_CHAR_UNSIGNED
@@ -8795,8 +8802,7 @@
 @defmac AC_LANG_SAVE
 @maindex LANG_SAVE
 Remember the current language (as set by @code{AC_LANG}) on a stack.
-Doe not change which language is current.  @code{AC_LANG_PUSH} is
-preferred.
+The current language does not change.  @code{AC_LANG_PUSH} is preferred.
 @end defmac

 @defmac AC_LINK_FILES (@address@hidden, @address@hidden)
@@ -8826,8 +8832,8 @@
 @defmac AC_LONG_64_BITS
 @maindex LONG_64_BITS
 @cvindex LONG_64_BITS
-If the C type @code{long int} is 16 bits wide, define
address@hidden  Use @samp{AC_CHECK_SIZEOF(long int)} instead.
+Define @code{LONG_64_BITS} if the C type @code{long int} is 64 bits wide.
+Use more generic @samp{AC_CHECK_SIZEOF([long int])} instead.
 @end defmac

 @defmac AC_LONG_DOUBLE
Index: doc/install.texi
--- doc/install.texi    Tue Jul  4 06:34:22 2000
+++ doc/install.texi    Thu Nov 23 17:52:41 2000
@@ -170,9 +170,9 @@
 If @file{config.sub} isn't included in this package, then this package
 doesn't need to know the host type.

-If you are @emph{building} compiler tools for cross-compiling, you can
-also use the @address@hidden option to select the type of
-system they will produce code for.
+If you are @emph{building} compiler tools for cross-compiling, you should
+use the @address@hidden option to select the type of system
+they will produce code for.

 If you want to @emph{use} a cross compiler, that generates code for a
 platform different from the build platform, you should specify the host
_______________________