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.

link|improve this question

64% accept rate
Duplicate: serverfault.com/questions/122562/… – Warner Jul 8 '10 at 21:51
feedback

3 Answers

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

link|improve this answer
feedback

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.

link|improve this answer
feedback

You could start running gentoo ;)

link|improve this answer
And how, pray tell, would that help? – David Wolever Jul 8 '10 at 21:45
Of course this isn't really what you want, but you can globally define certain flags with portage: gentoo-portage.com/USE – andyortlieb Jul 12 '10 at 17:41
feedback

Your Answer

 
or
required, but never shown

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