Hi, it seems currently one cannot run ./bootstrap-prefix.sh successfully: >>> Emerging (40 of 95) perl-core/File-Temp-0.231.100::gentoo Warning: File compression unsupported zstd. Missing package: app-arch/zstd * File-Temp-0.2311.tar.gz BLAKE2B SHA512 size ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking File-Temp-0.2311.tar.gz to /auto/vestec1-elixir/projects/biocev/gentoo/tmp/var/tmp/portage/perl-core/File-Temp-0.231.100/work >>> Source unpacked in /auto/vestec1-elixir/projects/biocev/gentoo/tmp/var/tmp/portage/perl-core/File-Temp-0.231.100/work >>> Preparing source in /auto/vestec1-elixir/projects/biocev/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 /auto/vestec1-elixir/projects/biocev/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=/auto/vestec1-elixir/projects/biocev/gentoo/tmp/usr INSTALLDIRS=vendor INSTALLMAN3DIR=none DESTDIR=/auto/vestec1-elixir/projects/biocev/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 1803: Called perl-module_src_configure * environment, line 1329: 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 '/auto/vestec1-elixir/projects/biocev/gentoo/tmp/var/tmp/portage/perl-core/File-Temp-0.231.100/temp/build.log'. * The ebuild environment file is located at '/auto/vestec1-elixir/projects/biocev/gentoo/tmp/var/tmp/portage/perl-core/File-Temp-0.231.100/temp/environment'. * Working directory: '/auto/vestec1-elixir/projects/biocev/gentoo/tmp/var/tmp/portage/perl-core/File-Temp-0.231.100/work/File-Temp-0.2311' * S: '/auto/vestec1-elixir/projects/biocev/gentoo/tmp/var/tmp/portage/perl-core/File-Temp-0.231.100/work/File-Temp-0.2311'
Probably bug 892239. In future, please include the *full* prefix logs that the script tells you to. *** This bug has been marked as a duplicate of bug 892239 ***
Hi Sam, sorry for that but the stage3.log has 40 MB. I was not sure if I can run prefix bash provided the stage failed. Therefore no emerge --info , I just did not have any. I could still grep-out some lines. I thought I had included the relevant potion of the particular package failing. Now I se the stage3.log did not contain the trailing lines which were only left on the terminal: Hmmmm, I was already afraid of this to happen. Running /auto/vestec1-elixir/projects/biocev/gentoo/bin/bash ./bootstrap-prefix.sh "/auto/vestec1-elixir/projects/biocev/gentoo" stage3 somewhere failed :( Details might be found in the build log: /auto/vestec1-elixir/projects/biocev/gentoo/tmp/var/tmp/portage/perl-core/File-Temp-0.231.100/temp/build.log /auto/vestec1-elixir/projects/biocev/gentoo/var/tmp/portage/sys-devel/m4-1.4.19-r2/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 /auto/vestec1-elixir/projects/biocev/gentoo/stage3.log
ls -latr /auto/vestec1-elixir/projects/biocev/gentoo/ celkem 57374 drwxrws--- 3 mmokrejs 10296 4096 May 30 14:49 .. -rwxrwx--x 1 mmokrejs 10296 101640 May 30 14:58 bootstrap-prefix.sh -rw-rw---- 1 mmokrejs 10296 2126995 May 30 15:18 stage1.log -rw-rw---- 1 mmokrejs 10296 0 May 30 15:18 .stage1-finished drwxrws--- 7 mmokrejs 10296 4096 May 30 15:28 tmp -rw-rw---- 1 mmokrejs 10296 14609561 May 30 16:25 stage2.log -rw-rw---- 1 mmokrejs 10296 0 May 30 16:25 .stage2-finished drwxrws--- 7 mmokrejs 10296 4096 May 30 16:26 var drwxrws--- 2 mmokrejs 10296 4096 May 30 16:26 run drwxrws--- 11 mmokrejs 10296 4096 May 30 16:26 . drwxr-xr-x 2 mmokrejs meta 4096 May 30 16:59 sbin drwxrws--- 2 mmokrejs 10296 4096 May 30 17:00 lib64 drwxrws--- 11 mmokrejs 10296 4096 May 30 17:29 usr drwxrws--- 5 mmokrejs 10296 4096 May 30 17:29 lib drwxrws--- 2 mmokrejs 10296 4096 May 30 18:06 bin drwxrws--- 12 mmokrejs 10296 4096 May 30 18:06 etc -rw-rw---- 1 mmokrejs 10296 41890106 May 30 18:26 stage3.log $ $ /auto/vestec1-elixir/projects/biocev/gentoo/bin/bash mmokrejs@foo ~ $ emerge --info bash: emerge: command not found $ $ find /auto/vestec1-elixir/projects/biocev/gentoo/ -name emerge /auto/vestec1-elixir/projects/biocev/gentoo/tmp/usr/bin/emerge /auto/vestec1-elixir/projects/biocev/gentoo/tmp/usr/lib/portage/bin/emerge /auto/vestec1-elixir/projects/biocev/gentoo/tmp/usr/lib/portage/lib/portage/tests/emerge /auto/vestec1-elixir/projects/biocev/gentoo/var/db/repos/gentoo/app-xemacs/emerge $ $ /auto/vestec1-elixir/projects/biocev/gentoo/tmp/usr/bin/emerge --info python: no python-exec wrapped executable found in /auto/vestec1-elixir/projects/biocev/gentoo/tmp/usr/lib/python-exec. $ /auto/vestec1-elixir/projects/biocev/gentoo/tmp/usr/bin/emerge /auto/vestec1-elixir/projects/biocev/gentoo/tmp/usr/lib/portage/bin/emerge python: no python-exec wrapped executable found in /auto/vestec1-elixir/projects/biocev/gentoo/tmp/usr/lib/python-exec. $ Hmm, well provided the build process stopped I do get startprefix.sh installed (yet) to set the environment and so I cannot really move ahead. Are you sure the libperl.so.5.36: cannot open shared object file: No such file or directory is a "normal" message on Gentoo-Prefix?
Created attachment 863000 [details] stage3.log.xz
no, I think what may have happened is a perl upgrade, using a later snapshot may help, but need to check
Created attachment 863001 [details] stage2.log.xz
Created attachment 863002 [details] stage1.log.xz
