aclocal 'too many loops' has been
popping up sporadically for a week or two now. Possibly 7.5
related.
I suspect that there is a build order and/or race condition
element to this. It often goes away if you just run build-pkgs a
second time.
The second possible element is that build-pkgs is using flags that
preserve the mock environment between packages. The goal was to
avoid reinstalling required packages that are often common across
the packages we build. It was a build time speedup that has been
in use for 2-3 years now without incident.
Google shows that other folks have hit 'aclocal too many loops' as
well, and there are suggestions that it might be fixed in a recent
update to automake. Scanning the changelog for the latest and
greatest from gnu.org doesn't show any obvious fixes addressing
this issue.
Scott
On 18-09-26 11:32 AM, Cordoba Malibran, Erich wrote:
BUILDSTDERR: aclocal: error: too many loops
BUILDSTDERR: aclocal: Please contact <bug-automake@gnu.org>.
BUILDSTDERR: at /usr/share/automake-1.13/Automake/Channels.pm line 662.
BUILDSTDERR: Automake::Channels::msg('automake', '', 'too many loops') called at /usr/share/automake-1.13/Automake/ChannelDefs.pm line 212
BUILDSTDERR: Automake::ChannelDefs::prog_error('too many loops') called at /usr/bin/aclocal line 1187
BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c (%build)
BUILDSTDERR: Macro expanded in comment on line 214: %global _libexecdir %{_exec_prefix}/lib
BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c (%build)