AUTOCONF(1)
β¨ NAME β¨
ok bestie come CLOSE π this is the autoconf manual page, and it's literally the thing that generates your configuration scripts. like, the whole ./configure moment? that's autoconf's child. no cap.
π¦ SYNOPSIS π¦
autoconf [OPTION] ... [TEMPLATE-FILE]
πΈ DESCRIPTION πΈ
So here's the tea π«: autoconf generates a configuration script for you. If you hand it a TEMPLATE-FILE, it uses that. If you don't, it looks for configure.ac β and if that's not there, it goes looking for configure.in instead.
Where does the output go? Here's the rule, don't mix it up π: if you gave it a TEMPLATE-FILE, the output goes to standard output. If you didn't, it gets written into configure. that's it that's the whole vibe.
π Operation modes π
-h,--helpβ prints this help, then dips out. bye π-V,--versionβ prints the version number, then exits. periodt.-v,--verboseβ verbosely reports the processing. she's chatty β¨-d,--debugβ doesn't remove temporary files. leaving the evidence behind, we love that π-o,--output=FILEβ saves the output into FILE. (stdout is the default, fyi)-W,--warnings=CATEGORYβ reports the warnings falling in CATEGORY β and the default category issyntax
β¨ OPTIONS β¨
--opt-functionsβ uses shell-functions to reduce repetition. DRY queen π
π Warning categories include: π
crossβ cross compilation issuesobsoleteβ obsolete constructs (she's giving vintage, but like, not in a good way π)syntaxβ dubious syntactic constructsallβ all the warningsno-CATEGORYβ turns off the warnings on CATEGORYnoneβ turns off all the warnings. silence, iconically π€«errorβ warnings are error
The environment variable WARNINGS is honored. yes, she reads her environment, main character energy π
π Library directories π
-A,--autoconf-dir=ACDIRβ where Autoconf's macro files live (rarely needed, so don't stress bestie)-l,--localdir=DIRβ the location of theaclocal.m4file
π§ Tracing π§
-t,--trace=MACROβ reports the list of calls to MACRO-i,--initializationβ also traces Autoconf's initialization process
lowkey important: in tracing mode, no configuration script is created. like, none. zero. the script simply does not manifest π
π AUTHOR π
Written by David J. MacKenzie. we stan a legend π«Ά
π REPORTING BUGS π
Report bugs to <dickey@invisible-island.net>.
(be nice to the inbox bestie, that's someone's whole email π)
π COPYRIGHT π
Copyright 2003-2024,2025 Thomas E. Dickey Copyright 1992, 1993, 1994, 1996, 1999, 2000, 2001 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. (translation: she's free, she's open, she promises nothing legally, and that's just the deal β¨)
π SEE ALSO π
autoconf(1)autoreconf(1)autoupdate(1)autoheader(1)autoscan(1)config.guess(1)config.sub(1)ifnames(1)libtool(1)
The full documentation for autoconf is maintained as a Texinfo manual. If the info and autoconf programs are properly installed at your site, the command
info autoconf
should give you access to the complete manual. go read it, i'll wait πβ¨
ok that's the whole page, you ate that π½οΈπ this was GNU Autoconf 2.52.20260412, dated April 2026, and yes the header still says AUTOCONF(1) because some things are sacred. mwah π
π¦ where this page comes from
- ubuntu stonking: autoconf-dickey 2.52+20260412-1 Β· GPL-2.0-or-later WITH Autoconf exception
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms