Mike Bushroe <[email protected]> skribis: > But ignoring my fumbling around in the dark my original request was to > re-consider the order of tests made once the configure file it built. > Currently many of the long and arduous dependency installs are not > checked until near the end, about 10 minutes down the line on my > laptop. This means that for every one of the listed major dependencies > that I didn't install, didn't get to correctly install, or got a > version too far back, it would add another 10 minute ./configure run > just to tell me what major package to work on loading next. Then > another 10 minute run to go one line further to report the next > missing piece. So on top of the time it took to install the next piece > I was adding the 10 minute run of guile's configure for each attempt.
I think you should use configure’s caching mechanism: just run ./configure -C and then, when it fails, it already has a cache of most of what it tested already, so the next run will quickly resume close to where it stopped. HTH, Ludo’.
