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.
(In reply to Ondrej Dubaj from comment #1) > Gentle ping. Sry that I didn't immediately come back to you. The issues comes from a couple of ... foo() prototypes instead of ... foo(void). I'm a bit surprised that autoconf adds this additional moaning ... but maybe just compiler flag defaults changing slightly. Anyway the issue is cleaned up with upstream/master and we are about to start an upstream release-cycle within the next 2 weeks. To make giving feedback on the release-candidates easier we usually are doing a fedora-release with each of the release-candidates. Thus question is if you would be fine with a release that is compatible to autoconf-271 within the next 2 weeks. If not I've just created a quick patch we could put on top of the current fedora release that I've just successfully tested building against your copr-repo. Regards Klaus
Release in two weeks is no problem for us, we are aiming autoconf-2.71 for f36, so we have plenty of time till then. Thanks for the clarification!