Your package fails to build with the newest autoconf-2.71, which was part of a recent wide Fedora change. More information about Fedora autoconf Change available here: https://fedoraproject.org/wiki/Changes/Autoconf_271#How_To_Test. The easiest way to reproduce the problem is to execute a fedora scratch-build on your package. Thank you for cooperation!
The problem was with glibc-2.34 (malloc_hook changes to be exact) rather than autoconf-2.71. But, as this library's replacement, memkind, is not only vastly more powerful, but also as of version 1.12 has reached feature parity with what vmem did, there's no point spending developer tuits in fixing vmem. Let's retire it. On the other hand, vmem is still working well in releases of Fedora and Red Hat that have glibc ≤ 2.33.