On Friday 23 June 2006 11:50, Frank Cusack wrote:
On June 23, 2006 11:22:21 AM -0400 Alan DeKok <aland@nitros9.org> wrote:
Also, I'm seeing it trying to cache to /dev/null. Is that intentional?
No. I'll look into this.
From autoconf 2.59 documentation: By default, `configure' uses no cache file (technically, it uses `--cache-file=/dev/null'), to avoid problems caused by accidental use of stale cache files. To enable caching, `configure' accepts `--config-cache' (or `-C') to cache results in the file `config.cache'. Alternatively, `--cache-file=FILE' specifies that FILE be the cache file. The cache file is created if it does not exist already. When `configure' calls `configure' scripts in subdirectories, it uses the `--cache-file' argument so that they share the same cache. Kevin Bonner