My last current attempt to get a 2006.0 live and working... In a chrooted env (a 2005.0) - unpacked the 'release' stage3 tarball - unpacked the release portage snapshot - prepared my config files (make.conf, rc.conf, etc...) - emerge'd --sync - emerge --update portage (as recommended by the system and a lot of bugzillas) THEN ... ... Finding dependencies for perlio.o. Finding dependencies for perlapi.o. Finding dependencies for numeric.o. Finding dependencies for locale.o. Finding dependencies for pp_pack.o. Finding dependencies for pp_sort.o. Finding dependencies for miniperlmain.o. Finding dependencies for perlmain.o. Finding dependencies for opmini.o. make[1]: Entering directory `/var/tmp/portage/libperl-5.8.8-r1/work/perl-5.8.8' echo Makefile.SH cflags.SH config_h.SH makeaperl.SH makedepend.SH makedir.SH myconfig.SH writemain.SH pod/Makefile.SH | tr ' ' '\n' >.shlist make[1]: Leaving directory `/var/tmp/portage/libperl-5.8.8-r1/work/perl-5.8.8' Updating makefile... test -s perlmain.c && touch perlmain.c cd x2p; make depend make[1]: Entering directory `/var/tmp/portage/libperl-5.8.8-r1/work/perl-5.8.8/x2p' makefile:159: *** missing separator. Stop. make[1]: Leaving directory `/var/tmp/portage/libperl-5.8.8-r1/work/perl-5.8.8/x2p' make: *** [depend] Error 2 !!! ERROR: sys-devel/libperl-5.8.8-r1 failed. !!! Function src_compile, Line 268, Exitcode 2 !!! Couldn't make libperl.so depends MY EMERGE --INFO (being in the chrooted env) asus etc # emerge --info Portage 2.0.54 (default-linux/x86/2006.0, gcc-3.4.4, glibc-2.3.5-r2, 2.6.11-gentoo-r9 i686) ================================================================= System uname: 2.6.11-gentoo-r9 i686 Intel(R) Pentium(R) M processor 1.60GHz Gentoo Base System version 1.6.14 app-admin/eselect-compiler: [Not Present] dev-lang/python: 2.4.2 dev-python/pycrypto: [Not Present] dev-util/ccache: [Not Present] dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1 sys-devel/gcc-config: 1.3.12-r6 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=i686 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/lib/X11/xkb /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=i686 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" LANG="FR_fr@euro" LC_ALL="FR_fr@euro" LINGUAS="fr en" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X alsa apache2 apm arts avi berkdb bitmap-fonts bzip2 cli crypt cups dlloaderdri eds emboss encode esd expat foomaticdb fortran gdbm gif gpm gstreamer gtk gtk2 imlib ipv6 isdnlog jpeg kde libg++ libwww mad mikmod motif mp3 mpeg ncurses nls nptl ogg opengl pam pcre pdflib perl png pppd python qt qt3 qt4 quicktime readline reflection sdlsession spell spl ssl tcpd truetype truetype-fonts type1-fonts udev vorbis xml xmms xorg xv zlib input_devices_keyboard input_devices_mouse input_devices_evdev linguas_fr linguas_en userland_GNU kernel_linux elibc_glibc" Unset: CTARGET, INSTALL_MASK, LDFLAGS, MAKEOPTS, PORTAGE_RSYNC_EXTRA_OPTS, PORTAGE_RSYNC_OPTS, PORTDIR_OVERLAY ...will soon give up with 2006.0 ... and maybe Gentoo. Did not face so many issues with previous releases...
This is a dup bug from long ago. how's /dev/null and /dev/zero look in your chroot? iirc the problem is that in your chroot you haven't properly set these up, so they appear as files instead of device nodes.
(In reply to comment #1) > This is a dup bug from long ago. how's /dev/null and /dev/zero look in your > chroot? iirc the problem is that in your chroot you haven't properly set these > up, so they appear as files instead of device nodes. > (In reply to comment #1) > This is a dup bug from long ago. how's /dev/null and /dev/zero look in your > chroot? iirc the problem is that in your chroot you haven't properly set these > up, so they appear as files instead of device nodes. > In fact, this is an old attempt. Because KDE did not emerge correctly (NPTL seems to create some mess in many locations), I added USE='-posix' to successfully emerge KDE. BUT... This created another mess when updating Porgage : Perl cannot compile without Posix threads. Finally, I restarted all from scratch because USE='-posix' is definitely not a good choice. At the moment, I successfully updated Portage, and KDE is compiling because I added a symlink ln -s /usr/lib/gcc/i686-pc-linux-gnu/3.4.6 /usr/lib/gcc/i686-pc-linux-gnu/3.4.5 This is definitely not clean, but seems to work, ... and I could not get any other help from the KDE / glibc teams. I think you may now close this bug.
*** Bug 145787 has been marked as a duplicate of this bug. ***
