starting with portage-2.047-r8 i can't emerge any ebuilds anymore. emerge always fails with an error similar to: !!! ERROR: {ebuild name} failed. !!! Function econf, Line xyz, Exitcode 1 !!! no configure script found after reading bug report #16768 i force-updated portage to 2.0.47-r9 (amazingly, this worked), but it didn't solve the issues hal portage # emerge info Portage 2.0.47-r9 (, gcc-3.2.2, glibc-2.2.5-r4,2.3.1-r2) ================================================================= System uname: 2.4.20-gentoo-r1 i686 AMD Athlon(tm) Processor GENTOO_MIRRORS="http://www.ibiblio.org/pub/Linux/distributions/gentoo" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X1 1/xkb /usr/kde/3.1/share/config /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" PORTDIR="/usr/portage" DISTDIR="/usr/portage/distfiles" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR_OVERLAY="/usr/local/portage" USE="x86 oss 3dnow apm avi crypt cups encode gif jpeg libg++ mikmod mmx mpeg ncurses nls pdflib png quicktime spell truetype xml2 xmms xv zlib directfb gtkhtml alsa gdbm berkdb slang readline arts tetex aalib nas bonobo svga ggi tcltk java guile ruby X sdl gpm tcpd pam libwww ssl perl python esd imlib oggvorbis gnome gtk qt kde motif opengl mozilla cdr scanner +gif +mmx +3dnow +ldap +odbc +fbcon +qtmt +oss +libg++ +nls +mitshm" COMPILER="gcc3" CHOST="i686-pc-linux-gnu" CFLAGS="-march=athlon-tbird -O3 -pipe" CXXFLAGS="-march=athlon-tbird -O3 -pipe" ACCEPT_KEYWORDS="x86" MAKEOPTS="-j2" AUTOCLEAN="yes" SYNC="rsync://rsync.gentoo.org/gentoo-portage" FEATURES="sandbox ccache" wanted to diff econf() to an earlier version.. but didn't find any victims in #gentoo ;) hmm.. moment. looks like the tgz's aren't even unpacked. at least when executing ebuild xyz unpack.. i.e. ebuild says: hal mono # ebuild mono-0.23.ebuild unpack >>> md5 ;-) mono-0.23.tar.gz >>> md5 ;-) mcs-0.23.tar.gz >>> Checking mono-0.23.tar.gz's mtime... >>> Checking mcs-0.23.tar.gz's mtime... >>> WORKDIR is up-to-date, keeping... hal mono-0.23 # ls -laR .: insgesamt 48 drwxr-xr-x 4 portage portage 4096 2003-03-13 22:15 . drwxr-xr-x 187 portage portage 36864 2003-03-13 21:44 .. drwsrws--- 2 portage portage 4096 2003-03-13 22:35 temp -rw-r--r-- 1 root root 0 2003-03-13 22:15 .unpacked drwx------ 2 root root 4096 2003-03-13 22:15 work ./temp: insgesamt 60 drwsrws--- 2 portage portage 4096 2003-03-13 22:35 . drwxr-xr-x 4 portage portage 4096 2003-03-13 22:15 .. -rw-rw-r-- 1 root portage 2900 2003-03-13 22:35 eclass-debug.log -rw-rw-r-- 1 portage portage 46372 2003-03-13 22:35 environment -rw-rw-r-- 1 portage portage 0 2003-03-13 22:35 successful ./work: insgesamt 40664 drwx------ 2 root root 4096 2003-03-13 22:15 . drwxr-xr-x 4 portage portage 4096 2003-03-13 22:15 .. -rw-r--r-- 1 root root 29460480 2003-03-13 22:15 mcs-0.23.tar -rw-r--r-- 1 root root 12113920 2003-03-13 22:15 mono-0.23.tar hmm.. now i've made an 'rm -rf /var/tmp/portage/*'.. hal mono # ebuild mono-0.23.ebuild unpack >>> md5 ;-) mono-0.23.tar.gz >>> md5 ;-) mcs-0.23.tar.gz >>> Unpacking source... >>> Unpacking mono-0.23.tar.gz to /var/tmp/portage/mono-0.23/work >>> Unpacking mcs-0.23.tar.gz to /var/tmp/portage/mono-0.23/work /usr/sbin/ebuild.sh: line 32: /var/tmp/portage/mono-0.23/work/mono-0.23/runtime/mcs: Datei oder Verzeichnis nicht gefunden chmod: konnte Attribute von
starting with portage-2.047-r8 i can't emerge any ebuilds anymore. emerge always fails with an error similar to: !!! ERROR: {ebuild name} failed. !!! Function econf, Line xyz, Exitcode 1 !!! no configure script found after reading bug report #16768 i force-updated portage to 2.0.47-r9 (amazingly, this worked), but it didn't solve the issues hal portage # emerge info Portage 2.0.47-r9 (, gcc-3.2.2, glibc-2.2.5-r4,2.3.1-r2) ================================================================= System uname: 2.4.20-gentoo-r1 i686 AMD Athlon(tm) Processor GENTOO_MIRRORS="http://www.ibiblio.org/pub/Linux/distributions/gentoo" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X1 1/xkb /usr/kde/3.1/share/config /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" PORTDIR="/usr/portage" DISTDIR="/usr/portage/distfiles" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR_OVERLAY="/usr/local/portage" USE="x86 oss 3dnow apm avi crypt cups encode gif jpeg libg++ mikmod mmx mpeg ncurses nls pdflib png quicktime spell truetype xml2 xmms xv zlib directfb gtkhtml alsa gdbm berkdb slang readline arts tetex aalib nas bonobo svga ggi tcltk java guile ruby X sdl gpm tcpd pam libwww ssl perl python esd imlib oggvorbis gnome gtk qt kde motif opengl mozilla cdr scanner +gif +mmx +3dnow +ldap +odbc +fbcon +qtmt +oss +libg++ +nls +mitshm" COMPILER="gcc3" CHOST="i686-pc-linux-gnu" CFLAGS="-march=athlon-tbird -O3 -pipe" CXXFLAGS="-march=athlon-tbird -O3 -pipe" ACCEPT_KEYWORDS="x86" MAKEOPTS="-j2" AUTOCLEAN="yes" SYNC="rsync://rsync.gentoo.org/gentoo-portage" FEATURES="sandbox ccache" wanted to diff econf() to an earlier version.. but didn't find any victims in #gentoo ;) hmm.. moment. looks like the tgz's aren't even unpacked. at least when executing ebuild xyz unpack.. i.e. ebuild says: hal mono # ebuild mono-0.23.ebuild unpack >>> md5 ;-) mono-0.23.tar.gz >>> md5 ;-) mcs-0.23.tar.gz >>> Checking mono-0.23.tar.gz's mtime... >>> Checking mcs-0.23.tar.gz's mtime... >>> WORKDIR is up-to-date, keeping... hal mono-0.23 # ls -laR .: insgesamt 48 drwxr-xr-x 4 portage portage 4096 2003-03-13 22:15 . drwxr-xr-x 187 portage portage 36864 2003-03-13 21:44 .. drwsrws--- 2 portage portage 4096 2003-03-13 22:35 temp -rw-r--r-- 1 root root 0 2003-03-13 22:15 .unpacked drwx------ 2 root root 4096 2003-03-13 22:15 work ./temp: insgesamt 60 drwsrws--- 2 portage portage 4096 2003-03-13 22:35 . drwxr-xr-x 4 portage portage 4096 2003-03-13 22:15 .. -rw-rw-r-- 1 root portage 2900 2003-03-13 22:35 eclass-debug.log -rw-rw-r-- 1 portage portage 46372 2003-03-13 22:35 environment -rw-rw-r-- 1 portage portage 0 2003-03-13 22:35 successful ./work: insgesamt 40664 drwx------ 2 root root 4096 2003-03-13 22:15 . drwxr-xr-x 4 portage portage 4096 2003-03-13 22:15 .. -rw-r--r-- 1 root root 29460480 2003-03-13 22:15 mcs-0.23.tar -rw-r--r-- 1 root root 12113920 2003-03-13 22:15 mono-0.23.tar hmm.. now i've made an 'rm -rf /var/tmp/portage/*'.. hal mono # ebuild mono-0.23.ebuild unpack >>> md5 ;-) mono-0.23.tar.gz >>> md5 ;-) mcs-0.23.tar.gz >>> Unpacking source... >>> Unpacking mono-0.23.tar.gz to /var/tmp/portage/mono-0.23/work >>> Unpacking mcs-0.23.tar.gz to /var/tmp/portage/mono-0.23/work /usr/sbin/ebuild.sh: line 32: /var/tmp/portage/mono-0.23/work/mono-0.23/runtime/mcs: Datei oder Verzeichnis nicht gefunden chmod: konnte Attribute von »/var/tmp/portage/mono-0.23/work/mono-0.23/runtime/mcs« nicht holen: Datei oder Verzeichnis nicht gefunden >>> Source unpacked. similar for any other ebuild (btw "Datei oder Verzeichnis nicht gefunden" means "file or directory not found"). yep. unpack doesn't seem to work. please take a look at it.
I don't know if it's relevant, but the fact that the profile is not reported in "emerge -V" was caused by the fact that the reporter had a trailing slash at the end of the /etc/make.profile symlink.
Use a rescue portage and then update portage the normal way. cd /usr/portage/sys-apps/portage/ less README.RESCUE
nicholas, i found the reason for these major probs: i set the Swiss-German locale LC="de_CH" LC_ALL="de_CH" This seems to cause major headaches to portage (or eventually a tool portage uses when unpacking). The only way to workaround these problems seems to be completely unsetting these two environment variables: unset LC unset LC_ALL (setting them to "C" or "en" doesn't help) Strange and pretty bad imho, as this is a locale I need e.g. to make mutt correctly display german characters. Regarding emergency portage: Please add a note to README.RESCUE that the config files /etc/make.conf /etc/make.globals /etc/etc-update.conf will be overwritten(!) by unpacking the tgz. So people are aware to make backups eventually. I was lucky to have backups of these files on another box.
Rescue portages allow for updates to -r10. The issue is resolved in -r10.
