Your package fails to build with the newest upcoming autoconf-2.71, which is part of a wide Fedora change. Please see the attached copr: https://copr.fedorainfracloud.org/coprs/odubaj/autoconf-2.70/packages/. More information about testing your package when building with autoconf available here: https://fedoraproject.org/wiki/Changes/Autoconf_271#How_To_Test
Gentle ping.
Hello, this issue does not seem to be resolved, can you please check it one more time ? Soonly we are planning to move to autoconf-2.71, so there will be FTBFS on this component. Thank you.
I've "fixed" the problem by removing the 'BuildRequires: autoconf'. Upstream gdb and related projects currently use autoconf 2.69. Changing to another version of autoconf will require agreement from a number of upstream maintainers, not just for gdb, but for other projects (binutils, gcc, and perhaps others) too. I found that the 'BuildRequires: autoconf' line was added to gdb.spec a little over a year ago while attempting to make gdb work when compiled with -flto. In the course of making that change, some of the m4 files had been patched requiring autoconf to be run to bring in the changes to the configure files. However, since then, we disabled LTO and also removed inclusion of the patch which modified the m4 files. We did, however, still have some cruft in gdb.spec which invoked autoconf; I checked and found that this change came in as a result of the LTO work by Jeff Law. I've removed those lines, so that autoconf is no longer invoked when performing a build. These changes are in gdb-10.2-5.fc35. I've tested using the copr mentioned in the Description for this bug and found that the gdb package now builds in the mock environment. (I also tested prior to making those changes and found that it did not build using gdb-10.2-4.fc35.) I'm closing this bug, but please reopen it if you have problems.