Hi Boris,
if I get it right, these errors only appears when the maintainer mode is
active (btw, what does this mode add to the build log?). Could we force
a reconf when the mode is enabled? I fear that requiring automake to be
installed on a system could cause headaches (at least to me) when
testing the build on systems that don't have the full GNU stack installed.
Alberto
Boris Kolpackov wrote:
Hi Alberto,
Alberto Massari <[EMAIL PROTECTED]> writes:
there used to be problems with automake older than a certain version,
and having the preprocessed files helped working on the code even if the
developer didn't have that specific version (clearly, if he was not
touching the makefiles).
So, by removing the preprocessed files, we are putting even more
constraints on the developer's toolset (have automake, and have it
updated). What kind of errors do you find when using a different version
of automake?
They were some criptic automake errors that were gone once I
regenerated configure, etc., by running the reconf script.
They were caused by the version mispatch and the maintainers
mode option.
I think it is better to require a developer to have reasonable
autotools version than to have the build process fail with some
cryptic error message (no, it does not say "Hey, update your
autotools and run reconf!" ;-)) and let the developer wonder
what to do next.
Plus it is a fairly common practice not to keep autotools-generated
scripts in the repository, so I don't think it will surprise anybody.
Boris
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
