- updated info patch
Changed files:
autoconf-info.patch -> 1.20
autoconf.spec -> 1.148
---- 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 @@
+--- autoconf-2.66/doc/autoconf.texi.orig 2010-07-06 19:37:13.069390901 +0200
++++ autoconf-2.66/doc/autoconf.texi 2010-07-07 09:32:22.977390901 +0200
+@@ -220,29 +220,19 @@
* 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
* 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
* Obsolete Constructs:: Kept for backward compatibility
* Using Autotest:: Creating portable test suites
* FAQ:: Frequent Autoconf Questions, with answers
* Obsolete Constructs:: Kept for backward compatibility
* Using Autotest:: Creating portable test suites
* FAQ:: Frequent Autoconf Questions, with answers
Making @command{configure} Scripts
* Writing Autoconf Input:: What to put in an Autoconf input file
Making @command{configure} Scripts
* Writing Autoconf Input:: What to put in an Autoconf input file
Writing @file{configure.ac}
Writing @file{configure.ac}
Configuration Header Files
* Header Templates:: Input for the configuration headers
Configuration Header Files
* Header Templates:: Input for the configuration headers
* Autoheader Macros:: How to specify CPP templates
Existing Tests
* Autoheader Macros:: How to specify CPP templates
Existing Tests
--* autom4te Invocation:: A @acronym{GNU} M4 wrapper
-+* autom4te:: A @acronym{GNU} M4 wrapper
+-* autom4te Invocation:: A GNU M4 wrapper
++* autom4te:: A GNU M4 wrapper
* Customizing autom4te:: Customizing the Autoconf package
Programming in M4sugar
* Customizing autom4te:: Customizing the Autoconf package
Programming in M4sugar
* System Type:: Specifying the system type
* Sharing Defaults:: Setting site-wide defaults for @command{configure}
* Defining Variables:: Specifying the compiler etc.
* System Type:: Specifying the system type
* Sharing Defaults:: Setting site-wide defaults for @command{configure}
* Defining Variables:: Specifying the compiler etc.
* Obsolete Macros:: Backward compatibility macros
* Autoconf 1:: Tips for upgrading your files
* Autoconf 2.13:: Some fresher tips
* Obsolete Macros:: Backward compatibility macros
* Autoconf 1:: Tips for upgrading your files
* Autoconf 2.13:: Some fresher tips
* Using an Autotest Test Suite:: Autotest and the user
* Writing Testsuites:: Autotest macros
* Using an Autotest Test Suite:: Autotest and the user
* Writing Testsuites:: Autotest macros
* Making testsuite Scripts:: Using autom4te to create @command{testsuite}
Using an Autotest Test Suite
* Making testsuite Scripts:: Using autom4te to create @command{testsuite}
Using an Autotest Test Suite
@item
a shell script called @file{config.status} that, when run, recreates
@item
a shell script called @file{config.status} that, when run, recreates
@item
an optional shell script normally called @file{config.cache}
@item
an optional shell script normally called @file{config.cache}
@menu
* Writing Autoconf Input:: What to put in an Autoconf input file
@menu
* Writing Autoconf Input:: What to put in an Autoconf input file
@end menu
@node Writing Autoconf Input
@end menu
@node Writing Autoconf Input
or specialized features, @file{configure.ac} might need to contain some
hand-crafted shell commands; see @ref{Portable Shell, , Portable Shell
Programming}. The @command{autoscan} program can give you a good start
or specialized features, @file{configure.ac} might need to contain some
hand-crafted shell commands; see @ref{Portable Shell, , Portable Shell
Programming}. The @command{autoscan} program can give you a good start
information).
Previous versions of Autoconf promoted the name @file{configure.in},
information).
Previous versions of Autoconf promoted the name @file{configure.in},
@section Using @command{autoscan} to Create @file{configure.ac}
@cindex @command{autoscan}
@section Using @command{autoscan} to Create @file{configure.ac}
@cindex @command{autoscan}
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
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
information about a program that can help with that job).
When using @command{autoscan} to maintain a @file{configure.ac}, simply
information about a program that can help with that job).
When using @command{autoscan} to maintain a @file{configure.ac}, simply
Prepend @var{dir} to the include path. Multiple invocations accumulate.
@end table
Prepend @var{dir} to the include path. Multiple invocations accumulate.
@end table
@section Using @command{ifnames} to List Conditionals
@cindex @command{ifnames}
@section Using @command{ifnames} to List Conditionals
@cindex @command{ifnames}
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
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
@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
@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
Print the version number of Autoconf and exit.
@end table
Print the version number of Autoconf and exit.
@end table
@section Using @command{autoconf} to Create @command{configure}
@cindex @command{autoconf}
@section Using @command{autoconf} to Create @command{configure}
@cindex @command{autoconf}
@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
@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
@item --trace=@var{macro}[:@var{format}]
@itemx -t @var{macro}[:@var{format}]
@item --trace=@var{macro}[:@var{format}]
@itemx -t @var{macro}[:@var{format}]
The @var{format} is a regular string, with newlines if desired, and
several special escape codes. It defaults to @samp{$f:$l:$n:$%}; see
The @var{format} is a regular string, with newlines if desired, and
several special escape codes. It defaults to @samp{$f:$l:$n:$%}; see
@item --initialization
@itemx -i
@item --initialization
@itemx -i
@section Using @command{autoreconf} to Update @command{configure} Scripts
@cindex @command{autoreconf}
@section Using @command{autoreconf} to Update @command{configure} Scripts
@cindex @command{autoreconf}
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
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
-Invocation, , Invoking the @code{autopoint} Program, gettext,
+@code{AM_GNU_GETTEXT_VERSION(@var{gettext-version})}.
+@xref{autopoint, , Invoking the @code{autopoint} Program, gettext,
-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.
+ GNU @code{gettext} utilities}, for further details.
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
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
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
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
for more details.
The @var{inputs} may be absolute or relative file names. In the latter
for more details.
The @var{inputs} may be absolute or relative file names. In the latter
so @file{config.status} ensures that @file{config.h} is considered up to
date. @xref{Output}, for more information about @code{AC_OUTPUT}.
so @file{config.status} ensures that @file{config.h} is considered up to
date. @xref{Output}, for more information about @code{AC_OUTPUT}.
configuration-related dependencies.
@node Configuration Headers
configuration-related dependencies.
@node Configuration Headers
@menu
* Header Templates:: Input for the configuration headers
@menu
* Header Templates:: Input for the configuration headers
* Autoheader Macros:: How to specify CPP templates
@end menu
* Autoheader Macros:: How to specify CPP templates
@end menu
generated header.
Since it is a tedious task to keep a template header up to date, you may
generated header.
Since it is a tedious task to keep a template header up to date, you may
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
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
probably use @samp{AH_BOTTOM} to append the @samp{#include} directive.
probably use @samp{AH_BOTTOM} to append the @samp{#include} directive.
@subsection Using @command{autoheader} to Create @file{config.h.in}
@cindex @command{autoheader}
@subsection Using @command{autoheader} to Create @file{config.h.in}
@cindex @command{autoheader}
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
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
If you use this macro without specifying @var{action-if-universal}, you
should also use @code{AC_CONFIG_HEADERS}; otherwise
If you use this macro without specifying @var{action-if-universal}, you
should also use @code{AC_CONFIG_HEADERS}; otherwise
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},
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},
inconsistent, composed of results depending upon two different
compilers.
inconsistent, composed of results depending upon two different
compilers.
@item
@var{variable} is kept during automatic reconfiguration
@item
@var{variable} is kept during automatic reconfiguration
line argument, including when no cache is used:
@example
line argument, including when no cache is used:
@example
+@@ -10666,11 +10654,11 @@
It supports M4 extensions designed for use in tools like Autoconf.
@menu
It supports M4 extensions designed for use in tools like Autoconf.
@menu
--* autom4te Invocation:: A @acronym{GNU} M4 wrapper
-+* autom4te:: A @acronym{GNU} M4 wrapper
+-* autom4te Invocation:: A GNU M4 wrapper
++* autom4te:: A GNU M4 wrapper
* Customizing autom4te:: Customizing the Autoconf package
@end menu
* Customizing autom4te:: Customizing the Autoconf package
@end menu
@subsection Invoking @command{autom4te}
The command line arguments are modeled after M4's:
@subsection Invoking @command{autom4te}
The command line arguments are modeled after M4's:
@item --preselect=@var{macro}
@itemx -p @var{macro}
@item --preselect=@var{macro}
@itemx -p @var{macro}
wrapped in between a @samp{begin-language: "@var{language}"},
@samp{end-language: "@var{language}"} pair.
wrapped in between a @samp{begin-language: "@var{language}"},
@samp{end-language: "@var{language}"} pair.
more generally arguments, are introduced by @samp{args:
@var{arguments}}. You may use the traditional shell syntax to quote the
@var{arguments}.
more generally arguments, are introduced by @samp{args:
@var{arguments}}. You may use the traditional shell syntax to quote the
@var{arguments}.
When the user runs @samp{autoconf -W error}, warnings from
@code{m4_warn} (including those issued through @code{AC_DIAGNOSE} and
When the user runs @samp{autoconf -W error}, warnings from
@code{m4_warn} (including those issued through @code{AC_DIAGNOSE} and
@node Dependencies Between Macros
@section Dependencies Between Macros
@node Dependencies Between Macros
@section Dependencies Between Macros
-@@ -18580,16 +18568,16 @@
+@@ -21307,16 +21295,16 @@
* System Type:: Specifying the system type
* Sharing Defaults:: Setting site-wide defaults for @command{configure}
* Defining Variables:: Specifying the compiler etc.
* System Type:: Specifying the system type
* Sharing Defaults:: Setting site-wide defaults for @command{configure}
* Defining Variables:: Specifying the compiler etc.
@chapter config.status Invocation
@cindex @command{config.status}
@chapter config.status Invocation
@cindex @command{config.status}
@menu
* Obsolete config.status Use:: Obsolete convention for @command{config.status}
* acconfig Header:: Additional entries in @file{config.h.in}
@menu
* Obsolete config.status Use:: Obsolete convention for @command{config.status}
* acconfig Header:: Additional entries in @file{config.h.in}
* Obsolete Macros:: Backward compatibility macros
* Autoconf 1:: Tips for upgrading your files
* Autoconf 2.13:: Some fresher tips
* Obsolete Macros:: Backward compatibility macros
* Autoconf 1:: Tips for upgrading your files
* Autoconf 2.13:: Some fresher tips
@section Obsolete @file{config.status} Invocation
@file{config.status} now supports arguments to specify the files to
@section Obsolete @file{config.status} Invocation
@file{config.status} now supports arguments to specify the files to
Before, environment variables had to be used.
@defvar CONFIG_COMMANDS
Before, environment variables had to be used.
@defvar CONFIG_COMMANDS
@file{config.status} ignores this variable.
@end defvar
@file{config.status} ignores this variable.
@end defvar
self-contained, and should not depend upon @file{acconfig.h} etc.
self-contained, and should not depend upon @file{acconfig.h} etc.
@section Using @command{autoupdate} to Modernize @file{configure.ac}
@cindex @command{autoupdate}
@section Using @command{autoupdate} to Modernize @file{configure.ac}
@cindex @command{autoupdate}
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
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
If you distribute @file{install.sh} with your package, rename it to
@file{install-sh} so @command{make} builtin rules don't inadvertently
If you distribute @file{install.sh} with your package, rename it to
@file{install-sh} so @command{make} builtin rules don't inadvertently
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.
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.
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
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
@menu
* Using an Autotest Test Suite:: Autotest and the user
* Writing Testsuites:: Autotest macros
@menu
* Using an Autotest Test Suite:: Autotest and the user
* Writing Testsuites:: Autotest macros
* Making testsuite Scripts:: Using autom4te to create @command{testsuite}
@end menu
* Making testsuite Scripts:: Using autom4te to create @command{testsuite}
@end menu
@itemize @bullet
@item a debugging script named @file{run} which reruns the test in
@itemize @bullet
@item a debugging script named @file{run} which reruns the test in
of debugging scripts has the purpose of easing the chase for bugs.
@item all the files created with @code{AT_DATA}
of debugging scripts has the purpose of easing the chase for bugs.
@item all the files created with @code{AT_DATA}
@section Running @command{testsuite} Scripts
@cindex @command{testsuite}
@section Running @command{testsuite} Scripts
@cindex @command{testsuite}
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
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
which can be a long process for complex @file{configure.ac}.
This is why all these tools, instead of running directly M4, invoke
which can be a long process for complex @file{configure.ac}.
This is why all these tools, instead of running directly M4, invoke
Summary(ru.UTF-8): GNU autoconf - автоконфигуратор исходных текстов
Summary(uk.UTF-8): GNU autoconf - автоконфігуратор вихідних текстів
Name: autoconf
Summary(ru.UTF-8): GNU autoconf - автоконфигуратор исходных текстов
Summary(uk.UTF-8): GNU autoconf - автоконфігуратор вихідних текстів
Name: autoconf
-Version: 2.65
-Release: 4
+Version: 2.66
+Release: 1
License: GPL v2+/v3+
Group: Development/Building
# stable releases:
Source0: http://ftp.gnu.org/gnu/autoconf/%{name}-%{version}.tar.xz
License: GPL v2+/v3+
Group: Development/Building
# stable releases:
Source0: http://ftp.gnu.org/gnu/autoconf/%{name}-%{version}.tar.xz
-# Source0-md5: dfb23a46ecb73a0abade39c053a6c5a1
+# Source0-md5: adbe7e7fde3c34a400d33a8ac631c877
# devel releases:
#Source0: http://alpha.gnu.org/gnu/autoconf/%{name}-%{version}.tar.bz2
Patch0: %{name}-mawk.patch
# devel releases:
#Source0: http://alpha.gnu.org/gnu/autoconf/%{name}-%{version}.tar.bz2
Patch0: %{name}-mawk.patch
projects / packages / autoconf.git / commitdiff