* doc/autoconf.texi (all over the map): Reword a few sentences to fix many underflow and overflow warnings during `make dvi'. Index: doc/autoconf.texi =================================================================== RCS file: /cvsroot/autoconf/autoconf/doc/autoconf.texi,v retrieving revision 1.897 diff -u -r1.897 autoconf.texi --- doc/autoconf.texi 10 May 2005 23:37:37 -0000 1.897 +++ doc/autoconf.texi 15 May 2005 03:10:14 -0000 @@ -656,25 +656,25 @@ Mail suggestions to @email{autoconf@@gnu.org, the Autoconf mailing list}. -Bug reports should be emailed to @email{bug-autoconf@@gnu.org, the +Bug reports should be sent to @email{bug-autoconf@@gnu.org, the Autoconf Bugs mailing list}. If possible, first check that your bug is not already solved in current development versions, and that it has not been reported yet. Be sure to include all the needed information and a short @file{configure.ac} that demonstrates the problem. -Autoconf's development tree is accessible via @acronym{CVS}; see the address@hidden://savannah.gnu.org/projects/autoconf/, Autoconf +Autoconf's development tree is accessible via anonymous @acronym{CVS}; +see the @uref{http://savannah.gnu.org/projects/autoconf/, Autoconf Summary} for details. Patches relative to the current @acronym{CVS} version can be sent for review to the @email{autoconf-patches@@gnu.org, Autoconf Patches mailing list}. Archives of @email{bug-autoconf@@gnu.org} can be -found in @uref{http://lists.gnu.org/archive/html/bug-autoconf/}, and +found in @uref{http://lists.gnu.org/archive/@/html/bug-autoconf/}, and similarly for the other mailing lists. -Because of its mission, Autoconf includes only a set of often-used -macros that have already demonstrated their usefulness. Nevertheless, -if you wish to share your macros, or find existing ones, see the +Because of its mission, the Autoconf package itself includes only a set of +often-used macros that have already demonstrated their usefulness. +Nevertheless, if you wish to share your macros, or find existing ones, see the @uref{http://www.gnu.org/software/ac-archive/, @acronym{GNU} Autoconf Macro Archive}, which is kindly run by @email{simons@@cryp.to, Peter Simons}. @@ -792,7 +792,7 @@ The home pages for @uref{http://www.gnu.org/software/autoconf/, Autoconf}, @uref{http://www.gnu.org/software/automake/, Automake}, and address@hidden://www.gnu.org/software/libtool/, Libtool}. address@hidden://@/www.gnu.org/@/software/libtool/, Libtool}. @item Automake Manual @@ -806,7 +806,7 @@ by G. V. Vaughan, B. Elliston, T. Tromey, and I. L. Taylor. SAMS (originally New Riders), 2000, ISBN 1578701902.} describes the complete @acronym{GNU} build environment. You can also find address@hidden://sources.redhat.com/autobook/, the entire book on-line}. address@hidden://@/sources.redhat.com/autobook/, the entire book on-line}. @end itemize @@ -1342,8 +1342,8 @@ @end table Warnings about @samp{syntax} are enabled by default, and the environment -variable @env{WARNINGS}, a comma separated list of categories, is -honored. Passing @samp{-W @var{category}} will actually behave as if +variable @env{WARNINGS}, a comma separated list of categories, is honored +as well. Passing @samp{-W @var{category}} will actually behave as if you had passed @samp{--warnings=syntax,$WARNINGS,@var{category}}. If you want to disable the defaults and @env{WARNINGS}, but (for example) enable the warnings about obsolete constructs, you would use @option{-W @@ -1509,8 +1509,8 @@ Install the missing auxiliary files in the package. By default, files are copied; this can be changed with @option{--symlink}. -This option triggers calls to @samp{automake --add-missing}, address@hidden, @samp{autopoint}, etc. +If deemed appropriate, this option triggers calls to address@hidden --add-missing}, @samp{libtoolize}, @samp{autopoint}, etc. @item --symlink @itemx -s @@ -1564,8 +1564,8 @@ @end table Warnings about @samp{syntax} are enabled by default, and the environment -variable @env{WARNINGS}, a comma separated list of categories, is -honored. Passing @samp{-W @var{category}} will actually behave as if +variable @env{WARNINGS}, a comma separated list of categories, is honored +as well. Passing @samp{-W @var{category}} will actually behave as if you had passed @samp{--warnings=syntax,$WARNINGS,@var{category}}. If you want to disable the defaults and @env{WARNINGS}, but (for example) enable the warnings about obsolete constructs, you would use @option{-W @@ -2618,10 +2618,15 @@ (Be careful if you copy these lines directly into your Makefile, as you will need to convert the indented lines to start with the tab character.) -In addition, you should use @samp{AC_CONFIG_FILES([stamp-h], [echo -timestamp > stamp-h])} so @file{config.status} will ensure that address@hidden is considered up to date. @xref{Output}, for more -information about @code{AC_OUTPUT}. +In addition, you should use + address@hidden +AC_CONFIG_FILES([stamp-h], [echo timestamp > stamp-h]) address@hidden example + address@hidden +so @file{config.status} will ensure that @file{config.h} is considered up to +date. @xref{Output}, for more information about @code{AC_OUTPUT}. @xref{config.status Invocation}, for more examples of handling configuration-related dependencies. @@ -4167,7 +4172,7 @@ If the system has the @code{getloadavg} function, define @code{HAVE_GETLOADAVG}, and set @code{GETLOADAVG_LIBS} to any libraries -needed to get that function. Also add @code{GETLOADAVG_LIBS} to +necessary to get that function. Also add @code{GETLOADAVG_LIBS} to @code{LIBS}. Otherwise, require an @code{AC_LIBOBJ} replacement for @samp{getloadavg} with source code in @address@hidden/getloadavg.c}, and possibly define several other C preprocessor macros and output @@ -4536,8 +4541,8 @@ @defmac AC_CHECK_FUNCS (@address@hidden, @ovar{action-if-found}, @ovar{action-if-not-found}) @acindex{CHECK_FUNCS} @cvindex address@hidden -For each @var{function} in the blank-or-newline-separated argument list, -define @address@hidden (in all capitals) if it is available. +For each @var{function} enumerated in the blank-or-newline-separated argument +list, define @address@hidden (in all capitals) if it is available. If @var{action-if-found} is given, it is additional shell code to execute when one of the functions is found. You can give it a value of @samp{break} to break out of the loop on the first match. If @@ -5620,8 +5625,10 @@ yields @example address@hidden: "foo.c", line 13: error 4048: Non-terminating comment at end of file. address@hidden: "foo.c", line 13: error 4033: Missing #endif at end of file. address@hidden: "foo.c", line 13: error 4048: \ +Non-terminating comment at end of file. address@hidden: "foo.c", line 13: error 4033: \ +Missing #endif at end of file. @end example @noindent @@ -6416,7 +6423,7 @@ @cindex Large file support @cindex LFS Arrange for address@hidden://www.unix-systems.org/version2/whatsnew/lfs20mar.html, address@hidden://www.unix-systems.org/version2/@/whatsnew/@/lfs20mar.html, large-file support}. On some hosts, one must use special compiler options to build programs that can access large files. Append any such options to the output variable @code{CC}. Define @@ -7124,8 +7131,8 @@ @item Tru64 @cindex Tru64 -The @uref{http://h30097.www3.hp.com/docs/, -documentation of several versions of Tru64} is available in different address@hidden://h30097.www3.hp.com/@/docs/, +Documentation of several versions of Tru64} is available in different formats. @item Unix version 7 @@ -7581,7 +7588,7 @@ are invalid for some reason, the user may delete or edit it. By default, @command{configure} uses no cache file (technically, it uses address@hidden/dev/null}), to avoid problems caused by accidental address@hidden/dev/@/null}), to avoid problems caused by accidental use of stale cache files. To enable caching, @command{configure} accepts @option{--config-cache} (or @@ -8407,9 +8414,9 @@ @end example @noindent -If you want to disable @command{autom4te}'s defaults and address@hidden, but (for example) enable the warnings about obsolete -constructs, you would use @option{-W none,obsolete}. +For example, if you want to disable @command{autom4te}'s defaults and address@hidden, but enable the warnings about obsolete constructs, +you would use @option{-W none,obsolete}. @cindex Back trace @cindex Macro invocation stack @@ -8433,11 +8440,11 @@ @example $ @kbd{autom4te -l autoconf -Wcross} -configure.ac:8: warning: AC_RUN_IFELSE called without default \ -to allow cross compiling +configure.ac:8: warning: AC_RUN_IFELSE called without \ +default to allow cross compiling $ @kbd{autom4te -l autoconf -Wcross,error -f} -configure.ac:8: error: AC_RUN_IFELSE called without default \ -to allow cross compiling +configure.ac:8: error: AC_RUN_IFELSE called without \ +default to allow cross compiling acgeneral.m4:3044: AC_RUN_IFELSE is expanded from... configure.ac:2: INNER is expanded from... configure.ac:5: OUTER is expanded from... @@ -8648,10 +8656,10 @@ @cindex @file{autom4te.cfg} As an example, if Autoconf is installed in its default location, address@hidden/usr/local}, running @samp{autom4te -l m4sugar foo.m4} is -strictly equivalent to running @samp{autom4te --prepend-include address@hidden/usr/local}, the command @samp{autom4te -l m4sugar foo.m4} is +strictly equivalent to the command @samp{autom4te --prepend-include /usr/local/share/autoconf m4sugar/m4sugar.m4f --warnings syntax foo.m4}. -Recursive expansion applies: running @samp{autom4te -l m4sh foo.m4} +Recursive expansion applies here: the command @samp{autom4te -l m4sh foo.m4} is the same as @samp{autom4te --language M4sugar m4sugar/m4sh.m4f foo.m4}, i.e., @samp{autom4te --prepend-include /usr/local/share/autoconf m4sugar/m4sugar.m4f m4sugar/m4sh.m4f --mode 777 foo.m4}. The definition @@ -9655,7 +9663,7 @@ There are several families of shells, most prominently the Bourne family and the C shell family which are deeply incompatible. If you want to write portable shell scripts, avoid members of the C shell family. The address@hidden://www.faqs.org/faqs/unix-faq/shell/shell-differences/, the address@hidden://www.faqs.org/@/faqs/unix-faq/shell/shell-differences/, the Shell difference FAQ} includes a small history of Posix shells, and a comparison between several of them. @@ -9731,10 +9739,10 @@ @prindex @command{/usr/bin/ksh} on Solaris @command{/usr/bin/ksh} is @samp{ksh88}, @prindex @command{/usr/xpg4/bin/sh} on Solaris address@hidden/usr/xpg4/bin/sh} is a Posix-compliant variant of address@hidden/usr/xpg4/@/bin/sh} is a Posix-compliant variant of @samp{ksh88}, and @prindex @command{/usr/dt/bin/dtksh} on Solaris address@hidden/usr/dt/bin/dtksh} is @samp{ksh93}. @command{/usr/bin/ksh} address@hidden/usr/dt/@/bin/dtksh} is @samp{ksh93}. @command{/usr/bin/ksh} is standard on Solaris; the other variants are parts of optional packages. There is no extra charge for these packages, but they are not part of a minimal OS install and therefore some installations may @@ -10829,7 +10829,8 @@ such code, e.g.: @example -cmp file1 file2 >/dev/null 2>&1 || echo files differ or trouble +cmp file1 file2 >/dev/null 2>&1 || + echo files differ or trouble @end example More generally, one can always rewrite @samp{! @var{command}} as: @@ -11987,7 +11997,8 @@ @example $ @kbd{touch /tmp/foo} $ @kbd{mv /tmp/foo .} address@hidden: ./foo: set owner/group (was: 3830/0): Operation not permitted address@hidden: ./foo: set owner/group (was: 3830/0): \ +Operation not permitted $ @kbd{echo $?} 0 $ @kbd{ls foo} @@ -12367,7 +12378,7 @@ address@hidden as expected. This syntax (@code{foo=bar make -e}) is portable only when used -outside a @file{Makefile}, for instance from a script or from the +outside of a @file{Makefile}, for instance from a script or from the command line. When run inside a @command{make} rule, GNU @command{make} 3.80 and prior versions forget to propagate the @code{-e} option to address@hidden @@ -13347,20 +13348,22 @@ @c FIXME: Remove AS_IF when the problem of AC_REQUIRE within `if' is solved. @example -AC_ARG_WITH(readline, - [AS_HELP_STRING(--with-readline, +AC_ARG_WITH([readline], + [AS_HELP_STRING([--with-readline], [support fancy command line editing @@<:@@default=check@@:>@@])], [], - with_readline=check) + [with_readline=check]) LIBREADLINE= AS_IF([test "x$with_readline" != xno], - [AC_CHECK_LIB(readline, main, - [AC_SUBST(LIBREADLINE, "-lreadline -lncurses") - AC_DEFINE(HAVE_LIBREADLINE, 1, [Define if you have libreadline]) + [AC_CHECK_LIB([readline], [main], + [AC_SUBST([LIBREADLINE], ["-lreadline -lncurses"]) + AC_DEFINE([HAVE_LIBREADLINE], [1], + [Define if you have libreadline]) ], [if test "x$with_readline" != xcheck; then - AC_MSG_FAILURE([--with-readline was given, but test for readline failed]) + AC_MSG_FAILURE( + [--with-readline was given, but test for readline failed]) fi ], -lncurses)]) @end example @@ -13371,20 +13374,22 @@ @c FIXME: Remove AS_IF when the problem of AC_REQUIRE within `if' is solved. @example -AC_ARG_WITH(readline, - [AS_HELP_STRING(--with-readline, +AC_ARG_WITH([readline], + [AS_HELP_STRING([--with-readline], [enable experimental support for readline])], [], - with_readline=no) + [with_readline=no]) LIBREADLINE= AS_IF([test "x$with_readline" != xno], - [AC_CHECK_LIB(readline, main, - [AC_SUBST(LIBREADLINE, "-lreadline -lncurses") - AC_DEFINE(HAVE_LIBREADLINE, 1, [Define if you have libreadline]) + [AC_CHECK_LIB([readline], [main], + [AC_SUBST([LIBREADLINE], ["-lreadline -lncurses"]) + AC_DEFINE([HAVE_LIBREADLINE], [1], + [Define if you have libreadline]) ], - [AC_MSG_FAILURE([--with-readline was given, but test for readline failed])], - -lncurses)]) + [AC_MSG_FAILURE( + [--with-readline was given, but test for readline failed])], + [-lncurses])]) @end example The last example shows how to use @code{AC_ARG_WITH} to give the user the @@ -13393,20 +13398,22 @@ @c FIXME: Remove AS_IF when the problem of AC_REQUIRE within `if' is solved. @example -AC_ARG_WITH(readline, - [AS_HELP_STRING(--without-readline, +AC_ARG_WITH([readline], + [AS_HELP_STRING([--without-readline], [disable support for readline])], [], - with_readline=yes) + [with_readline=yes]) LIBREADLINE= AS_IF([test "x$with_readline" != xno], - [AC_CHECK_LIB(readline, main, - [AC_SUBST(LIBREADLINE, "-lreadline -lncurses") - AC_DEFINE(HAVE_LIBREADLINE, 1, [Define if you have libreadline]) + [AC_CHECK_LIB([readline], [main], + [AC_SUBST([LIBREADLINE], ["-lreadline -lncurses"]) + AC_DEFINE([HAVE_LIBREADLINE], [1], + [Define if you have libreadline]) ], - [AC_MSG_FAILURE([test for readline failed, use --without-readline if you want to force readline support off])], - -lncurses)]) + [AC_MSG_FAILURE( +[readline test failed (--without-readline forces disabling)])], + [-lncurses])]) @end example These three examples can be easily adapted to the case where @@ -16096,7 +16115,8 @@ $(SHELL) $(TESTSUITE) $(TESTSUITEFLAGS) installcheck-local: atconfig atlocal $(TESTSUITE) - $(SHELL) $(TESTSUITE) AUTOTEST_PATH="$(bindir)" $(TESTSUITEFLAGS) + $(SHELL) $(TESTSUITE) AUTOTEST_PATH="$(bindir)" \ + $(TESTSUITEFLAGS) AUTOTEST = $(AUTOM4TE) --language=autotest $(TESTSUITE): $(srcdir)/testsuite.at @@ -16331,8 +16351,8 @@ @example AC_DEFINE_UNQUOTED([DATADIR], [$datadir], - [Define to the read-only architecture-independent - data directory.]) + [Define to the read-only + architecture-independent data directory.]) @end example @noindent @@ -16374,7 +16394,7 @@ Use @code{AC_DEFINE} but have @command{configure} compute the literal value of @code{datadir} and others. Many people have wrapped macros to automate this task. For instance, the macro @code{AC_DEFINE_DIR} from -the @uref{http://www.gnu.org/software/ac-archive/, @acronym{GNU} Autoconf Macro +the @uref{http://www.gnu.org/@/software/ac-archive/, @acronym{GNU} Autoconf Macro Archive}. This solution does not conform to the @acronym{GNU} Coding Standards. Index: doc/install.texi =================================================================== RCS file: /cvsroot/autoconf/autoconf/doc/install.texi,v retrieving revision 1.42 diff -u -r1.42 install.texi --- doc/install.texi 1 Feb 2005 00:32:44 -0000 1.42 +++ doc/install.texi 15 May 2005 03:10:14 -0000 @@ -121,13 +121,13 @@ @section Installation Names By default, @samp{make install} will install the package's files in address@hidden/usr/local/bin}, @file{/usr/local/man}, etc. You can specify an address@hidden/usr/local/bin}, @file{/usr/@/local/@/man}, etc. You can specify an installation prefix other than @file{/usr/local} by giving @command{configure} the option @address@hidden You can specify separate installation prefixes for architecture-specific -files and architecture-independent files. If you give address@hidden the option @address@hidden, the +files and architecture-independent files. If you pass the option address@hidden@var{prefix}} to @command{configure}, the package will use @var{prefix} as the prefix for installing programs and libraries. Documentation and other data files will still use the regular prefix. @@ -187,7 +187,7 @@ doesn't need to know the machine type. If you are @emph{building} compiler tools for cross-compiling, you -should use the @address@hidden option to select the type of +should use the option @address@hidden 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