How to fi autotools failures分析和总结分析和总结.docxVIP

How to fix autotools failures Content: Introduction With the term autotools we usually refer to the tools developed by the GNU project to create platform and operating-system independent build systems, autoconf, automake and libtool. Although not every package uses all of them at the same time, most of the modern ones do so; older packages often does not use automake and libtool instead; KDE packages uses a more complex build system that relies at the end on the three software above. Its simple to recognize a package which build system is based on autotools: if theres a configure script, and a configure.in or configure.ac file, the build system is based on autoconf; if there are one or more Makefile.am files in the various sub-directories, its also automake based; if theres a ltmain.sh script, its also using libtool. To build a package that uses an autotools-based build system, the tools themselves arent strictly needed: the configure script is a simple Bourne Shell script (usually, but this will be discussed lately) and it transforms the Makefile.in files into simpler Makefile for make (or, more often, gmake). In spite of them being optional for building the software, often the patches needed to solve problems like --as-needed build failure or automagic dependencies requires us to re-run the tools to recreate scripts and makefiles templates. This guide wont give directions on how to fix packages errors with use of autotools, as thats a wide topic that requires lot of stuff to be explained. For a simple introductions of the most common errors while using autotools, its rather suggested to read the best practices with autotools article. Instead, it will describe the common cases where re-running autotools lead to failures, either on the rebuilding of the script or at build time. Re-running autotools The first important thing to know is how to properly rebuild autotools support, as that is a common problem that makes some ebuild fail. The order in which autotools are