Name Date Size

..27-Apr.-20224 KiB

.gitattributesH A D13-Aug.-2017417

.gitignoreH A D03-Oct.-20211 KiB

.prev-versionH A D16-Feb.-20215

.x-update-copyrightH A D16-Feb.-2021772

AUTHORSH A D19-May-20227.9 KiB

bin/H19-May-20224 KiB

bootstrapH A D29-Jun.-20227.5 KiB

BUGSH A D19-May-20221.4 KiB

build-aux/H19-May-20224 KiB

cfg.mkH A D19-May-20223.7 KiB

ChangeLog.0H A D17-Sep.-201712.6 KiB

ChangeLog.1H A D17-Sep.-201767.2 KiB

ChangeLog.2H A D17-Sep.-2017420 KiB

ChangeLog.3H A D23-Sep.-2017835.1 KiB

configure.acH A D19-May-20227.6 KiB

COPYINGH A D10-Jul.-202017.6 KiB

COPYING.EXCEPTIONH A D10-Jul.-20201.8 KiB

COPYINGv3H A D10-Jul.-202034.3 KiB

doc/H22-Jun.-20224 KiB

GNUmakefileH A D16-Feb.-20214.5 KiB

HACKINGH A D19-May-20226.1 KiB

lib/H19-May-20224 KiB

m4/H19-May-20224 KiB

maint.mkH A D29-Jun.-202265.1 KiB

Makefile.amH A D19-May-20226.2 KiB

man/H19-May-20224 KiB

NEWSH A D19-May-2022101.7 KiB

READMEH A D19-May-20223.4 KiB

README-alphaH A D19-May-20221.1 KiB

README-hackingH A D19-May-20225.3 KiB

tests/H29-Jun.-20224 KiB

THANKSH A D19-May-202221.5 KiB

TODOH A D19-May-202223 KiB

README

1-*- text -*-
2
3Autoconf
4
5Autoconf is an extensible package of M4 macros that produce shell
6scripts to automatically configure software source code packages.
7These scripts can adapt the packages to many kinds of UNIX-like
8systems without manual user intervention.  Autoconf creates a
9configuration script for a package from a template file that lists the
10operating system features that the package can use, in the form of M4
11macro calls.
12
13Producing configuration scripts using Autoconf requires GNU M4 and
14Perl.  You should install GNU M4 (version 1.4.6 or later is required;
151.4.14 or later is recommended) and Perl (5.006 or later) before
16configuring Autoconf, so that Autoconf's configure script can find
17them.  The configuration scripts produced by Autoconf are
18self-contained, so their users do not need to have Autoconf (or GNU
19M4, Perl, etc.).
20
21You can get GNU M4 here:
22
23https://ftp.gnu.org/gnu/m4/
24
25The file INSTALL should be distributed with packages that use
26Autoconf-generated configure scripts and Makefiles that conform to the
27GNU coding standards.  The package's README can just give an overview
28of the package, where to report bugs, and a pointer to INSTALL for
29instructions on compilation and installation.  This removes the need
30to maintain many similar sets of installation instructions.
31
32Be sure to read BUGS and INSTALL.
33
34Mail suggestions to autoconf@gnu.org, report bugs to
35bug-autoconf@gnu.org, and submit patches to autoconf-patches@gnu.org.
36All changes can be tracked at the read-only autoconf-commit@gnu.org.
37Always include the Autoconf version number, which you can get by
38running 'autoconf --version'.  Archives of bug-autoconf@gnu.org can be
39found in <https://lists.gnu.org/archive/html/bug-autoconf/>, and
40similarly for the other mailing lists.
41
42Licensing
43=========
44Autoconf is released under the General Public License version 3 (GPLv3+).
45Additionally, Autoconf includes a licensing exception in some of its
46source files; see the respective copyright notices for how your
47project is impacted by including scripts generated by Autoconf, and the
48COPYING.EXCEPTION file for the exception in terms of the Additional
49Permissions as described in section 7 of GPLv3.
50
51For more licensing information, see
52<https://www.gnu.org/licenses/gpl-faq.html> and
53<https://www.gnu.org/licenses/exceptions.html>.
54
55For any copyright year range specified as YYYY-ZZZZ in this package
56note that the range specifies every single year in that closed interval.
57
58GNU Project notice
59==================
60Autoconf is part of the GNU Operating System, developed by the GNU Project.
61
62If you are the author of an awesome program and want to join us in
63writing Free (libre) Software, please consider making it an official
64GNU program and become a GNU Maintainer.  Instructions on how to do
65this are here:
66  https://www.gnu.org/help/evaluation
67
68Don't have a program to contribute?  Look at all the other ways to help:
69  https://www.gnu.org/help/help.html
70
71And to learn more about Free (libre) Software in general, please read
72and share this page:
73  https://gnu.org/philosophy/free-sw.html
74
75We are looking forward to hacking with you!
76
77-----
78
79Copyright (C) 1992-1994, 1998, 2000-2017, 2020-2022 Free Software
80Foundation, Inc.
81
82Copying and distribution of this file, with or without modification,
83are permitted in any medium without royalty provided the copyright
84notice and this notice are preserved.  This file is offered as-is,
85without warranty of any kind.
86

