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
This doesn't look like fail because autoconf, but because of recent change in glibc. It's already discussed at m4 upstream mailing list and also at [1]. [1] https://sourceware.org/bugzilla/show_bug.cgi?id=20305
Gentle ping.
There’s no obvious interest upstream, so maybe this should be reassigned to glibc or another bug should be created there for extra eyes.
There is currently no plan to revert the glibc change. m4 has to be fixed. Thanks.
(In reply to Ernestas from comment #3) > There’s no obvious interest upstream, so maybe this should be reassigned to > glibc or another bug should be created there for extra eyes. Upstream has released 1.4.18b that fixes this issue (inherits the fix from gnulib). I've created COPR repo with that release: https://copr.fedorainfracloud.org/coprs/vcrhonek/m4-test/ Stable 1.4.19 is going to be released later this month.