For some reason eaclocal() from autotools.eclass parses ACLOCAL_AMFLAGS from selected files and adds them as arguments to the aclocal call (thus breaking standard autotools behavior?). This may crash emerge if the flags contain unexpanded macros, though a manual aclocal will run fine. For this problem in the wild see e.g. bug 222303. Reproducible: Always
Created attachment 157977 [details, diff] patch against /usr/portage/eclass/autotools.eclass Strip macros from arguments to aclocal call. I do not really understand the intention of giving extra arguments to the aclocal call, but this patch fixes the problem I was facing. Still, why is eaclocal behaving different than aclocal? Cheers, Benjamin
ACLOCAL_AMFLAGS cannot have configure-expanded values in it. if it does, that package is broken. fix the package. running standard autotools too will break, so that is not a valid argument.