Hi, if you want to build your new system from stage1, you will get into trouble with coreutils first and Test-Harness and PodParser later. When 'emerge -e system' comes to build coreutils, it misses /usr/lib/perl5/5.8.8/i486-linux/auto/POSIX/assert.al, which can easily be fixed by copying it from another system. After that it will fail to build Test-Harness and PodParser, which I worked around with commenting out line 'inherit perl-modul' on both ebuilds, followed by an 'ebuild ... digest' and 'emerge --resume' will finish 'emerge -e system' for you. While perl was rebuild in this step and should now have all required files, you can 'emerge Test-Harness PodParser' normaly. (Don't forget to undo your changes to the ebuild-files.) I think this problem can be solved by reordering the ports to build for 'emerge -e system'. Bye. Reproducible: Always Steps to Reproduce: 1. Perform a Stage1-Installation Actual Results: Cancel on 'emerge -e system' Expected Results: To finish 'emerge -e system' normaly
*** This bug has been marked as a duplicate of bug 147184 ***
#147184 fixes only the build-process of coreutils
Maybe if you actually posted some real info, someone could have a look. On that note, stage1 is unsupported.
Reproducing the bug: / # mkdir /chroot / # tar xjpf ../stage2-i686-2007.0.tar.bz2 -C chroot / # mkdir /chroot/usr/portage / # mount -o bind /usr/portage /chroot/usr/portage/ / # mount -o bind /dev/ /chroot/dev/ / # mount -t proc none /chroot/proc / # chroot /chroot /bin/bash / # env-update >>> Regenerating /etc/ld.so.cache... / # source /etc/profile / # emerge -av portage [...] [ebuild U ] sys-apps/portage-2.1.2.11 [2.1.2.2] USE="-build* -doc -epydoc -selinux)" LINGUAS="-pl" 0 kB [...] / # emerge -epv system | grep perl [ebuild R ] sys-devel/libperl-5.8.8-r1 USE="berkdb* gdbm* -debug -ithreads" 0 kB [ebuild R ] app-admin/perl-cleaner-1.04.3 0 kB [ebuild N ] perl-core/Test-Harness-2.64 0 kB [ebuild N ] perl-core/PodParser-1.35 0 kB [ebuild R ] dev-lang/perl-5.8.8-r2 USE="berkdb* gdbm* -build* -debug -doc -ithreads -perlsuid" 0 kB [ebuild N ] dev-perl/Locale-gettext-1.05 8 kB [ebuild N ] sys-apps/util-linux-2.12r-r7 USE="crypt nls perl -old-crypt (-selinux) -static" 170 kB / # find /usr/lib/perl5/5.8.8/i486-linux/ExtUtils find: /usr/lib/perl5/5.8.8/i486-linux/ExtUtils: No such file or directory / # emerge Test-Harness Calculating dependencies... done! >>> Verifying ebuild Manifests... >>> Emerging (1 of 1) perl-core/Test-Harness-2.64 to / * Test-Harness-2.64.tar.gz RMD160 ;-) ... [ ok ] * Test-Harness-2.64.tar.gz SHA1 ;-) ... [ ok ] * Test-Harness-2.64.tar.gz SHA256 ;-) ... [ ok ] * Test-Harness-2.64.tar.gz size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking Test-Harness-2.64.tar.gz ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking Test-Harness-2.64.tar.gz to /var/tmp/portage/perl-core/Test-Harness-2.64/work >>> Source unpacked. >>> Compiling source in /var/tmp/portage/perl-core/Test-Harness-2.64/work/Test-Harness-2.64 ... * Using ExtUtils::MakeMaker Can't locate ExtUtils/MakeMaker/Config.pm in @INC (@INC contains: /etc/perl /usr/lib/perl5/vendor_perl/5.8.8/i486-linux /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl /usr/lib/perl5/site_perl/5.8.8/i486-linux /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl /usr/lib/perl5/5.8.8/i486-linux /usr/lib/perl5/5.8.8 /usr/local/lib/site_perl .) at /usr/lib/perl5/5.8.8/ExtUtils/MakeMaker.pm line 7. BEGIN failed--compilation aborted at /usr/lib/perl5/5.8.8/ExtUtils/MakeMaker.pm line 7. Compilation failed in require at Makefile.PL line 3. BEGIN failed--compilation aborted at Makefile.PL line 3. !!! ERROR: perl-core/Test-Harness-2.64 failed. Call stack: ebuild.sh, line 1632: Called dyn_compile ebuild.sh, line 983: Called qa_call 'src_compile' ebuild.sh, line 44: Called src_compile ebuild.sh, line 1322: Called perl-module_src_compile perl-module.eclass, line 136: Called perl-module_src_prep perl-module.eclass, line 125: Called die !!! Unable to build! (are you using USE="build"?) !!! If you need support, post the topmost build error, and the call stack if relevant. !!! A complete build log is located at '/var/tmp/portage/perl-core/Test-Harness-2.64/temp/build.log'. / #
Right; exactly one of the reasons why anything but stage3 install in *unsupported*. Meaning, you are totally on your own solving whatever issues you encounter when using this install method, not our problem.
*** This bug has been marked as a duplicate of bug 187866 ***
