[Python-Dev] pyconfig.h not regenerated by "config.status --recheck"

[Sjoerd Mullender]

On Tue, May 6 2003 Skip Montanaro wrote:

> 
>     >> This generated pyconfig.h.  It would thus appear that config.status
>     >> shouldn't be used by developers.  Apparently one of the other flags
>     >> it appends to the generated configure command suppresses generation
>     >> of pyconfig.h (and maybe other files).
> 
>     Martin> Can you find out whether this is related to the fact that you
>     Martin> are building in a separate build directory?
> 
> I just confirmed that it's not related to the separate build directory.
> When you run config.status --recheck it reruns your latest configure command
> with the extra flags --no-create and --no-recursion.  Without rummaging
> around in the configure file my guess is the --no-create flag is the
> culprit.  
> 
> So, a word to the wise: avoid config.status --recheck.

I don't agree.  Just run ./config.status without arguments after running
./config.status --recheck.  That *will* regenerate all files.

-- Sjoerd Mullender <sjoerd@acm.org>