| Bug #50446 | MySQL Proxy requires automake-1.10 but finds and defaults to -1.9 if it's there | ||
|---|---|---|---|
| Submitted: | 19 Jan 2010 15:37 | Modified: | 9 Jan 2015 10:34 |
| Reporter: | MC Brown | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Proxy: Install/Config | Severity: | S3 (Non-critical) |
| Version: | OS: | Any | |
| Assigned to: | Jan Kneschke | CPU Architecture: | Any |
[2 Feb 2010 17:43]
Enterprise Tools JIRA Robot
Jan Kneschke writes: revno: 959 committer: jan@mysql.com branch nick: trunk timestamp: Thu 2010-01-21 13:56:52 +0100 message: replaced automake-1.9 by -1.10 and likewise for autoconf (fixes #50446)
Description: When running autogen.sh on a machine with both automake-1.9 and automake-1.10 on it, the build defaults to using the automake-1.9 executable if it exists. This is wrong, since mysql-proxy now needs 1.10 to build (through the use of abs_top_builddir). How to repeat: Download mysql-proxy from bzr and then run autogen.sh on a machine with automake-1.9 installed. Suggested fix: The issue is in autogen.sh, which explicitly looks for automake-19 and automake-1.9 in preference to automake. We should change: if test x$AUTOMAKE = x; then if test \! "x`which automake-1.9 2> /dev/null | grep -v '^no'`" = x; then AUTOMAKE=automake-1.9 elif test \! "x`which automake19 2> /dev/null | grep -v '^no'`" = x; then AUTOMAKE=automake19 elif test \! "x`which automake 2> /dev/null | grep -v '^no'`" = x; then AUTOMAKE=automake else echo "automake 1.9.x wasn't found, exiting"; exit 0 fi fi And the corresponding issue under aclocal, to use the 1.10 version