When one inherits autotools with WANT_AUTOMAKE="none", a package sys-devel/automake not placed in DEPEND. But an utility aclocal from sys-devel/automake is always called, even with WANT_AUTOMAKE="none": eautoreconf->eaclocal->autotools_run_tool->aclocal. A build fails if aclocal is not founded. Please, or place sys-devel/automake in DEPEND in this case, or don't run aclocal always when WANT_AUTOMAKE is "none".
eaclocal is only run if the package is using it already, and if the package is using automake already, you shouldn't be disabling the depend by setting it to "none"
(In reply to comment #1) > eaclocal is only run if the package is using it already, and if the package > is using automake already, you shouldn't be disabling the depend by setting > it to "none" As far as I can see, eautoreconf calls eaclocal unconditionally. Does this imply that eautoreconf can't/shouldn't be used with WANT_AUTOMAKE="none"?
The related bug: https://bugs.gentoo.org/show_bug.cgi?id=401505
i misread the logic at the top of eaclocal() will probably have to update that func to skip `aclocal` if the dep is disabled
*** Bug 401505 has been marked as a duplicate of this bug. ***
autoreconf itself unconditionally executes aclocal. i'm not sure the few packages that can get by w/out running aclocal are worth supporting this workflow. it's very hard to know if other m4 files are available that will need to be gathered up by aclocal so that autoconf will have them available. in short, i think i'll change the eclass to always depend on automake.
the eclass now always depends on automake http://sources.gentoo.org/eclass/autotools.eclass?r1=1.132&r2=1.133
