Martin Buchholz <martin(a)xemacs.org> writes:
SJ> In general I agree, but it's really a PITA when it takes
~1h to run
SJ> configure and you only wanted to make a minor change (so you edited
SJ> config.cache to make it redo that test). Also, developing
SJ> configure.in stuff (as I've been doing a couple of times with xemacs
SJ> for the past days) is slowed down.
One HOUR???
The worst I've seen is 5 minutes or so. Seems like there's a serious
performance problem with your system. How long does compiling xemacs take?
This was on a HURD system, many moons ago. The performance of HURD
was very poor, and I tried to get it through XEmacs' configure. I
never got as far as to actually compiling it though (too many broken
things in the OS). Config.cache was useful getting a number of
projects through. I admit this isn't within the 95 % of common usage,
but just to show that there are situations were it's nice.
Also, when hacking configure.in, you have to THINK REALLY HARD,
because you have to get it right the first time, because the code has
to work on many different machines. If you're having an
edit-compile-debug cycle, you're code probably isn't going to work
anyways. Use your brain, not the computer, to find the bugs.
Gotta try that sometime. :-)