2012/10/31 Darrell Anderson <humanreadable@...>:
>
> I'm not an automake guru, but my first thought was what version of automake are you using?
>
> Then I thought this probably is an irrelevant question. :) All of the cmake and admin directories in each module are clones from respective masters in the upstream GIT repository. Patching any of those files means patching only the master copy. Local copies of the repo will not keep the links to the master directories, at least that does not happen on my system. There is a script that is run at the upstream servers to keep everything in sync. In summary this means if one build fails then others are likely to fail too because the base files are all clones.
>
> A key file in this explanation is admin/cvs.sh:58:
>
> case $AUTOMAKE_STRING in
>   automake*1.6.* | automake*1.7* | automake*1.8* | automake*1.9* | automake*1.10* | automake*1.11* | automake*1.12*)
>
> To my knowledge that covers all expected versions of automake. Hence my statement that the question probably is irrelevant. :)
>
> Darrell
I've got:
app-shells/bash:          4.2_p37
dev-lang/python:          2.7.3-r2, 3.2.3
dev-util/cmake:           2.8.9
dev-util/pkgconfig:       0.27.1
sys-devel/autoconf:       2.13, 2.68
sys-devel/automake:       1.9.6-r3, 1.11.6
sys-devel/binutils:       2.22-r1
sys-devel/gcc:            4.6.3
sys-devel/libtool:        2.4-r1
sys-devel/make:           3.82-r3
sys-kernel/linux-headers: 3.4-r2 (virtual/os-headers)
sys-libs/glibc:           2.15-r3

I feel I'm totally lame in autotools...