Sam Varshavchik <[EMAIL PROTECTED]> writes: > William Hue writes: > >> I don't know about the latest version, but older versions of Courier's >> configure default cache_file to ./config.cache in the top-level directory. >> configure scripts in the subdirectories get passed --cache-file with a >> relative path (e.g. --cache-file=.././config.cache) and do load the cache >> properly. Perhaps the cache-file processing in the latest release's >> configure scripts is broken? > > No. Cache file processing is turned off by default in the current > version of autoconf. The reason given: > > 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. > > Investigating what needs to be done to work around this.
Well, after seeing the positive effects of using --cache-file, I now do this: I run "configure" from within a script. The first thing that the script does is to do a '/bin/rm -f' on the cache file. Then, I invoke "configure" with the appropriate "--cache-file" parameter. This ensures that I won't be bitten by stale cache files, and it also speeds up the configure by a factor of 2.5-3.5. Perhaps a "build" script that does this would be in order ... or at very least, some written instructions in the INSTALL file that explain the use of "--cache-file" and the desirablitity of removing the previous cache file before re-running "configure". -- Lloyd Zusman [EMAIL PROTECTED] God bless you. ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
