Rebuilding autotools through maintainer-mode is _not_ good, because it usually means you forget to add dependencies, and they'll magically use the same version as used by upstream, which might not be what the user have installed at all.
If you patch Makefile.am or configure.in/configure.ac you _have to_ use autotools.eclass and eautomake/eautoreconf. Exceptions are granted _only_ for system packages that would make it impossible to run autotools during stagebuilding.
Please fix your package.
Created attachment 157863 [details]
build.log for app-text/gv-3.6.4
Diego, I've bumped app-text/gv to 3.6.4 and changed it to modify only Makefile.am instead of also Makefile.in, then inherited autotools and ran eautoreconf. Why am I still getting..
>>> Completed installing gv-3.6.4 into /var/tmp/portage/app-text/gv-3.6.4/image/
* QA Notice: Automake "maintainer mode" detected:
* if (/bin/sh /var/tmp/portage/app-text/gv-3.6.4/work/gv-3.6.4/missing --run makeinfo --version) >/dev/null 2>&1; then \
* if /bin/sh /var/tmp/portage/app-text/gv-3.6.4/work/gv-3.6.4/missing --run makeinfo -I . \
* If you patch Makefile.am, configure.in, or configure.ac then you
* should use autotools.eclass and eautomake or eautoreconf. Exceptions
* are limited to system packages for which it is impossible to run
* autotools during stage building. See
* http://www.gentoo.org/proj/en/qa/autofailure.xml for more information.
strip: x86_64-pc-linux-gnu-strip --strip-unneeded -R .comment
The problem disappeared with 3.7.1. Please reopen if you can still reproduce.