Re: run configure on different machines

[Guido Draheim]

Am 25.07.2013 14:17, schrieb A.P. Horst:
> Hello,
>
> for several projects we use autoconf for configuration and checking. Now a 
> colleague of mine checked out one of these projects, tried to configure it 
> (seemingly succeeded), but the build failed. It turns out that config.h 
> generated by configure is
> full of #undef [something]. Nothing is defined, not even PACKAGE. In fact, 
> there is also an #undef PACKAGE.
> How can this be? Isn't configure supposed to work across machines?
> The problem got solved by him running autoreconf -i. But I do not think this is 
> how it is supposed to be.

There can be multiple possible reasons for that behviour.
First of all, I am wondering whether you have committed
the config.h file to the version control repository - if
so then delete it and add it to the ignore-files list.

Also state the automake-version as some version have tried
to be very minimalistic about recompiling when unnecessary.
Since some version control systems will have an interesting
handling of file mtime it might turn out that the makefile
rules were setup so that it thought there is no need to
regenerate the config.h - please check the mtimes of the
files that you would expect to get configure-generated.

cheers, Guido