README-alpha

1-*- text -*-
2
3This is a test release of this package.  Using it more or less
4implicitly signs you up to help us find whatever problems you report.
5
6You need up-to-date build tools.  To avoid some bootstrapping issues
7you may need to run the command "autoreconf -fvim" first, before
8running "configure".
9
10The documentation still needs more work.  Suggestions welcome.
11Patches even more welcome.
12
13Please send comments and problem reports about this test release to
14bug-autoconf@gnu.org.  This program will get better only if you report
15the problems you encounter.
16
17Please, *do not package this*, *do not distribute it* widely, it is
18not ready for full scale use.  Because it is not fully functional, if
19you distribute this package, we will be buried under bug reports from
20panicked users.  We don't have time to spend on this, and nor do the
21users.
22
23-----
24
25Copyright (C) 2000-2003, 2009-2017, 2020-2022 Free Software Foundation,
26Inc.
27
28Copying and distribution of this file, with or without modification,
29are permitted in any medium without royalty provided the copyright
30notice and this notice are preserved.  This file is offered as-is,
31without warranty of any kind.
32

README-hacking

1-*- outline -*-
2
3These notes intend to help people working on the checked-out sources.
4These requirements do not apply when building from a distribution
5tarball.  Don't put this file into the distribution.  Don't mention it
6in the ChangeLog.  You may want to also see HACKING for
7maintainer-specific rules.
8
9* Requirements
10
11We've opted to keep only the highest-level sources in the GIT repository.
12This eases our maintenance burden, (fewer merges etc.), but imposes more
13requirements on anyone wishing to build from the just-checked-out sources.
14For example, you have to use recent stable versions of the maintainer
15tools we depend upon, including:
16
17- Automake 1.11+ <https://www.gnu.org/software/automake/>
18- Help2man 1.29+ <https://www.gnu.org/software/help2man/>
19- M4 1.4.6+ <https://www.gnu.org/software/m4/>
20- Perl 5.006+ <https://www.cpan.org/>
21- Texinfo 4.11+ <https://www.gnu.org/software/texinfo/>
22
23The following are useful as well, if you want to be able to run commands
24like "make dist-xz" or "make distcheck":
25
26- Gzip <https://www.gnu.org/software/gzip/>
27- Tar <https://www.gnu.org/software/tar/>
28- XZ Utils <https://tukaani.org/xz/>
29
30Although we try to keep the CVS mirror of the git repository usable,
31some of the tests in the testsuite will fail if git was not used to
32generate the version string.  Therefore, we recommend:
33
34- Git 1.4.4+ <https://git-scm.com/>
35
36You may find it useful to install the git-merge-changelog merge driver:
37https://git.savannah.gnu.org/cgit/gnulib.git/plain/lib/git-merge-changelog.c
38
39then add the following to .git/config or ~/.gitconfig:
40[merge "merge-changelog"]
41	name = GNU ChangeLog merge driver
42	driver = git-merge-changelog %O %A %B
43[diff "texinfo"]
44	funcname = ^@node[\t ][\t ]*\\([^,][^,]*\\)
45
46Only building the initial full source tree will be a bit painful.
47Later, a plain 'git pull && make' should be sufficient.
48
49If you want to test Autoconf on a machine without git, it may be
50easier to first bootstrap Autoconf on a different machine with git,
51run 'make dist', and copy the tarball to the machine under test.  It
52should always be possible to create a self-contained tarball which
53does not rely on the bootstrap-only tools.
54
55* First GIT checkout
56
57You can get an anonymous copy of the source repository using any one
58of these three methods, although the CVS mirror is less tested:
59
60  $ git clone git://git.sv.gnu.org/autoconf
61  $ git clone https://git.sv.gnu.org/r/autoconf.git
62  $ cvs -d:pserver:anonymous@pserver.git.sv.gnu.org:/srv/git/autoconf.git \
63      co -d autoconf HEAD
64
65If you have a Savannah user name and commit rights to the Autoconf
66project, you should use this instead:
67
68  $ git clone <username>@git.sv.gnu.org:/srv/git/autoconf.git
69
70The next step is to generate files like configure and Makefile.in:
71
72  $ cd autoconf
73  $ ./bootstrap
74
75The bootstrap script generates the same files ���autoreconf -vi��� would,
76in a normal package, but it uses autoconf *from the git sources* to do
77it.  This means you do not need autoconf installed already, and you do
78not need to re-generate ���configure��� after building Autoconf.
79
80You can now build and test the package:
81
82  $ ./configure
83  $ make
84  $ make check
85
86At this point, there should be no difference between your local copy,
87and the GIT master copy:
88
89  $ git diff
90
91should output no difference.
92
93The testsuite is run by 'make check'.  You may find it useful to run a
94subset of the testsuite; for example, all tests with the 'm4sugar'
95keyword as well as test 10:
96
97  $ make check TESTSUITEFLAGS='10 -k m4sugar'
98
99You can pass options to configure scripts invoked by the testsuite by
100setting the configure_options variable:
101
102  $ make check TESTSUITEFLAGS='configure_options="CC=gcc-2.95"'
103
104The test suite is not automatically parallelized by ���make -j���.  If you
105want to parallelize the testsuite, you need to use TESTSUITEFLAGS for
106that, too:
107
108  $ make check TESTSUITEFLAGS=-j8
109
110* Submitting patches
111
112All patches should be submitted to <autoconf-patches@gnu.org> for
113review, in context or unified diff format against the latest sources.
114In most cases, a patch should include a test case, to ensure that
115regressions do not creep back in.  Remember to add documentation and a
116NEWS entry for anything that is visible to the user.
117
118If your change is significant (i.e., if it adds more than ~10 lines),
119then you'll have to have a copyright assignment on file with the FSF.
120Since that involves first an email exchange between you and the FSF,
121and then the exchange (FSF to you, then back) of an actual sheet of paper
122with your signature on it, and finally, some administrative processing
123in Boston, the process can take a few weeks.
124
125The forms to choose from are in gnulib's doc/Copyright/ directory.
126If you want to assign a single change, you should use the file,
127doc/Copyright/request-assign.changes:
128
129    https://git.sv.gnu.org/cgit/gnulib.git/tree/doc/Copyright/request-assign.changes
130
131If you would like to assign past and future autoconf work,
132you'd use doc/Copyright/request-assign.future:
133
134    https://git.sv.gnu.org/cgit/gnulib.git/tree/doc/Copyright/request-assign.future
135
136Enjoy!
137
138-----
139
140Copyright (C) 2002-2017, 2020-2022 Free Software Foundation, Inc.
141
142Copying and distribution of this file, with or without modification,
143are permitted in any medium without royalty provided the copyright
144notice and this notice are preserved.  This file is offered as-is,
145without warranty of any kind.
146