From: Jakub Bogusz Date: Wed, 10 Sep 2008 15:59:52 +0000 (+0000) Subject: - updated for 2.63 X-Git-Tag: auto/th/autoconf-2_63-1~1 X-Git-Url: http://git.pld-linux.org/?p=packages%2Fautoconf.git;a=commitdiff_plain;h=421bed4444f37fe353637ab1a44464a9759128a0 - updated for 2.63 Changed files: autoconf-info.patch -> 1.18 --- diff --git a/autoconf-info.patch b/autoconf-info.patch index 4a3749d..c1c484a 100644 --- a/autoconf-info.patch +++ b/autoconf-info.patch @@ -1,5 +1,5 @@ ---- 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 +--- autoconf-2.63/doc/autoconf.texi.orig 2008-09-10 17:43:06.324991499 +0200 ++++ autoconf-2.63/doc/autoconf.texi 2008-09-10 17:43:06.468990661 +0200 @@ -203,29 +203,19 @@ @@ -84,7 +84,7 @@ * Customizing autom4te:: Customizing the Autoconf package Programming in M4sugar -@@ -559,13 +549,13 @@ +@@ -561,13 +551,13 @@ * System Type:: Specifying the system type * Sharing Defaults:: Setting site-wide defaults for @command{configure} * Defining Variables:: Specifying the compiler etc. @@ -100,7 +100,7 @@ * Obsolete Macros:: Backward compatibility macros * Autoconf 1:: Tips for upgrading your files * Autoconf 2.13:: Some fresher tips -@@ -590,7 +580,7 @@ +@@ -592,7 +582,7 @@ * Using an Autotest Test Suite:: Autotest and the user * Writing Testsuites:: Autotest macros @@ -109,7 +109,7 @@ * Making testsuite Scripts:: Using autom4te to create @command{testsuite} Using an Autotest Test Suite -@@ -946,7 +936,7 @@ +@@ -948,7 +938,7 @@ @item a shell script called @file{config.status} that, when run, recreates @@ -118,7 +118,7 @@ @item an optional shell script normally called @file{config.cache} -@@ -1006,10 +996,10 @@ +@@ -1008,10 +998,10 @@ @menu * Writing Autoconf Input:: What to put in an Autoconf input file @@ -133,7 +133,7 @@ @end menu @node Writing Autoconf Input -@@ -1025,7 +1015,7 @@ +@@ -1027,7 +1017,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 @@ -142,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 -@@ -1281,7 +1271,7 @@ +@@ -1283,7 +1273,7 @@ @end display @@ -151,7 +151,7 @@ @section Using @command{autoscan} to Create @file{configure.ac} @cindex @command{autoscan} -@@ -1303,7 +1293,7 @@ +@@ -1305,7 +1295,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 @@ -160,7 +160,7 @@ information about a program that can help with that job). When using @command{autoscan} to maintain a @file{configure.ac}, simply -@@ -1342,7 +1332,7 @@ +@@ -1348,7 +1338,7 @@ Prepend @var{dir} to the include path. Multiple invocations accumulate. @end table @@ -169,7 +169,7 @@ @section Using @command{ifnames} to List Conditionals @cindex @command{ifnames} -@@ -1351,8 +1341,7 @@ +@@ -1357,8 +1347,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 @@ -179,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 -@@ -1374,7 +1363,7 @@ +@@ -1380,7 +1369,7 @@ Print the version number of Autoconf and exit. @end table @@ -188,7 +188,7 @@ @section Using @command{autoconf} to Create @command{configure} @cindex @command{autoconf} -@@ -1468,8 +1457,7 @@ +@@ -1474,8 +1463,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 @@ -198,7 +198,7 @@ @item --trace=@var{macro}[:@var{format}] @itemx -t @var{macro}[:@var{format}] -@@ -1481,7 +1469,7 @@ +@@ -1487,7 +1475,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 @@ -207,7 +207,7 @@ @item --initialization @itemx -i -@@ -1555,7 +1543,7 @@ +@@ -1561,7 +1549,7 @@ @end group @end example @@ -216,7 +216,7 @@ @section Using @command{autoreconf} to Update @command{configure} Scripts @cindex @command{autoreconf} -@@ -1592,8 +1580,8 @@ +@@ -1598,8 +1586,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 @@ -227,7 +227,7 @@ @acronym{GNU} @code{gettext} utilities}, for further details. @noindent -@@ -1897,8 +1885,8 @@ +@@ -1914,8 +1902,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 @@ -238,7 +238,7 @@ @end defmac -@@ -2111,7 +2099,7 @@ +@@ -2128,7 +2116,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 @@ -247,7 +247,7 @@ for more details. The @var{inputs} may be absolute or relative file names. In the latter -@@ -2971,7 +2959,7 @@ +@@ -2991,7 +2979,7 @@ so @file{config.status} ensures that @file{config.h} is considered up to date. @xref{Output}, for more information about @code{AC_OUTPUT}. @@ -256,7 +256,7 @@ configuration-related dependencies. @node Configuration Headers -@@ -3051,7 +3039,7 @@ +@@ -3071,7 +3059,7 @@ @menu * Header Templates:: Input for the configuration headers @@ -265,20 +265,34 @@ * Autoheader Macros:: How to specify CPP templates @end menu -@@ -3106,10 +3094,10 @@ - comments in preprocessor macros has never been a good idea. +@@ -3113,7 +3101,7 @@ + generated header. Since it is a tedious task to keep a template header up to date, you may -use @command{autoheader} to generate it, see @ref{autoheader Invocation}. +use @command{autoheader} to generate it, see @ref{autoheader}. + During the instantiation of the header, each @samp{#undef} line in the + template file for each symbol defined by @samp{AC_DEFINE} is changed to an +@@ -3151,7 +3139,7 @@ + probably use @samp{AH_BOTTOM} to append the @samp{#include} directive. + -@node autoheader Invocation +@node autoheader @subsection Using @command{autoheader} to Create @file{config.h.in} @cindex @command{autoheader} -@@ -8749,7 +8737,7 @@ +@@ -6801,7 +6789,7 @@ + And finally, the default for @var{action-if-universal} is to ensure that + @samp{WORDS_BIGENDIAN} is defined if and only if a universal build is + detected and the current code is big-endian; this default works only if +-@command{autoheader} is used (@pxref{autoheader Invocation}). ++@command{autoheader} is used (@pxref{autoheader}). + + If you use this macro without specifying @var{action-if-universal}, you + should also use @code{AC_CONFIG_HEADERS}; otherwise +@@ -8794,7 +8782,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}, @@ -287,7 +301,7 @@ inconsistent, composed of results depending upon two different compilers. -@@ -8802,7 +8790,7 @@ +@@ -8847,7 +8835,7 @@ @item @var{variable} is kept during automatic reconfiguration @@ -296,7 +310,7 @@ line argument, including when no cache is used: @example -@@ -9790,11 +9778,11 @@ +@@ -9856,11 +9844,11 @@ It supports M4 extensions designed for use in tools like Autoconf. @menu @@ -310,7 +324,7 @@ @subsection Invoking @command{autom4te} The command line arguments are modeled after M4's: -@@ -10052,7 +10040,7 @@ +@@ -10118,7 +10106,7 @@ not. @end table @@ -319,7 +333,7 @@ @item --preselect=@var{macro} @itemx -p @var{macro} -@@ -10140,8 +10128,8 @@ +@@ -10206,8 +10194,8 @@ wrapped in between a @samp{begin-language: "@var{language}"}, @samp{end-language: "@var{language}"} pair. @@ -330,7 +344,7 @@ more generally arguments, are introduced by @samp{args: @var{arguments}}. You may use the traditional shell syntax to quote the @var{arguments}. -@@ -11785,7 +11773,7 @@ +@@ -12175,7 +12163,7 @@ When the user runs @samp{autoconf -W error}, warnings from @code{m4_warn} (including those issued through @code{AC_DIAGNOSE} and @@ -339,7 +353,7 @@ @node Dependencies Between Macros @section Dependencies Between Macros -@@ -17974,16 +17962,16 @@ +@@ -18580,16 +18568,16 @@ * System Type:: Specifying the system type * Sharing Defaults:: Setting site-wide defaults for @command{configure} * Defining Variables:: Specifying the compiler etc. @@ -359,7 +373,7 @@ @chapter config.status Invocation @cindex @command{config.status} -@@ -18129,7 +18117,7 @@ +@@ -18735,7 +18723,7 @@ @menu * Obsolete config.status Use:: Obsolete convention for @command{config.status} * acconfig Header:: Additional entries in @file{config.h.in} @@ -368,7 +382,7 @@ * Obsolete Macros:: Backward compatibility macros * Autoconf 1:: Tips for upgrading your files * Autoconf 2.13:: Some fresher tips -@@ -18139,7 +18127,7 @@ +@@ -18745,7 +18733,7 @@ @section Obsolete @file{config.status} Invocation @file{config.status} now supports arguments to specify the files to @@ -377,7 +391,7 @@ Before, environment variables had to be used. @defvar CONFIG_COMMANDS -@@ -18170,7 +18158,7 @@ +@@ -18776,7 +18764,7 @@ @file{config.status} ignores this variable. @end defvar @@ -386,7 +400,7 @@ would be: @example -@@ -18244,7 +18232,7 @@ +@@ -18850,7 +18838,7 @@ self-contained, and should not depend upon @file{acconfig.h} etc. @@ -395,7 +409,7 @@ @section Using @command{autoupdate} to Modernize @file{configure.ac} @cindex @command{autoupdate} -@@ -19389,7 +19377,7 @@ +@@ -20028,7 +20016,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 @@ -403,8 +417,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 don't inadvertently -@@ -19444,7 +19432,7 @@ + @file{install-sh} so @command{make} builtin rules don't inadvertently +@@ -20083,7 +20071,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. @@ -413,7 +427,7 @@ 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 -@@ -19980,7 +19968,7 @@ +@@ -20619,7 +20607,7 @@ @menu * Using an Autotest Test Suite:: Autotest and the user * Writing Testsuites:: Autotest macros @@ -422,7 +436,7 @@ * Making testsuite Scripts:: Using autom4te to create @command{testsuite} @end menu -@@ -20042,7 +20030,7 @@ +@@ -20681,7 +20669,7 @@ @itemize @bullet @item a debugging script named @file{run} which reruns the test in @@ -431,7 +445,7 @@ 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 @@ +@@ -20943,7 +20931,7 @@ @end defmac @@ -440,7 +454,7 @@ @section Running @command{testsuite} Scripts @cindex @command{testsuite} -@@ -20471,7 +20459,7 @@ +@@ -21115,7 +21103,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 @@ -449,7 +463,7 @@ @end defmac @item -@@ -20825,7 +20813,7 @@ +@@ -21469,7 +21457,7 @@ which can be a long process for complex @file{configure.ac}. This is why all these tools, instead of running directly M4, invoke