X-Git-Url: http://git.pld-linux.org/?a=blobdiff_plain;f=autoconf-info.patch;h=4a3749dea266aa0a07b562bb51c41ab782c95aac;hb=14d25fc5602bdfaafc53f339fd0b33cf06cee653;hp=7a265fa61042f5c8607e21538f5c050f23bd5b71;hpb=c6137bbf9fa7470bd27c39773e3832e08ae7adb4;p=packages%2Fautoconf.git diff --git a/autoconf-info.patch b/autoconf-info.patch index 7a265fa..4a3749d 100644 --- a/autoconf-info.patch +++ b/autoconf-info.patch @@ -1,22 +1,21 @@ ---- autoconf-2.57/doc/autoconf.texi.wiget Wed Dec 4 17:25:14 2002 -+++ autoconf-2.57/doc/autoconf.texi Wed Dec 4 17:25:14 2002 -@@ -95,33 +95,19 @@ +--- autoconf-2.62/doc/autoconf.texi.orig 2008-04-16 20:34:45.377155963 +0200 ++++ autoconf-2.62/doc/autoconf.texi 2008-04-16 20:39:04.079896078 +0200 +@@ -203,29 +203,19 @@ --@dircategory GNU programming tools +-@dircategory Software development +@dircategory Programming tools: @direntry --* Autoconf: (autoconf). Create source code configuration scripts +-* Autoconf: (autoconf). Create source code configuration scripts. -@end direntry - -@dircategory Individual utilities -@direntry -* autoscan: (autoconf)autoscan Invocation. - Semi-automatic @file{configure.ac} writing --* ifnames: (autoconf)ifnames Invocation. -- Listing the conditionals in source code --* autoconf: (autoconf)autoconf Invocation. +-* ifnames: (autoconf)ifnames Invocation. Listing conditionals in source. +-* autoconf-invocation: (autoconf)autoconf Invocation. - How to create configuration scripts -* autoreconf: (autoconf)autoreconf Invocation. - Remaking multiple @command{configure} scripts @@ -24,29 +23,26 @@ - How to create configuration templates -* autom4te: (autoconf)autom4te Invocation. - The Autoconf executables backbone --* configure: (autoconf)configure Invocation. -- Configuring a package +-* configure: (autoconf)configure Invocation. Configuring a package. -* autoupdate: (autoconf)autoupdate Invocation. - Automatic update of @file{configure.ac} --* config.status: (autoconf)config.status Invocation. -- Recreating a configuration --* testsuite: (autoconf)testsuite Invocation. -- Running an Autotest test suite +-* config.status: (autoconf)config.status Invocation. Recreating configurations. +-* testsuite: (autoconf)testsuite Invocation. Running an Autotest test suite. +* Autoconf: (autoconf). Create source code configuration scripts +* autoscan: (autoconf)autoscan. Semi-automatic @file{configure.ac} writing -+* ifnames: (autoconf)ifnames. Listing the conditionals in source code ++* ifnames: (autoconf)ifnames. Listing conditionals in source +* autoconf: (autoconf)autoconf. How to create configuration scripts +* autoreconf: (autoconf)autoreconf. Remaking multiple @command{configure} scripts +* autoheader: (autoconf)autoheader. How to create configuration templates +* autom4te: (autoconf)autom4te. The Autoconf executables backbone +* configure: (autoconf)configure. Configuring a package +* autoupdate: (autoconf)autoupdate. Automatic update of @file{configure.ac} -+* config.status: (autoconf)config.status. Recreating a configuration -+* testsuite: (autoconf)testsuite. Running an Autotest test suite ++* config.status: (autoconf)config.status. Recreating configurations. ++* testsuite: (autoconf)testsuite. Running an Autotest test suite. @end direntry @titlepage -@@ -161,7 +147,7 @@ +@@ -267,7 +257,7 @@ * Manual Configuration:: Selecting features that can't be guessed * Site Configuration:: Local defaults for @command{configure} * Running configure Scripts:: How to use the Autoconf output @@ -55,10 +51,10 @@ * Obsolete Constructs:: Kept for backward compatibility * Using Autotest:: Creating portable test suites * FAQ:: Frequent Autoconf Questions, with answers -@@ -181,10 +167,10 @@ +@@ -288,10 +278,10 @@ Making @command{configure} Scripts - * Writing configure.ac:: What to put in an Autoconf input file + * Writing Autoconf Input:: What to put in an Autoconf input file -* autoscan Invocation:: Semi-automatic @file{configure.ac} writing -* ifnames Invocation:: Listing the conditionals in source code -* autoconf Invocation:: How to create configuration scripts @@ -70,7 +66,7 @@ Writing @file{configure.ac} -@@ -217,7 +203,7 @@ +@@ -326,7 +316,7 @@ Configuration Header Files * Header Templates:: Input for the configuration headers @@ -79,7 +75,7 @@ * Autoheader Macros:: How to specify CPP templates Existing Tests -@@ -328,7 +314,7 @@ +@@ -443,7 +433,7 @@ Using @command{autom4te} @@ -88,7 +84,7 @@ * Customizing autom4te:: Customizing the Autoconf package Programming in M4sugar -@@ -395,13 +381,13 @@ +@@ -559,13 +549,13 @@ * System Type:: Specifying the system type * Sharing Defaults:: Setting site-wide defaults for @command{configure} * Defining Variables:: Specifying the compiler etc. @@ -97,35 +93,35 @@ Obsolete Constructs - * Obsolete config.status Use:: Different calling convention - * acconfig.h:: Additional entries in @file{config.h.in} + * Obsolete config.status Use:: Obsolete convention for @command{config.status} + * acconfig Header:: Additional entries in @file{config.h.in} -* autoupdate Invocation:: Automatic update of @file{configure.ac} +* autoupdate:: Automatic update of @file{configure.ac} * Obsolete Macros:: Backward compatibility macros * Autoconf 1:: Tips for upgrading your files * Autoconf 2.13:: Some fresher tips -@@ -426,7 +412,7 @@ +@@ -590,7 +580,7 @@ * Using an Autotest Test Suite:: Autotest and the user - * Writing testsuite.at:: Autotest macros + * Writing Testsuites:: Autotest macros -* testsuite Invocation:: Running @command{testsuite} scripts +* testsuite:: Running @command{testsuite} scripts * Making testsuite Scripts:: Using autom4te to create @command{testsuite} Using an Autotest Test Suite -@@ -740,7 +726,7 @@ +@@ -946,7 +936,7 @@ @item - a shell script called @file{config.status} that, when run, will recreate + a shell script called @file{config.status} that, when run, recreates -the files listed above (@pxref{config.status Invocation}); +the files listed above (@pxref{config.status}); @item an optional shell script normally called @file{config.cache} -@@ -800,10 +786,10 @@ +@@ -1006,10 +996,10 @@ @menu - * Writing configure.ac:: What to put in an Autoconf input file + * Writing Autoconf Input:: What to put in an Autoconf input file -* autoscan Invocation:: Semi-automatic @file{configure.ac} writing -* ifnames Invocation:: Listing the conditionals in source code -* autoconf Invocation:: How to create configuration scripts @@ -136,8 +132,8 @@ +* autoreconf:: Remaking multiple @command{configure} scripts @end menu - @node Writing configure.ac -@@ -819,7 +805,7 @@ + @node Writing Autoconf Input +@@ -1025,7 +1015,7 @@ or specialized features, @file{configure.ac} might need to contain some hand-crafted shell commands; see @ref{Portable Shell}. The @command{autoscan} program can give you a good start in writing @@ -146,7 +142,7 @@ Previous versions of Autoconf promoted the name @file{configure.in}, which is somewhat ambiguous (the tool needed to process this file is not -@@ -1047,7 +1033,7 @@ +@@ -1281,7 +1271,7 @@ @end display @@ -155,7 +151,7 @@ @section Using @command{autoscan} to Create @file{configure.ac} @cindex @command{autoscan} -@@ -1069,7 +1055,7 @@ +@@ -1303,7 +1293,7 @@ use a configuration header file, you must add a call to @code{AC_CONFIG_HEADERS} (@pxref{Configuration Headers}). You might also have to change or add some @code{#if} directives to your program in @@ -164,7 +160,7 @@ information about a program that can help with that job). When using @command{autoscan} to maintain a @file{configure.ac}, simply -@@ -1108,7 +1094,7 @@ +@@ -1342,7 +1332,7 @@ Prepend @var{dir} to the include path. Multiple invocations accumulate. @end table @@ -173,7 +169,7 @@ @section Using @command{ifnames} to List Conditionals @cindex @command{ifnames} -@@ -1117,8 +1103,7 @@ +@@ -1351,8 +1341,7 @@ preprocessor conditionals. If a package has already been set up to have some portability, @command{ifnames} can thus help you figure out what its @command{configure} needs to check for. It may help fill in some gaps in a @@ -183,7 +179,7 @@ @command{ifnames} scans all of the C source files named on the command line (or the standard input, if none are given) and writes to the standard -@@ -1140,7 +1125,7 @@ +@@ -1374,7 +1363,7 @@ Print the version number of Autoconf and exit. @end table @@ -192,7 +188,7 @@ @section Using @command{autoconf} to Create @command{configure} @cindex @command{autoconf} -@@ -1234,8 +1219,7 @@ +@@ -1468,8 +1457,7 @@ @cindex Macro invocation stack Because @command{autoconf} uses @command{autom4te} behind the scenes, it displays a back trace for errors, but not for warnings; if you want @@ -202,7 +198,7 @@ @item --trace=@var{macro}[:@var{format}] @itemx -t @var{macro}[:@var{format}] -@@ -1247,7 +1231,7 @@ +@@ -1481,7 +1469,7 @@ The @var{format} is a regular string, with newlines if desired, and several special escape codes. It defaults to @samp{$f:$l:$n:$%}; see @@ -211,7 +207,7 @@ @item --initialization @itemx -i -@@ -1321,7 +1305,7 @@ +@@ -1555,7 +1543,7 @@ @end group @end example @@ -220,7 +216,18 @@ @section Using @command{autoreconf} to Update @command{configure} Scripts @cindex @command{autoreconf} -@@ -1606,8 +1590,8 @@ +@@ -1592,8 +1580,8 @@ + Gettext supplies the @command{autopoint} command to add translation + infrastructure to a source package. If you use @command{autopoint}, + your @file{configure.ac} should invoke both @code{AM_GNU_GETTEXT} and +-@code{AM_GNU_GETTEXT_VERSION(@var{gettext-version})}. @xref{autopoint +-Invocation, , Invoking the @code{autopoint} Program, gettext, ++@code{AM_GNU_GETTEXT_VERSION(@var{gettext-version})}. ++@xref{autopoint, , Invoking the @code{autopoint} Program, gettext, + @acronym{GNU} @code{gettext} utilities}, for further details. + + @noindent +@@ -1897,8 +1885,8 @@ source directory; @command{configure} checks for this file's existence to make sure that the directory that it is told contains the source code in fact does. Occasionally people accidentally specify the wrong directory @@ -231,7 +238,7 @@ @end defmac -@@ -1774,7 +1758,7 @@ +@@ -2111,7 +2099,7 @@ when used in @var{output}, or the standard input when used in the @var{inputs}. You most probably don't need to use this in @file{configure.ac}, but it is convenient when using the command line @@ -239,17 +246,17 @@ +interface of @file{./config.status}, see @ref{config.status}, for more details. - The @var{inputs} may be absolute or relative filenames. In the latter -@@ -2388,7 +2372,7 @@ - @file{config.h} is considered up to date. @xref{Output}, for more - information about @code{AC_OUTPUT}. + The @var{inputs} may be absolute or relative file names. In the latter +@@ -2971,7 +2959,7 @@ + so @file{config.status} ensures 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 +@xref{config.status}, for more examples of handling configuration-related dependencies. @node Configuration Headers -@@ -2450,7 +2434,7 @@ +@@ -3051,7 +3039,7 @@ @menu * Header Templates:: Input for the configuration headers @@ -258,7 +265,7 @@ * Autoheader Macros:: How to specify CPP templates @end menu -@@ -2504,10 +2488,10 @@ +@@ -3106,10 +3094,10 @@ comments in preprocessor macros has never been a good idea. Since it is a tedious task to keep a template header up to date, you may @@ -271,8 +278,8 @@ @subsection Using @command{autoheader} to Create @file{config.h.in} @cindex @command{autoheader} -@@ -6447,7 +6431,7 @@ - files will depend upon @command{bizarre-cc} being the C compiler. If +@@ -8749,7 +8737,7 @@ + files depend upon @command{bizarre-cc} being the C compiler. If for some reason the user runs @command{./configure} again, or if it is run via @samp{./config.status --recheck}, (@xref{Automatic Remaking}, -and @pxref{config.status Invocation}), then the configuration can be @@ -280,7 +287,7 @@ inconsistent, composed of results depending upon two different compilers. -@@ -6499,7 +6483,7 @@ +@@ -8802,7 +8790,7 @@ @item @var{variable} is kept during automatic reconfiguration @@ -289,8 +296,8 @@ line argument, including when no cache is used: @example -@@ -7370,11 +7354,11 @@ - @command{m4} itself. +@@ -9790,11 +9778,11 @@ + It supports M4 extensions designed for use in tools like Autoconf. @menu -* autom4te Invocation:: A @acronym{GNU} M4 wrapper @@ -303,7 +310,7 @@ @subsection Invoking @command{autom4te} The command line arguments are modeled after M4's: -@@ -7657,7 +7641,7 @@ +@@ -10052,7 +10040,7 @@ not. @end table @@ -312,7 +319,7 @@ @item --preselect=@var{macro} @itemx -p @var{macro} -@@ -7727,8 +7711,8 @@ +@@ -10140,8 +10128,8 @@ wrapped in between a @samp{begin-language: "@var{language}"}, @samp{end-language: "@var{language}"} pair. @@ -323,16 +330,16 @@ more generally arguments, are introduced by @samp{args: @var{arguments}}. You may use the traditional shell syntax to quote the @var{arguments}. -@@ -8141,7 +8125,7 @@ +@@ -11785,7 +11773,7 @@ When the user runs @samp{autoconf -W error}, warnings from - @code{AC_DIAGNOSE} and @code{AC_WARNING} are reported as error, see --@ref{autoconf Invocation}. -+@ref{autoconf}. + @code{m4_warn} (including those issued through @code{AC_DIAGNOSE} and +-@code{AC_WARNING}) are reported as errors, see @ref{autoconf Invocation}. ++@code{AC_WARNING}) are reported as errors, see @ref{autoconf}. @node Dependencies Between Macros @section Dependencies Between Macros -@@ -12054,7 +12038,7 @@ +@@ -17974,16 +17962,16 @@ * System Type:: Specifying the system type * Sharing Defaults:: Setting site-wide defaults for @command{configure} * Defining Variables:: Specifying the compiler etc. @@ -341,25 +348,27 @@ @end menu @set autoconf -@@ -12063,7 +12047,7 @@ + @include install.texi - @c ============================================== Recreating a Configuration + +-@c ============================================== config.status Invocation ++@c ============================================== config.status -@node config.status Invocation +@node config.status - @chapter Recreating a Configuration + @chapter config.status Invocation @cindex @command{config.status} -@@ -12203,7 +12187,7 @@ +@@ -18129,7 +18117,7 @@ @menu - * Obsolete config.status Use:: Different calling convention - * acconfig.h:: Additional entries in @file{config.h.in} + * Obsolete config.status Use:: Obsolete convention for @command{config.status} + * acconfig Header:: Additional entries in @file{config.h.in} -* autoupdate Invocation:: Automatic update of @file{configure.ac} +* autoupdate:: Automatic update of @file{configure.ac} * Obsolete Macros:: Backward compatibility macros * Autoconf 1:: Tips for upgrading your files * Autoconf 2.13:: Some fresher tips -@@ -12213,7 +12197,7 @@ +@@ -18139,7 +18127,7 @@ @section Obsolete @file{config.status} Invocation @file{config.status} now supports arguments to specify the files to @@ -368,7 +377,7 @@ Before, environment variables had to be used. @defvar CONFIG_COMMANDS -@@ -12244,7 +12228,7 @@ +@@ -18170,7 +18158,7 @@ @file{config.status} ignores this variable. @end defvar @@ -377,7 +386,7 @@ would be: @example -@@ -12318,7 +12302,7 @@ +@@ -18244,7 +18232,7 @@ self-contained, and should not depend upon @file{acconfig.h} etc. @@ -386,7 +395,7 @@ @section Using @command{autoupdate} to Modernize @file{configure.ac} @cindex @command{autoupdate} -@@ -13243,7 +13227,7 @@ +@@ -19389,7 +19377,7 @@ If you have an @file{aclocal.m4} installed with Autoconf (as opposed to in a particular package's source directory), you must rename it to @@ -394,8 +403,8 @@ +@file{acsite.m4}. @xref{autoconf}. If you distribute @file{install.sh} with your package, rename it to - @file{install-sh} so @code{make} builtin rules won't inadvertently -@@ -13298,7 +13282,7 @@ + @file{install-sh} so @code{make} builtin rules don't inadvertently +@@ -19444,7 +19432,7 @@ the documentation for them. @xref{Obsolete Macros}, for a table showing the new names for the old macros. Use the @command{autoupdate} program to convert your @file{configure.ac} to using the new macro names. @@ -404,16 +413,25 @@ Some macros have been superseded by similar ones that do the job better, but are not call-compatible. If you get warnings about calling obsolete -@@ -13863,7 +13847,7 @@ +@@ -19980,7 +19968,7 @@ @menu * Using an Autotest Test Suite:: Autotest and the user - * Writing testsuite.at:: Autotest macros + * Writing Testsuites:: Autotest macros -* testsuite Invocation:: Running @command{testsuite} scripts +* testsuite:: Running @command{testsuite} scripts * Making testsuite Scripts:: Using autom4te to create @command{testsuite} @end menu -@@ -14125,7 +14109,7 @@ +@@ -20042,7 +20030,7 @@ + + @itemize @bullet + @item a debugging script named @file{run} which reruns the test in +-@dfn{debug mode} (@pxref{testsuite Invocation}). The automatic generation ++@dfn{debug mode} (@pxref{testsuite}). The automatic generation + of debugging scripts has the purpose of easing the chase for bugs. + + @item all the files created with @code{AT_DATA} +@@ -20304,7 +20292,7 @@ @end defmac @@ -422,7 +440,7 @@ @section Running @command{testsuite} Scripts @cindex @command{testsuite} -@@ -14267,7 +14251,7 @@ +@@ -20471,7 +20459,7 @@ An Autotest test suite is to be configured in @var{directory}. This macro requires the instantiation of @file{@var{directory}/atconfig} from @file{@var{directory}/atconfig.in}, and sets the default @@ -431,34 +449,37 @@ @end defmac @item -@@ -14596,7 +14580,7 @@ - which can be a very long process for complex @file{configure.ac}. +@@ -20825,7 +20813,7 @@ + which can be a long process for complex @file{configure.ac}. This is why all these tools, instead of running directly M4, invoke -@command{autom4te} (@pxref{autom4te Invocation}) which, while answering to +@command{autom4te} (@pxref{autom4te}) which, while answering to a specific demand, stores additional information in @file{autom4te.cache} for future runs. For instance, if you run - @command{autoconf}, behind the scenes, @command{autom4te} will also ---- autoconf-2.57/doc/install.texi.wiget Mon Jul 29 10:20:52 2002 -+++ autoconf-2.57/doc/install.texi Wed Dec 4 17:25:14 2002 -@@ -225,7 +225,7 @@ - overridden in the site shell script). - + @command{autoconf}, behind the scenes, @command{autom4te} also +--- autoconf-2.62/doc/install.texi.orig 2007-12-08 14:58:52.000000000 +0100 ++++ autoconf-2.62/doc/install.texi 2008-04-16 20:34:45.697178391 +0200 +@@ -239,7 +239,7 @@ + CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash + @end example -@node configure Invocation +@node configure @section @command{configure} Invocation @command{configure} recognizes the following options to control how it ---- autoconf-2.57/doc/standards.texi.wiget Sat Nov 23 06:08:33 2002 -+++ autoconf-2.57/doc/standards.texi Wed Dec 4 17:26:51 2002 -@@ -6,7 +6,7 @@ - @set lastupdate November 23, 2002 +--- autoconf-2.62/doc/standards.texi.orig 2008-04-04 15:16:45.000000000 +0200 ++++ autoconf-2.62/doc/standards.texi 2008-04-16 20:39:27.317224488 +0200 +@@ -6,9 +6,9 @@ + @set lastupdate February 23, 2008 @c %**end of header -@dircategory GNU organization +@dircategory Miscellaneous: @direntry - * Standards: (standards). GNU coding standards. +-* Standards: (standards). GNU coding standards. ++* Standards: (standards). GNU coding standards @end direntry + + @c @setchapternewpage odd