Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

How to optimize restarting of ./configure script when it fails?

E.g. start ./configure to figure out missing dependency; start it again to figure out the next missing dependency and so on. If we have N missing dependencies, we have to wait for about N*(const+N/2) tests totally before we successfully configure it.

"./configure -C" fails, and "config.cache" is empty.

ccache is already in use. ./configure is executed by /bin/dash.

How to either

  1. Force it to cache partial results?
  2. Make it continue on failure and report all missing things at once?
  3. Dramatically speed up re-running the same tests somehow.

Are there alternative ./configure script generators? May be I should hack something inside ./configure to enable caching or not exiting?

P.S. I wish ./configure just prints the list of Debian lib*-dev packages I need to install in order to satisfy it.

share|improve this question
What package is so broken that config.cache isn't generated? –  Ignacio Vazquez-Abrams Oct 20 '10 at 17:58
And what about systems that don't run Debian? Or what about when a package name changes? Or... –  Ignacio Vazquez-Abrams Oct 20 '10 at 17:58
@Ignacio Vazquez-Abrams, I mean it would be most comfortable for me. –  Vi. Oct 20 '10 at 18:14

1 Answer 1

You can use auto-apt to automatically install all the files configure is trying to detect.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.