Bug #41381 | 5.1.30 build depends on automake 1.10 and autoconf 2.60 | ||
---|---|---|---|
Submitted: | 10 Dec 2008 23:34 | Modified: | 11 Dec 2008 20:20 |
Reporter: | Mark Callaghan | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Compiling | Severity: | S3 (Non-critical) |
Version: | 5.1.30 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | autoconf, automake, build |
[10 Dec 2008 23:34]
Mark Callaghan
[10 Dec 2008 23:47]
Kent Boortz
If you didn't modify any autoconf input files or Makefile.am, this is definitely a bug. Normal users just compiling from source should not be hit by this problem. For developers that modify the source the requirement of very new versions of GNU auto tools is an inconvenience and should definitely be correctly documented and also be coded into the specification files as requirement. While good portability to a wide range of GNU autotools versions is good, it is not a strong requirement. Independently of the "aclocal.m4" you would have hit problems if the "missing" script would try call the specific version of automake/autoconf used during the build of the source TAR.
[10 Dec 2008 23:50]
Mark Callaghan
My source control system doesn't preserve timestamps, so the auto* tools think they need to run. Normal users who build from the official tar files won't have this problem. The fix might be limited to updating the docs with the new minimum versions for these tools. But was this change needed?
[11 Dec 2008 6:21]
Sveta Smirnova
Thank you for the report. Verified as described. To repeat in usual environment: ./configure touch aclocal.m4 make
[11 Dec 2008 20:20]
Omer Barnir
To build, you should either use our generated files (configure) or you should generate all files (run aclocal yourself, which will generate an aclocal.m4). Generating half the files, but relying on others, isn't something we should support. Regardless, there is a workarownd of touch -t OLD_DATE_STAMP aclocal.m4