On 2013-11-22 14:34, Dave Pointon wrote:
I don't know if it's of any help, but I've noticed that configure sometimes needs to be run twice before the additional/new/modified option(s) take effect - quite frequently, the first time is merely a re-run of the previously generated generated-configure.sh.
That sounds weird. I've never seen that behavior, and I can't really imagine how that could happen. Do you have any debug information about that?
What definitely *could* (and typically will) happen is that files are not re-compiled with new options due to a new configuration. But that is not helped by running configure again, but by running "make clean".
And if you really want to be on the safe side, it's probably a good idea to do "make dist-clean" before re-running configure. This will delete everything, including the old configuration.
/Magnus
