perl: error while loading shared libraries: libperl.so.5.36: cannot open shared object file: No such file or directory * Removing old .ph files >>> dev-lang/perl-5.36.0-r2 merged. >>> Emerging (38 of 94) virtual/perl-Data-Dumper-2.184.0::gentoo >>> Unpacking source... >>> Source unpacked in /home/vm/gentoo/tmp/var/tmp/portage/virtual/perl-Data-Dumper-2.184.0/work >>> Preparing source in /home/vm/gentoo/tmp/var/tmp/portage/virtual/perl-Data-Dumper-2.184.0/work ... >>> Source prepared. >>> Configuring source in /home/vm/gentoo/tmp/var/tmp/portage/virtual/perl-Data-Dumper-2.184.0/work ... >>> Source configured. >>> Compiling source in /home/vm/gentoo/tmp/var/tmp/portage/virtual/perl-Data-Dumper-2.184.0/work ... >>> Source compiled. >>> Test phase [not enabled]: virtual/perl-Data-Dumper-2.184.0 >>> Install virtual/perl-Data-Dumper-2.184.0 into /home/vm/gentoo/tmp/var/tmp/portage/virtual/perl-Data-Dumper-2.184.0/image >>> Completed installing virtual/perl-Data-Dumper-2.184.0 into /home/vm/gentoo/tmp/var/tmp/portage/virtual/perl-Data-Dumper-2.184.0/image * Final size of build directory: 0 KiB * Final size of installed tree: 0 KiB egrep: warning: egrep is obsolescent; using grep -E egrep: warning: egrep is obsolescent; using grep -E /home/vm/gentoo/var/tmp/portage/._portage_reinstall_.qi5fypxj/bin/estrip: line 38: scanelf: command not found /home/vm/gentoo/var/tmp/portage/._portage_reinstall_.qi5fypxj/bin/estrip: line 356: scanelf: command not found >>> Installing (38 of 94) virtual/perl-Data-Dumper-2.184.0::gentoo * checking 0 files for package collisions >>> Merging virtual/perl-Data-Dumper-2.184.0 to / >>> virtual/perl-Data-Dumper-2.184.0 merged. >>> Emerging (39 of 94) virtual/perl-CPAN-2.330.0::gentoo >>> Unpacking source... >>> Source unpacked in /home/vm/gentoo/tmp/var/tmp/portage/virtual/perl-CPAN-2.330.0/work >>> Preparing source in /home/vm/gentoo/tmp/var/tmp/portage/virtual/perl-CPAN-2.330.0/work ... >>> Source prepared. >>> Configuring source in /home/vm/gentoo/tmp/var/tmp/portage/virtual/perl-CPAN-2.330.0/work ... >>> Source configured. >>> Compiling source in /home/vm/gentoo/tmp/var/tmp/portage/virtual/perl-CPAN-2.330.0/work ... >>> Source compiled. >>> Test phase [not enabled]: virtual/perl-CPAN-2.330.0 >>> Install virtual/perl-CPAN-2.330.0 into /home/vm/gentoo/tmp/var/tmp/portage/virtual/perl-CPAN-2.330.0/image >>> Completed installing virtual/perl-CPAN-2.330.0 into /home/vm/gentoo/tmp/var/tmp/portage/virtual/perl-CPAN-2.330.0/image * Final size of build directory: 0 KiB * Final size of installed tree: 0 KiB egrep: warning: egrep is obsolescent; using grep -E egrep: warning: egrep is obsolescent; using grep -E /home/vm/gentoo/var/tmp/portage/._portage_reinstall_.qi5fypxj/bin/estrip: line 38: scanelf: command not found /home/vm/gentoo/var/tmp/portage/._portage_reinstall_.qi5fypxj/bin/estrip: line 356: scanelf: command not found >>> Installing (39 of 94) virtual/perl-CPAN-2.330.0::gentoo * checking 0 files for package collisions >>> Merging virtual/perl-CPAN-2.330.0 to / >>> virtual/perl-CPAN-2.330.0 merged. >>> Emerging (40 of 94) virtual/perl-Test-Harness-3.440.0::gentoo >>> Unpacking source... >>> Source unpacked in /home/vm/gentoo/tmp/var/tmp/portage/virtual/perl-Test-Harness-3.440.0/work >>> Preparing source in /home/vm/gentoo/tmp/var/tmp/portage/virtual/perl-Test-Harness-3.440.0/work ... >>> Source prepared. >>> Configuring source in /home/vm/gentoo/tmp/var/tmp/portage/virtual/perl-Test-Harness-3.440.0/work ... >>> Source configured. >>> Compiling source in /home/vm/gentoo/tmp/var/tmp/portage/virtual/perl-Test-Harness-3.440.0/work ... >>> Source compiled. >>> Test phase [not enabled]: virtual/perl-Test-Harness-3.440.0 >>> Install virtual/perl-Test-Harness-3.440.0 into /home/vm/gentoo/tmp/var/tmp/portage/virtual/perl-Test-Harness-3.440.0/image >>> Completed installing virtual/perl-Test-Harness-3.440.0 into /home/vm/gentoo/tmp/var/tmp/portage/virtual/perl-Test-Harness-3.440.0/image * Final size of build directory: 0 KiB * Final size of installed tree: 0 KiB egrep: warning: egrep is obsolescent; using grep -E egrep: warning: egrep is obsolescent; using grep -E /home/vm/gentoo/var/tmp/portage/._portage_reinstall_.qi5fypxj/bin/estrip: line 38: scanelf: command not found /home/vm/gentoo/var/tmp/portage/._portage_reinstall_.qi5fypxj/bin/estrip: line 356: scanelf: command not found >>> Installing (40 of 94) virtual/perl-Test-Harness-3.440.0::gentoo * checking 0 files for package collisions >>> Merging virtual/perl-Test-Harness-3.440.0 to / >>> virtual/perl-Test-Harness-3.440.0 merged. >>> Emerging (41 of 94) virtual/perl-Encode-3.170.0::gentoo >>> Unpacking source... >>> Source unpacked in /home/vm/gentoo/tmp/var/tmp/portage/virtual/perl-Encode-3.170.0/work >>> Preparing source in /home/vm/gentoo/tmp/var/tmp/portage/virtual/perl-Encode-3.170.0/work ... >>> Source prepared. >>> Configuring source in /home/vm/gentoo/tmp/var/tmp/portage/virtual/perl-Encode-3.170.0/work ... >>> Source configured. >>> Compiling source in /home/vm/gentoo/tmp/var/tmp/portage/virtual/perl-Encode-3.170.0/work ... >>> Source compiled. >>> Test phase [not enabled]: virtual/perl-Encode-3.170.0 >>> Install virtual/perl-Encode-3.170.0 into /home/vm/gentoo/tmp/var/tmp/portage/virtual/perl-Encode-3.170.0/image >>> Completed installing virtual/perl-Encode-3.170.0 into /home/vm/gentoo/tmp/var/tmp/portage/virtual/perl-Encode-3.170.0/image * Final size of build directory: 0 KiB * Final size of installed tree: 0 KiB egrep: warning: egrep is obsolescent; using grep -E egrep: warning: egrep is obsolescent; using grep -E /home/vm/gentoo/var/tmp/portage/._portage_reinstall_.qi5fypxj/bin/estrip: line 38: scanelf: command not found /home/vm/gentoo/var/tmp/portage/._portage_reinstall_.qi5fypxj/bin/estrip: line 356: scanelf: command not found >>> Installing (41 of 94) virtual/perl-Encode-3.170.0::gentoo * checking 0 files for package collisions >>> Merging virtual/perl-Encode-3.170.0 to / >>> virtual/perl-Encode-3.170.0 merged. >>> Emerging (42 of 94) perl-core/File-Temp-0.231.100::gentoo * File-Temp-0.2311.tar.gz BLAKE2B SHA512 size ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking File-Temp-0.2311.tar.gz to /home/vm/gentoo/tmp/var/tmp/portage/perl-core/File-Temp-0.231.100/work >>> Source unpacked in /home/vm/gentoo/tmp/var/tmp/portage/perl-core/File-Temp-0.231.100/work >>> Preparing source in /home/vm/gentoo/tmp/var/tmp/portage/perl-core/File-Temp-0.231.100/work/File-Temp-0.2311 ... * Applying File-Temp-0.230.0-symlink-safety.patch ... [ ok ] >>> Source prepared. >>> Configuring source in /home/vm/gentoo/tmp/var/tmp/portage/perl-core/File-Temp-0.231.100/work/File-Temp-0.2311 ... perl: error while loading shared libraries: libperl.so.5.36: cannot open shared object file: No such file or directory * Using ExtUtils::MakeMaker * perl Makefile.PL PREFIX=/home/vm/gentoo/tmp/usr INSTALLDIRS=vendor INSTALLMAN3DIR=none DESTDIR=/home/vm/gentoo/tmp/var/tmp/portage/perl-core/File-Temp-0.231.100/image perl: error while loading shared libraries: libperl.so.5.36: cannot open shared object file: No such file or directory * ERROR: perl-core/File-Temp-0.231.100::gentoo failed (configure phase): * Unable to build! * * Call stack: * ebuild.sh, line 127: Called src_configure * environment, line 1131: Called perl-module_src_configure * environment, line 657: Called die * The specific snippet of code: * perl Makefile.PL "$@" <<< "${pm_echovar}" || die "Unable to build!"; * * If you need support, post the output of `emerge --info '=perl-core/File-Temp-0.231.100::gentoo'`, * the complete build log and the output of `emerge -pqv '=perl-core/File-Temp-0.231.100::gentoo'`. * The complete build log is located at '/home/vm/gentoo/tmp/var/tmp/portage/perl-core/File-Temp-0.231.100/temp/build.log'. * The ebuild environment file is located at '/home/vm/gentoo/tmp/var/tmp/portage/perl-core/File-Temp-0.231.100/temp/environment'. * Working directory: '/home/vm/gentoo/tmp/var/tmp/portage/perl-core/File-Temp-0.231.100/work/File-Temp-0.2311' * S: '/home/vm/gentoo/tmp/var/tmp/portage/perl-core/File-Temp-0.231.100/work/File-Temp-0.2311' >>> Failed to emerge perl-core/File-Temp-0.231.100, Log file: >>> '/home/vm/gentoo/tmp/var/tmp/portage/perl-core/File-Temp-0.231.100/temp/build.log' * Messages for package sys-apps/portage-3.0.43-r1: * Unable to find kernel sources at /usr/src/linux * Unable to calculate Linux Kernel version for build, attempting to use running version * Messages for package sys-libs/zlib-1.2.13-r1: * This package will overwrite one or more files that may belong to other * packages (see list below). You can use a command such as `portageq * owners / ` to identify the installed package that owns a * file. If portageq reports that only one package owns a file then do * NOT file a bug report. A bug report is only useful if it identifies at * least two or more packages that are known to install the same file(s). * If a collision occurs and you can not explain where the file came from * then you should simply ignore the collision since there is not enough * information to determine if a real problem exists. Please do NOT file * a bug report at https://bugs.gentoo.org/ unless you report exactly * which two packages install the same file(s). See * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how * to solve the problem. And once again, please do NOT file a bug report * unless you have completely understood the above message. * * Detected file collision(s): * * /home/vm/gentoo/tmp/usr/lib/pkgconfig/zlib.pc * /home/vm/gentoo/tmp/usr/include/zconf.h * /home/vm/gentoo/tmp/usr/include/zlib.h * /home/vm/gentoo/tmp/usr/lib/libz.so * /home/vm/gentoo/tmp/usr/lib/libz.so.1 * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * None of the installed packages claim the file(s). * * Package 'sys-libs/zlib-1.2.13-r1' merged despite file collisions. If * necessary, refer to your elog messages for the whole content of the * above message. * Messages for package dev-lang/python-exec-2.4.10: * This package will overwrite one or more files that may belong to other * packages (see list below). You can use a command such as `portageq * owners / ` to identify the installed package that owns a * file. If portageq reports that only one package owns a file then do * NOT file a bug report. A bug report is only useful if it identifies at * least two or more packages that are known to install the same file(s). * If a collision occurs and you can not explain where the file came from * then you should simply ignore the collision since there is not enough * information to determine if a real problem exists. Please do NOT file * a bug report at https://bugs.gentoo.org/ unless you report exactly * which two packages install the same file(s). See * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how * to solve the problem. And once again, please do NOT file a bug report * unless you have completely understood the above message. * * Detected file collision(s): * * /home/vm/gentoo/tmp/usr/bin/python * /home/vm/gentoo/tmp/usr/bin/python3 * /home/vm/gentoo/tmp/usr/bin/python-config * /home/vm/gentoo/tmp/usr/bin/python3-config * /home/vm/gentoo/tmp/usr/bin/2to3 * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * None of the installed packages claim the file(s). * * Package 'dev-lang/python-exec-2.4.10' merged despite file collisions. * If necessary, refer to your elog messages for the whole content of the * above message. * Messages for package app-alternatives/bzip2-1: * This package will overwrite one or more files that may belong to other * packages (see list below). You can use a command such as `portageq * owners / ` to identify the installed package that owns a * file. If portageq reports that only one package owns a file then do * NOT file a bug report. A bug report is only useful if it identifies at * least two or more packages that are known to install the same file(s). * If a collision occurs and you can not explain where the file came from * then you should simply ignore the collision since there is not enough * information to determine if a real problem exists. Please do NOT file * a bug report at https://bugs.gentoo.org/ unless you report exactly * which two packages install the same file(s). See * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how * to solve the problem. And once again, please do NOT file a bug report * unless you have completely understood the above message. * * Detected file collision(s): * * /home/vm/gentoo/tmp/bin/bzip2 * /home/vm/gentoo/tmp/bin/bunzip2 * /home/vm/gentoo/tmp/bin/bzcat * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * None of the installed packages claim the file(s). * * Package 'app-alternatives/bzip2-1' merged despite file collisions. If * necessary, refer to your elog messages for the whole content of the * above message. * Messages for package sys-apps/util-linux-2.38.1: * chown failure ignored with unprivileged user: * chown root:root ${D}${EPREFIX}/usr/bin/mount * /usr/bin/chown: changing ownership of '${D}${EPREFIX}/usr/bin/mount': Operation not permitted * chown failure ignored with unprivileged user: * chown root:root ${D}${EPREFIX}/usr/bin/umount * /usr/bin/chown: changing ownership of '${D}${EPREFIX}/usr/bin/umount': Operation not permitted * The mesg/wall/write tools have been disabled due to USE=-tty-helpers. * The agetty util now clears the terminal by default. You * might want to add --noclear to your /etc/inittab lines. * Messages for package app-alternatives/tar-0: * This package will overwrite one or more files that may belong to other * packages (see list below). You can use a command such as `portageq * owners / ` to identify the installed package that owns a * file. If portageq reports that only one package owns a file then do * NOT file a bug report. A bug report is only useful if it identifies at * least two or more packages that are known to install the same file(s). * If a collision occurs and you can not explain where the file came from * then you should simply ignore the collision since there is not enough * information to determine if a real problem exists. Please do NOT file * a bug report at https://bugs.gentoo.org/ unless you report exactly * which two packages install the same file(s). See * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how * to solve the problem. And once again, please do NOT file a bug report * unless you have completely understood the above message. * * Detected file collision(s): * * /home/vm/gentoo/tmp/bin/tar * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * None of the installed packages claim the file(s). * * Package 'app-alternatives/tar-0' merged despite file collisions. If * necessary, refer to your elog messages for the whole content of the * above message. * Messages for package app-alternatives/gzip-0: * This package will overwrite one or more files that may belong to other * packages (see list below). You can use a command such as `portageq * owners / ` to identify the installed package that owns a * file. If portageq reports that only one package owns a file then do * NOT file a bug report. A bug report is only useful if it identifies at * least two or more packages that are known to install the same file(s). * If a collision occurs and you can not explain where the file came from * then you should simply ignore the collision since there is not enough * information to determine if a real problem exists. Please do NOT file * a bug report at https://bugs.gentoo.org/ unless you report exactly * which two packages install the same file(s). See * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how * to solve the problem. And once again, please do NOT file a bug report * unless you have completely understood the above message. * * Detected file collision(s): * * /home/vm/gentoo/tmp/bin/gzip * /home/vm/gentoo/tmp/bin/gunzip * /home/vm/gentoo/tmp/bin/zcat * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * None of the installed packages claim the file(s). * * Package 'app-alternatives/gzip-0' merged despite file collisions. If * necessary, refer to your elog messages for the whole content of the * above message. * Messages for package perl-core/File-Temp-0.231.100: * ERROR: perl-core/File-Temp-0.231.100::gentoo failed (configure phase): * Unable to build! * * Call stack: * ebuild.sh, line 127: Called src_configure * environment, line 1131: Called perl-module_src_configure * environment, line 657: Called die * The specific snippet of code: * perl Makefile.PL "$@" <<< "${pm_echovar}" || die "Unable to build!"; * * If you need support, post the output of `emerge --info '=perl-core/File-Temp-0.231.100::gentoo'`, * the complete build log and the output of `emerge -pqv '=perl-core/File-Temp-0.231.100::gentoo'`. * The complete build log is located at '/home/vm/gentoo/tmp/var/tmp/portage/perl-core/File-Temp-0.231.100/temp/build.log'. * The ebuild environment file is located at '/home/vm/gentoo/tmp/var/tmp/portage/perl-core/File-Temp-0.231.100/temp/environment'. * Working directory: '/home/vm/gentoo/tmp/var/tmp/portage/perl-core/File-Temp-0.231.100/work/File-Temp-0.2311' * S: '/home/vm/gentoo/tmp/var/tmp/portage/perl-core/File-Temp-0.231.100/work/File-Temp-0.2311' Hmmmm, I was already afraid of this to happen. Running /home/vm/gentoo/bin/bash ./bootstrap-prefix.sh "/home/vm/gentoo" stage3 somewhere failed :( Details might be found in the build log: /home/vm/gentoo/tmp/var/tmp/portage/perl-core/File-Temp-0.231.100/temp/build.log /home/vm/gentoo/var/tmp/portage/dev-libs/openssl-1.1.1s/temp/build.log I have no clue, really. Please find friendly folks in #gentoo-prefix on irc.gentoo.org, gentoo-alt@lists.gentoo.org mailing list, or file a bug at bugs.gentoo.org under Gentoo/Alt, Prefix Support. This is most inconvenient, and it crushed my ego. Sorry, I give up. Should you want to give it a try, there is /home/vm/gentoo/stage3.log