%general-entities; ]> Autoconf-&autoconf-version; Autoconf <para>The Autoconf package contains programs for producing shell scripts that can automatically configure source code.</para> <segmentedlist> <segtitle>&buildtime;</segtitle> <segtitle>&diskspace;</segtitle> <seglistitem><seg>0.5 SBU</seg><seg>7.7 MB</seg></seglistitem> </segmentedlist> <segmentedlist> <segtitle>Autoconf installation depends on</segtitle> <seglistitem><seg>Bash, Coreutils, Diffutils, Grep, M4, Make, Perl, Sed</seg></seglistitem> </segmentedlist> </sect2> <sect2 role="installation"> <title>Installation of Autoconf Prepare Autoconf for compilation: ./configure --prefix=/usr Compile the package: make To test the results, issue: make check. This takes a long time, about 2 SBUs. Install the package: make install Contents of Autoconf Installed programs autoconf, autoheader, autom4te, autoreconf, autoscan, autoupdate and ifnames Short descriptions autoconf autoconf is a tool for producing shell scripts that automatically configure software source code packages to adapt to many kinds of Unix-like systems. The configuration scripts it produces are independent -- running them does not require the autoconf program. autoheader autoheader is a tool for creating template files of C #define statements for configure to use. autom4te autom4te is a wrapper for the M4 macro processor. autoreconf autoreconf comes in handy when there are a lot of autoconf-generated configure scripts around. The program runs autoconf and autoheader repeatedly (where appropriate) to remake the autoconf configure scripts and configuration header templates in a given directory tree. autoscan autoscan can help to create a configure.in file for a software package. It examines the source files in a directory tree, searching them for common portability problems and creates a configure.scan file that serves as as a preliminary configure.in for the package. autoupdate autoupdate modifies a configure.in file that still calls autoconf macros by their old names to use the current macro names. ifnames ifnames can be helpful when writing a configure.in for a software package. It 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 to determine what configure needs to check. It can fill in some gaps in a configure.in file generated by autoscan.