15. Obsolete Constructs

Autoconf changes, and throughout the years some constructs are obsoleted. Most of the changes involve the macros, but the tools themselves, or even some concepts, are now considered obsolete.

You may completely skip this chapter if you are new to Autoconf, its intention is mainly to help maintainers updating their packages by understanding how to move to more modern constructs.

15.1 Obsolete `config.status' Invocation    Different calling convention

15.2 `acconfig.h'    Additional entries in `config.h.in'

15.3 Using autoupdate to Modernize `configure.ac'    Automatic update of `configure.ac'

15.4 Obsolete Macros    Backward compatibility macros

15.5 Upgrading From Version 1    Tips for upgrading your files

15.6 Upgrading From Version 2.13    Some fresher tips

" It reminds me of the claim that Americans built the first computer... It depends on what properties are necessary for a device to be classed as a computer: That it's electronic? That it has Randomly Accessible Memory? That it operates on a stored program? I am tempted to suggest that one of the requirements implicit in some people's lists is that it was built in America. "