Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Is there any "conventional" way to save options passed to a ./configure script?

On the rare occasion that I need to build something from source, I generally need to pass it non-standard configure options (eg, --prefix=..., --with-foo=..., etc)… Then when I eventually need to re-build it, I've forgotten all the options I originally used.

Currently I use something like this:

$ mv configure{,.real}
$ echo "./configure.real --prefix=... --with-foo=..." > ./configure
$ chmod +x ./configure

But that feels… Less then ideal.

share|improve this question
Duplicate:… – Warner Jul 8 '10 at 21:51
up vote 3 down vote accepted

As well as config.log, most configure scripts will create a config.status script which will be executable, and when you run it will do the configure with the same options you did originally.

You should be able to just do ./config.status

share|improve this answer

After ./configure you normally have a config.log file containing the ./configure command (including option) as well as the software name. I use to keep this one.

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.