make[1]: Leaving directory `/var/tmp/portage/e2fsprogs-1.38/work/e2fsprogs-1.38/po' making install-shlibs in lib/e2p make[1]: Entering directory `/var/tmp/portage/e2fsprogs-1.38/work/e2fsprogs-1.38/lib/e2p' MKINSTALLDIRS /usr/lib /usr/lib INSTALL-ELF-LIB /usr/lib/libe2p.so.2.3 SYMLINK /usr/lib/libe2p.so.2 SYMLINK /usr/lib/libe2p.so LDCONFIG make[1]: Leaving directory `/var/tmp/portage/e2fsprogs-1.38/work/e2fsprogs-1.38/lib/e2p' making install-shlibs in lib/ext2fs make[1]: Entering directory `/var/tmp/portage/e2fsprogs-1.38/work/e2fsprogs-1.38/lib/ext2fs' COMPILE_ET ext2_err.et make[1]: ../et/compile_et: Command not found make[1]: *** [ext2_err.c] Error 127 make[1]: Leaving directory `/var/tmp/portage/e2fsprogs-1.38/work/e2fsprogs-1.38/lib/ext2fs' make: *** [install-shlibs-libs-recursive] Error 1 !!! ERROR: sys-fs/e2fsprogs-1.38 failed. !!! Function src_install, Line 82, Exitcode 2 Reproducible: Always Steps to Reproduce: 1. install gentoo 2. wait 6 months to update world 3. emerge -uD world Portage 2.0.51.22-r2 (hardened/x86/2.6, gcc-3.3.5-20050130, glibc-2.3.5-r0, 2.6.10-hardened-r3 i586) ================================================================= System uname: 2.6.10-hardened-r3 i586 AMD-K6(tm) 3D processor Gentoo Base System version 1.6.13 dev-lang/python: 2.3.5 sys-apps/sandbox: 1.2.11 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.5 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i586-pc-linux-gnu" CFLAGS="-O2 -march=k6-2 -fomit-frame-pointer -pipe" CHOST="i586-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/bind /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=k6-2 -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig clean distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://mirror.datapipe.net/gentoo http://mirrors.tds.net/gentoo ftp://ftp.ndlug.nd.edu/pub/gentoo/ http://chod.cwru.edu/gentoo" PKGDIR="/usr/portage//packages/x86/" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage/" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 3dnow berkdb bzlib crypt curl hardened nptl nptl-only pam pcre perl pic posix postgres python readline ssl tcpd vhosts zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS
COMPILE_ET is overridden on the cmdline ... can you post the output of `emerge info --verbose` please
Created attachment 65628 [details] emerge info --verbose I experience a very similar error when attempting to emerge e2fsprogs-1.38. I had previously downgraded to 1.35 due to a bug that was introduced in 1.36 and has not yet been fixed. Additionally, my system is moderately hosed due to a libcom_err.so problem, as described here (by someone else): http://galaxycow.com/blogs/vermyndax/archive/2005/07/24/2226.aspx
Can you: # cd /var/tmp/portage/e2fsprogs-1.38/work/e2fsprogs-1.38/lib/ext2fs # make COMPILE_ET=compile_et And see if that passes ?
Same here...after a downgrade to 1.35, it is not possible to have 1.38 anymore...And as to comment 3, nope it did not work: COMPILE_ET ext2_err.et make: compile_et: Command not found make: *** [ext2_err.h] Error 127
do you not have com_err-1.38 installed ? you should have /usr/bin/compile_et on your system ...
I think I should make the problem precise first: I downgraded to e2fsprogs 1.35 (don't ask why) and everything was fine. Then I decided to go back to 1.38 and the emerge went fine there too. However, although it emerged, fsck and similar did not function with the libcom_err.so not found complaints. Then I did a revdep-rebuild hoping to fix the missing libs and revdep-rebuild wanted to reemerge e2fsprogs and failed to compile it with the compile_et: Command not found error. Now I seemed to have fixed it by RE-emerging both sys-libs/com_err-1.38 and sys-libs/ss-1.38 (thx comment 5) then e2fsprogs emerge went sucessfully. However, I am still not sure if there is a bug related to downgrading to 1.35 and then back up to 1.38.
sounds good
