glfs/archive/autoconf213.xml
Xi Ruoyao 4e7ec17c2e
autoconf213: Archive
With a simple hack in SeaMonkey, autoconf-2.13 is not needed anymore.

Fixes: #18459
2023-11-10 14:35:47 +08:00

275 lines
9.0 KiB
XML

<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
<!ENTITY % general-entities SYSTEM "../../general.ent">
%general-entities;
<!ENTITY autoconf213-download-http "&gnu-http;/autoconf/autoconf-&autoconf213-version;.tar.gz">
<!ENTITY autoconf213-download-ftp " ">
<!ENTITY autoconf213-md5sum "9de56d4a161a723228220b0f425dc711">
<!ENTITY autoconf213-size "434 KB">
<!ENTITY autoconf213-buildsize "2.8 MB">
<!ENTITY autoconf213-time "less than 0.1 SBU (additional 0.1 SBU for the tests)">
]>
<sect1 id="autoconf213" xreflabel="Autoconf-&autoconf213-version;">
<?dbhtml filename="autoconf213.html"?>
<title>Autoconf&autoconf213-version;</title>
<indexterm zone="autoconf213">
<primary sortas="a-Autoconf213">Autoconf213</primary>
</indexterm>
<sect2 role="package">
<title>Introduction to Autoconf2.13</title>
<para>
<application>Autoconf2.13</application> is an old version of
<application>Autoconf</application> . This old version accepts switches
which are not valid in more recent versions and Mozilla applications
still need these switches now, so they require this old version for
regenerating the configure scripts. Unlike other Mozilla
applications, <application>SeaMonkey</application> release tarballs
do not contain the pre-generated configure scripts, so this old
version is required even if configure files have not been changed.
</para>
&lfs120_checked;
<bridgehead renderas="sect3">Package Information</bridgehead>
<itemizedlist spacing="compact">
<listitem>
<para>
Download (HTTP): <ulink url="&autoconf213-download-http;"/>
</para>
</listitem>
<listitem>
<para>
Download (FTP): <ulink url="&autoconf213-download-ftp;"/>
</para>
</listitem>
<listitem>
<para>
Download MD5 sum: &autoconf213-md5sum;
</para>
</listitem>
<listitem>
<para>
Download size: &autoconf213-size;
</para>
</listitem>
<listitem>
<para>
Estimated disk space required: &autoconf213-buildsize;
</para>
</listitem>
<listitem>
<para>
Estimated build time: &autoconf213-time;
</para>
</listitem>
</itemizedlist>
<bridgehead renderas="sect3">Additional Downloads</bridgehead>
<itemizedlist spacing="compact">
<listitem>
<para>
Required patch:
<ulink url="&patch-root;/autoconf-&autoconf213-version;-consolidated_fixes-1.patch"/>
</para>
</listitem>
</itemizedlist>
<!--
<bridgehead renderas="sect3">Autoconf2.13 Dependencies</bridgehead>
<bridgehead renderas="sect4">Optional</bridgehead>
<para role="optional">
<xref linkend="dejagnu"/> (Required for the tests)
</para>
-->
</sect2>
<sect2 role="installation">
<title>Installation of Autoconf2.13</title>
<para>
Install <application>Autoconf</application> by running the following
commands:
</para>
<screen><userinput>patch -Np1 -i ../autoconf-&autoconf213-version;-consolidated_fixes-1.patch &amp;&amp;
mv -v autoconf.texi autoconf213.texi &amp;&amp;
rm -v autoconf.info &amp;&amp;
./configure --prefix=/usr --program-suffix=2.13 &amp;&amp;
make</userinput></screen>
<para>
To test the installation <!--, if you have installed <xref linkend="dejagnu"/>,-->
issue <command>make check</command> (all 253 tests should pass).
</para>
<para>
Now, as the <systemitem class="username">root</systemitem> user:
</para>
<screen role="root"><userinput>make install &amp;&amp;
install -v -m644 autoconf213.info /usr/share/info &amp;&amp;
install-info --info-dir=/usr/share/info autoconf213.info</userinput></screen>
</sect2>
<sect2 role="commands">
<title>Command Explanations</title>
<para>
<command>mv -v autoconf.texi autoconf213.texi</command>: ensure that the
info file added by this package will not overwrite the more recent version.
</para>
<para>
<command>rm -v autoconf.info</command>: ensure that the info file will be
created by the current version of texinfo.
</para>
<para>
<command>--program-suffix=2.13</command>: ensure that the installed
programs have the version added to their names, so that only a script
which specifically looks for these old versions will find them.
</para>
<para>
<command>install -v -m644 ...</command>: the patch removes install-info
from the Makefile because that would install (and if necessary recreate)
standards.info which is an old version, so now
<filename>autoconf213.info</filename> has to be manually installed.
</para>
</sect2>
<sect2 role="content">
<title>Contents</title>
<segmentedlist>
<segtitle>Installed Programs</segtitle>
<segtitle>Installed Library</segtitle>
<segtitle>Installed Directory</segtitle>
<seglistitem>
<seg>
autoconf2.13,
autoheader2.13,
autoreconf2.13,
autoscan2.13,
autoupdate2.13, and
ifnames2.13
</seg>
<seg>
None
</seg>
<seg>
/usr/share/autoconf-2.13
</seg>
</seglistitem>
</segmentedlist>
<variablelist>
<bridgehead renderas="sect3">Short Descriptions</bridgehead>
<?dbfo list-presentation="list"?>
<?dbhtml list-presentation="table"?>
<varlistentry id="autoconf2.13">
<term><command>autoconf2.13</command></term>
<listitem>
<para>
Produces shell scripts that automatically configure software source
code packages to adapt to many kinds of Unix-like systems
</para>
<indexterm zone="autoconf213 autoconf2.13">
<primary sortas="b-autoconf2.13">autoconf2.13</primary>
</indexterm>
</listitem>
</varlistentry>
<varlistentry id="autoheader2.13">
<term><command>autoheader2.13</command></term>
<listitem>
<para>
is a tool for creating template files of C
<emphasis>#define</emphasis> statements for configure to use
</para>
<indexterm zone="autoconf213 autoheader2.13">
<primary sortas="b-autoheader2.13">autoheader2.13</primary>
</indexterm>
</listitem>
</varlistentry>
<varlistentry id="autoreconf2.13">
<term><command>autoreconf2.13</command></term>
<listitem>
<para>
This automatically runs <command>autoconf2.13</command>,
<command>autoheader2.13</command>, <command>aclocal</command>,
<command>automake</command>, <command>gettextize</command> and
<command>libtoolize</command> in the right order when changes
have been made to <command>autoconf</command> or
<command>automake</command> template files
</para>
<indexterm zone="autoconf213 autoreconf2.13">
<primary sortas="b-autoreconf2.13">autoreconf2.13</primary>
</indexterm>
</listitem>
</varlistentry>
<varlistentry id="autoscan2.13">
<term><command>autoscan2.13</command></term>
<listitem>
<para>
Can be used as a preliminary step in creating a
<filename>configure.in</filename> file
</para>
<indexterm zone="autoconf213 autoscan2.13">
<primary sortas="b-autoscan2.13">autoscan2.13</primary>
</indexterm>
</listitem>
</varlistentry>
<varlistentry id="autoupdate2.13">
<term><command>autoupdate2.13</command></term>
<listitem>
<para>
Modifies a <filename>configure.in</filename> file that still
calls <command>autoconf</command> macros by their old names
to use the current macro names
</para>
<indexterm zone="autoconf213 autoupdate2.13">
<primary sortas="b-autoupdate2.13">autoupdate2.13</primary>
</indexterm>
</listitem>
</varlistentry>
<varlistentry id="ifnames2.13">
<term><command>ifnames2.13</command></term>
<listitem>
<para>
Prints the identifiers that the package uses in C preprocessor
conditionals [If a package has already been set up to have some
portability, this program can help determine what configure needs to
check for. It can also fill in gaps in a configure.in file generated
by autoscan]
</para>
<indexterm zone="autoconf213 ifnames2.13">
<primary sortas="b-ifnames2.13">ifnames2.13</primary>
</indexterm>
</listitem>
</varlistentry>
</variablelist>
</sect2>
</sect1>