All versions keyworded for ~amd64 that I tested exhibited this failure. The newer ones appear to have the same problem as the earlier ones, but they mask the real error and replace it with a "helpful" fallback error, assuming that if it can't load from ".", then "you might be in the wrong directory". But alas, that's wrong. See the tracker bug for more details. >>> Configuring source in /var/tmp/portage/dev-util/makepp-2.0.98.4/work/makepp-2.0.98.4 ... Please call this script in the directory where you unpacked it! * ERROR: dev-util/makepp-2.0.98.4::gentoo failed (configure phase): * configure failed * >>> Preparing source in /var/tmp/portage/dev-util/makepp-2.0-r1/work/makepp-2.0 ... * Applying makepp-2.0-destdir.patch ... [ ok ] >>> Source prepared. >>> Configuring source in /var/tmp/portage/dev-util/makepp-2.0-r1/work/makepp-2.0 ... Can't locate Mpp/Text.pm in @INC (you may need to install the Mpp::Text module) (@INC contains: /etc/perl /usr/local/lib64/perl5/5.26.0/x86_64-linux /usr/local/lib64/perl5/5.26.0 /usr/lib64/perl5/vendor_perl/5.26.0/x86_64-linux /usr/lib64/perl5/vendor_perl/5.26.0 /usr/local/li b64/perl5 /usr/lib64/perl5/vendor_perl/5.26.0-RC1 /usr/lib64/perl5/vendor_perl/5.25.12 /usr/lib64/perl5/vendor_perl/5.25.11 /usr/lib64/perl5/vendor_perl/5.22.3 /usr/lib64/perl5/vendor_perl /usr/lib64/perl5/5.26.0/x86_64-linux /usr/lib64/perl5/5.26.0) at config.pl line 10. BEGIN failed--compilation aborted at config.pl line 10. * ERROR: dev-util/makepp-2.0-r1::gentoo failed (configure phase): * configure failed
commit 2bc04d0dcb682283477b9a98ea2150f495b8e253 (HEAD -> master, origin/master, origin/HEAD) Author: Andreas K. Hüttel <dilfridge@gentoo.org> Date: Sat Jul 8 21:44:13 2017 +0200 dev-util/makepp: Add build fix for Perl 5.26, bug 623454 Package-Manager: Portage-2.3.6, Repoman-2.3.2 dev-util/makepp/files/makepp-2.0.98.5-perl526.patch | 24 ++++++++++++++++++++++++ dev-util/makepp/makepp-2.0.98.5-r1.ebuild | 44 ++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 68 insertions(+)
A newer version will need to be stabilized on alpha I guess... as its stable version is far older
or maybe alpha version being moved to testing as nothing seems to need it
Bug is fixed in ~arch, only stabilization needs to be done (bug 671682)