Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionJaroslav Škarvada
2020-05-14 08:52:03 UTC
+++ This bug was initially created as a clone of Bug #1826935 +++
Description of problem:
PowerTOP recently (in v2.12) switched to autoconf-archive and it is not possible to build it now.
Version-Release number of selected component (if applicable):
autoconf-archive-2019.01.06-4.fc31.noarch
How reproducible:
Always
Steps to Reproduce:
1. dnf install automake libtool gettext-devel autoconf-archive
2. autoreconf -fi
3.
Actual results:
aclocal: installing 'm4/pkg.m4' from '/usr/share/aclocal/pkg.m4'
aclocal: installing 'm4/ax_require_defined.m4' from '/usr/share/aclocal/ax_require_defined.m4'
aclocal: error: too many loops
aclocal: Please contact <bug-automake>.
at /usr/share/automake-1.16/Automake/Channels.pm line 662.
Automake::Channels::msg("automake", "", "too many loops") called at /usr/share/automake-1.16/Automake/ChannelDefs.pm line 212
Automake::ChannelDefs::prog_error("too many loops") called at /usr/bin/aclocal line 1195
autoreconf: aclocal failed with exit status: 255
Expected results:
No too many loops error
Additional info:
Very strange that running the autoreconf twice workarounds the problem, i.e.:
autoreconf -fi || autoreconf -fi
It could be also problem in the autotools or the configure.ac.
--- Additional comment from Jaroslav Škarvada on 2020-04-22 21:49:43 CEST ---
Just dropping the
AX_ADD_FORTIFY_SOURCE
AX_PTHREAD
from the configure.ac and uninstalling the autoconf-archive, no "too many loops" error is reproduced. Then after reinstalling the autoconf-archive the error is reproduced again even without the AX_ macros.
--- Additional comment from Jaroslav Škarvada on 2020-04-22 21:55:59 CEST ---
Also reproducible in the rawhide.
In the rawhide:
automake-1.16.1-14.fc32.noarch
gettext-devel-0.20.2-1.fc33.x86_64
libtool-2.4.6-33.fc32.x86_64
autoconf-archive-2019.01.06-5.fc32.noarch
Comment 1Jaroslav Škarvada
2020-05-14 08:53:50 UTC
When rebuilding PowerTOP it's causing build errors (which we workaround in the spec), but it triggers rpmdiff errors we have to waive.
As I explained in bug 1826935, this is not a bug in autoconf-archive per se, but in the internal limits of aclocal. It is possible to work around that limit that by using AX_REQUIRED_DEFINED. I have submitted a pull request to powertop upstream to do that: https://github.com/fenrus75/powertop/pull/82