RBOX profile-update # emerge -v ">=sys-apps/portage-2.0.51-r9" Calculating dependencies ...done! >>> emerge (1 of 1) sys-apps/portage-2.0.51-r14 to / >>> md5 src_uri ;-) portage-2.0.51-r14.tar.bz2 >>> Unpacking source... >>> Unpacking portage-2.0.51-r14.tar.bz2 to /var/tmp/portage/portage-2.0.51-r14/work patching file pym/portage.py >>> Source unpacked. rm -f libsandbox.so sandbox rm -f *.o *~ core rm -f localdecls.h ./create-localdecls Checking truncate argument type... off_t Checking libc version... libc.so.6 libc.so.6 x86_64-pc-linux-gnu-gcc -O1 -pipe -DSB_HAVE_64BIT_ARCH -D_GNU_SOURCE -DPIC -fPIC -D_REENTRANT -Wall -c libsandbox.c In file included from libsandbox.c:78: localdecls.h:9: error: parse error before '.' token localdecls.h:9: error: missing terminating " character make: *** [libsandbox.o] Error 1 !!! ERROR: sys-apps/portage-2.0.51-r14 failed. !!! Function src_compile, Line 102, Exitcode 2 !!! (no error message) !!! If you need support, post the topmost build error, NOT this status message. Reproducible: Always Steps to Reproduce: 1. Follow profile update steps 2. Watch 3. Actual Results: Portage emerges unsucessfully. Expected Results: Portage emerges successfully. RBOX profile-update # emerge info Portage 2.0.51-r14 (default-linux/amd64/2005.0, gcc-3.4.3, glibc-2.3.4.20040808-r1, 2.6.9-gentoo-r14 x86_64) ================================================================= System uname: 2.6.9-gentoo-r14 x86_64 AMD Athlon(tm) 64 Processor 3500+ Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4 [2.3.4 (#1, Nov 23 2004, 03:15:02)] distcc 2.18.3 x86_64-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] dev-lang/python: 2.3.4 sys-devel/autoconf: 2.59-r5 sys-devel/automake: 1.8.5-r1 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.2-r7 virtual/os-headers: 2.4.21-r1 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CFLAGS="-O3 -fomit-frame-pointer -pipe -funroll-loops -march=athlon64" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -fomit-frame-pointer -pipe -funroll-loops -march=athlon64" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" LDFLAGS="-W1,-O1" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 " X aac acpi aim alsa bitmap-fonts cdr crypt cups dvd f77 fam flac foomaticdb fortran gif gimpprint gpm gstreamer imagemagick imlib ipv6 java jp2 jpeg lzw lzw-tiff mad motif mp3 mpeg multislot ncurses nptl offensive oggvorbis opengl oss pam perl png ppds python quicktime readline real sdl spell ssl tcltk tcpd tiff truetype truetype-fonts type1-fonts usb userlocales xml xml2 xmms xpm xrandr xv zlib" Unset: ASFLAGS, CBUILD, CTARGET Hmm... another big problem. It seems that running the automatic profile update (which failed on emerge linux-headers-2.6.5 because it had downgraded) downgraded me to 2.4 Linux Headers. Look at the emerge info. I think this is a big problem, so I'm marking it critical. To summarize: the profile update gets old linux headers automatically, and portage fails to emerge manually.
Building portage with "features="-sandbox" emerge portage" works. Changing the bug title, I'm assuming we don't want everybody downgrading linux-headers to those for kernel versions they're not running.
After emerging the correct kernel headers and following the rest of the steps in the profile update, portage successfully emerged.
Read the 2005.0 update guide carefully, it explicitly states to unmask those header files. This won't be necessary after the release of 2005.0. Resolved as INVALID
