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?
Lloyd Zusman wrote:
Scott Taylor <[EMAIL PROTECTED]> writes:
On Sat, 2005-02-05 at 21:28 -0500, Lloyd Zusman wrote:
I'm not sure, but I seem to remember seeing other autoconf-based systems cache all that stuff for the sub-components. I'll see if I can find an example.
./configure --cache-file=/tmp/courier.cache
Well, that made a huge difference: 105 minutes to run the latest Courier "configure", as compared to 4-5 hours for when I did it without the "--cache-file" parameter.
Thank you!
To Sam: could that parameter be made the default in future Courier releases?
------------------------------------------------------- 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
