Simon Peyton-Jones <[EMAIL PROTECTED]> wrote,
> | > Some parts of the configuration mechanism changed. Did you invoke
> | > autoheader and autoconf before configure?
> | I didn't either, I didn't even know about autoheader though I
> | suppose I should
[...]
> It's hard to specify exactly when its necessary to re-run autoconf.
A good heuristic is to re-run `autoconf' whenever any of the
`configure.in' files or `aclocal.m4' changes during a cvs
update and to re-run `fptools/configure' whenever any of the
.in files changes.
In fact, it is better to use `autoreconf' instead of
`autoconf', because the former handles all `configure.in's
in the source tree (otherwise, you have to call `autoconf'
manually in each directory where the `configure.in' changed)
and it also takes care of running `autoheader' where
necessary.
Manuel
