Bug #19349 Using DIST_COMMON break maintainer build using automake 1.7.9

• Submitted: 25 Apr 2006 18:59
• Modified: 4 Sep 2007 10:47
• Reporter: Kent Boortz
• Status: Won't fix
• Category: MySQL Server: Compiling
• Severity: S3 (Non-critical)
• Version: 5.1-bk
• OS: Linux (Linux)
• Assigned to: Kent Boortz
• CPU Architecture: Any

[25 Apr 2006 18:59] Kent Boortz

Description:
[16:41] ingo: automake: DIST_COMMON was set with `HASH(0x85a22c8)=' and is now 
A "maintainer" build using automake 1.7.9 breaks with

 automake: DIST_COMMON was set with `HASH(0x85a22c8)=' and is now set with `+='
 ++++ die 'Can'\''t execute automake'

Upgrading to automake 1.9 solved the problem in this case.

How to repeat:
Build 5.1.10 from BitKeeper with automake 1.7.9.

Suggested fix:
Find a way to express this without DIST_COMMON that is a non
documented make variable.

[4 Sep 2007 10:47] Kent Boortz

Can't find a clean solution to this. I think the explicit
DIST_COMMON is used to exclude "storage/ndb/config/common.mk.am"
from it that otherwise would have automatically been added
by automake. And the exclusion is to avoid a potential
race when two parallel make runs try copy the same include
file.

But I close this bug report anyway, as the manual states
the minimum automake version is 1.8.1 for MySQL 5.1.