Also sprach Akim Demaille: } } ** autom4te } } - Supports --cache, and --no-cache. } } - ~/.autom4te.cfg makes it possible to disable the caching mechanism } (autom4te.cache). See `Customizing autom4te' in the documentation. } This doesn't work.
[dangermouse self_installed] ls -ACF autoconf-2.53/ .autom4te.cfg configure.ac autoconf-2.53.tar.gz automake-1.6/ libtool-1.4.2/ autoconf-2.55/ automake-1.6.tar.gz libtool-1.4.2.tar.gz autoconf-2.55.tar.gz configure* [dangermouse self_installed] ls -ACF autoconf-2.53/ .autom4te.cfg configure.ac autoconf-2.53.tar.gz automake-1.6/ libtool-1.4.2/ autoconf-2.55/ automake-1.6.tar.gz libtool-1.4.2.tar.gz autoconf-2.55.tar.gz configure* [dangermouse self_installed] cat .autom4te.cfg ## ------------------ ## ## User Preferences. ## ## ------------------ ## begin-language: "Autoconf" args: --no-cache end-language: "Autoconf" [dangermouse self_installed] autoconf-2.55/bin/autoconf [dangermouse self_installed] ls -ACF autoconf-2.53/ autom4te.cache/ configure* autoconf-2.53.tar.gz .autom4te.cfg configure.ac autoconf-2.55/ automake-1.6/ libtool-1.4.2/ autoconf-2.55.tar.gz automake-1.6.tar.gz libtool-1.4.2.tar.gz >From the documentation: Customizing `autom4te' ---------------------- One can customize `autom4te' via `~/.autom4te.cfg' (i.e., as found in the user home directory), and `./.autom4te.cfg' (i.e., as found in the directory from which `autom4te' is run). The order is first reading `autom4te.cfg', then `~/.autom4te.cfg', then `./.autom4te.cfg', and finally the command line arguments. In these text files, comments are introduced with `#', and empty lines are ignored. Customization is performed on a per-language basis, wrapped in between a `begin-language: "LANGUAGE"', `end-language: "LANGUAGE"' pair. Customizing a language stands for appending options (*note autom4te Invocation::) to the current definition of the language. Options, and more generally arguments, are introduced by `args: ARGUMENTS'. You may use the traditional shell syntax to quote the ARGUMENTS. As an example, to disable Autoconf caches (`autom4te.cache') globally, include the following lines in `~/.autom4te.cfg': ## ------------------ ## ## User Preferences. ## ## ------------------ ## begin-language: "Autoconf" args: --no-cache end-language: "Autoconf" So, why does it still create that annoying autom4te.cache file? -- || Bill Wendling "Real Programmers have a Snoopy Calendar || [EMAIL PROTECTED] of '69 hanging on their wall" || Coding Simian -- Toon Moene
