Similar to bug 392047, this emerge fails with the following error: /var/tmp/portage/dev-libs/libevent-2.0.16/temp/environment: line 379: pushd: /var/tmp/portage/dev-libs/libevent-2.0.16/work/libevent-2.0.16_build: No such file or directory Reproducible: Always Steps to Reproduce: 1. emerge =dev-libs/libevent-2.0.16 Actual Results: emerge fails Like the other bug, setting AUTOTOOLS_IN_SOURCE_BUILD=1 in the environment or in the ebuild makes it set the right AUTOTOOLS_BUILD_DIR and the build succeeds.
Created attachment 293909 [details] full build.log
Strangely I traced this out-of-nowhere failure to a recent change in autotools-utils.eclass, revision 1.25 (of autotools-utils.eclass) builds libevent fine bug 1.26 does not. It looks like the change just adds "|| die" to a few of the pushd lines, not sure why this would break what was building before.
*** Bug 392055 has been marked as a duplicate of this bug. ***
(In reply to comment #2) > Strangely I traced this out-of-nowhere failure to a recent change in > autotools-utils.eclass, revision 1.25 (of autotools-utils.eclass) builds > libevent fine bug 1.26 does not. It looks like the change just adds "|| die" to > a few of the pushd lines, not sure why this would break what was building > before. It's because the ebuild used the eclass incorrectly from the beginning and maintainer ignored warnings. I'll apply a correct patch in a short while.
Created attachment 293915 [details, diff] dev-libs/libevent: Fix invalid use of autotools-utils. Fixes: https://bugs.gentoo.org/show_bug.cgi?id=392053 (Portage version: 2.2.0_alpha77/git/Linux x86_64, signed Manifest commit with key 42B9401D)
This fixed it! Thanks!
Comment on attachment 293915 [details, diff] dev-libs/libevent: Fix invalid use of autotools-utils. Thanks for the idea, but the patch needlessly complicates the ebuild. I'd rather just remove the .la files.
Fixed in all dev-libs/libevent-2*. Thanks for reporting. And thanks for explaining to me how to not use autotools-utils.eclass. The ride was fun at the time.
