Trying to emerge eix-0.2.0_alpha. Get: i686-pc-linux-gnu-g++ -Wall -g -march=pentium3 -O2 -pipe -fomit-frame-pointer -o eix main.o debug_stopwatch.o mask.o portagedb.o varsreader.o versionex.o version.o globals.o regexclass.o package.o levenshtein_distance.o versionex.o: file not recognized: File format not recognized collect2: ld returned 1 exit status distcc[11351] ERROR: compile (null) on localhost failed make[2]: *** [eix] Error 1 make[2]: Leaving directory `/tmp/portage/eix-0.2.0_alpha/work/eix-0.2.0_alpha/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/tmp/portage/eix-0.2.0_alpha/work/eix-0.2.0_alpha' make: *** [all] Error 2 !!! ERROR: app-portage/eix-0.2.0_alpha failed. !!! Function src_compile, Line 28, Exitcode 2 !!! emake failed !!! If you need support, post the topmost build error, NOT this status message. I see looking at similar bugs reports in other packages that this is related to MAKEOPTS. I'm using distcc and -j6. Will try with -distcc and -j1 shortly. Reproducible: Always Steps to Reproduce: 1. 2. 3.
MAKEOPTS="-j1" FEATURES="-distcc" emerge eix worked just fine (but so slow...)
works fine here with MAKEOPTS="-j2" maybe it's just distcc being baaad?
Yeah, that seems right: I tried -j1 both with distcc and without distcc, and it only worked without.
0.2.0 should be released today and so will the ebuild, please try if things got fixed, otherwise we have to investigate. don't hesitate to join #eix on freenode!
could you please attach emerge info as well thanks
maybe this helps http://www.mail-archive.com/distcc%40lists.samba.org/msg01338.html
abe@tock ~ $ emerge info # as requested Portage 2.0.51-r15 (default-linux/x86/2004.3, gcc-3.3.5, glibc-2.3.4.20040808-r1 , 2.6.10 i686) ================================================================= System uname: 2.6.10 i686 AMD Athlon(tm) XP 2000+ Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4 [2.3.4 (#1, Oct 17 2004, 09:19:09)] distcc 2.16 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ccache version 2.3 [enabled] dev-lang/python: 2.3.4 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.7.9-r1, 1.5, 1.6.3, 1.4_p6, 1.9.4, 1.8.5-r3 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=athlon-xp -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share /config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/shar e/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/sh are/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/tex mf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=athlon-xp -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distcc distlocks sandbox sfperms" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/ distributions/gentoo" MAKEOPTS="-j6" PKGDIR="/usr/local/packages-portage" PORTAGE_TMPDIR="/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 3dnow X aalib alsa arts avi bash-completion berkdb bitmap-fonts bonobo cdr crypt cups dvd dvdr encode esd f77 fam font-server foomaticdb fortran gdbm g if gnome gphoto2 gpm gtk gtk2 gtkhtml guile imagemagick imap imlib java jpeg kde libg++ libwww mad mbox mikmod mmx motif mpeg mysql ncurses nptl oggvorbis openg l oss pam pda pdflib perl png python qt quicktime readline scanner sdl slang spe ll ssl svga tcltk tcpd tetex tiff truetype truetype-fonts type1-fonts xml xml2 x mms xv zlib" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS
Hmm.. interesting. I was exporting /usr/portage from another machine, but I'd think this wouldn't matter during the build phase. Yesterday, I actually changed the /usr/portage NFS server to another machine, since one was being unreliable. (... tried switching NFS option no_subtree_check on new machine ...) Okay, now I'm not sure what was going on. I've cleared the .ccache and .distcc directories on the distcc machines and the localhost. eix builds fine, also regardless of the NFS option. I'm quite certain it was happening before, but I can't seem to make it fail now! Perhaps some other package updated in the past couple days which inadvertantly fixed this??
well, i don't know for sure, but after reading through google and mailinglists, this seems rather a bug concerning nfs/distcc/ccache or broken connection, hardware dying or the like i'll resolve as invalid for now, please feel free to reopen it, if the error occurs again