Sorry about my bad English. Here's the question:
Is there a way to resume ./configure script from where it stopped just after fixing a dependency requirement?
It seems that the script runs for a long time just until it throws me another unsatisfied dependency... After I fix it, the ./configure script starts running from zero again.
This would sure save me a few minutes every time I compile a package which I don't have easy access to its dependencies.
Does this resuming depend on the publisher providing caching for its configure script, or is there something I can do about that?
Any ideas? Thank you.