Every time I do an emerge world, It crashes with an unrecognised machine type. It appaers to have truncated it from 'i686-pc-linux-gnu' to 'i686-pc-linux-'. I imagine this is a problem with gcc, because I just updated to version i686-pc-linux-gnu-3.4.3-20050110. Unfortunately, I have no idea which config file to edit. Reproducible: Always Steps to Reproduce: 1.emerge -uDv world 2. 3. Actual Results: sandbox fails here, but as far as I can make out, any ebuild does the same thing . Xine-lib was the first one. tess sbin # emerge -uDv world Calculating world dependencies ...done! >>> emerge (1 of 12) sys-apps/sandbox-1.2.1-r2 to / >>> md5 files ;-) sandbox-1.2.ebuild >>> md5 files ;-) sandbox-1.2.1-r2.ebuild >>> md5 files ;-) sandbox-1.2.1.ebuild >>> md5 files ;-) sandbox-1.2.1-r1.ebuild >>> md5 files ;-) sandbox-1.2.1-r3.ebuild >>> md5 files ;-) ChangeLog >>> md5 files ;-) metadata.xml >>> md5 files ;-) files/digest-sandbox-1.2.1 >>> md5 files ;-) files/digest-sandbox-1.2.1-r1 >>> md5 files ;-) files/digest-sandbox-1.2.1-r2 >>> md5 files ;-) files/digest-sandbox-1.2.1-r3 >>> md5 files ;-) files/digest-sandbox-1.2 >>> md5 src_uri ;-) sandbox-1.2.1.tar.bz2 >>> Unpacking source... >>> Unpacking sandbox-1.2.1.tar.bz2 to /var/tmp/portage/sandbox-1.2.1-r2/work * Removing useless C++ checks ... [ ok ] >>> Source unpacked. * econf: updating sandbox-1.2.1/config.guess with /usr/share/gnuconfig/config.guess * econf: updating sandbox-1.2.1/config.sub with /usr/share/gnuconfig/config.sub ./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib configure: WARNING: If you wanted to set the --build type, don't use --host. If a cross compiler is detected then cross compile mode will be used. checking for a BSD-compatible install... /bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for i686-pc-linux-gnu-strip... i686-pc-linux-gnu-strip checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether i686-pc-linux-gnu-gcc accepts -g... yes checking for i686-pc-linux-gnu-gcc option to accept ANSI C... none needed checking for style of include used by make... GNU checking dependency style of i686-pc-linux-gnu-gcc... gcc3 checking for library containing strerror... none required checking for a BSD-compatible install... /bin/install -c checking whether make sets $(MAKE)... (cached) yes checking for gawk... (cached) gawk checking build system type... Invalid configuration `i686-pc-linux-': machine `i686-pc-linux' not recognized configure: error: /bin/sh ./config.sub i686-pc-linux- failed !!! Please attach the config.log to your bug report: !!! /var/tmp/portage/sandbox-1.2.1-r2/work/sandbox-1.2.1/config.log !!! ERROR: sys-apps/sandbox-1.2.1-r2 failed. !!! Function econf, Line 485, Exitcode 0 !!! econf failed !!! If you need support, post the topmost build error, NOT this status message. Expected Results: I expected it to compile cleanly My system is a bit of a mess, but it was running very smoothly prior to updating gcc. I put he bug to Major Severity, because of it being, as far as I can make out, gcc that is broken. I hope this was the right thing to do. Thanks. Tom. tess sbin # emerge info Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.4.3-20050110, glibc-2.3.5-r0, 2.6.10-gentoo-r6 i686) ================================================================= System uname: 2.6.10-gentoo-r6 i686 AMD Athlon(tm) Gentoo Base System version 1.6.11 Python: dev-lang/python-2.3.5 [2.3.5 (#1, Feb 21 2005, 05:30:56)] ccache version 2.4 [enabled] dev-lang/python: 2.3.5 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.5 sys-devel/binutils: 2.15.92.0.2-r8 sys-devel/libtool: 1.5.14 virtual/os-headers: 2.6.11 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=athlon-xp -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=athlon-xp -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks fixpackages sandbox sfperms strict" GENTOO_MIRRORS="ftp://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo ftp://ftp.heanet.ie/pub/gentoo/" 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="3dnow X aac aalib acl acpi alsa apache2 apm avi bash-completion berkdb bitmap-fonts bluetooth bmp bzlib cdparanoia cdr cups curl dga dio directfb divx4linux dvd dvdr dvdread emacs emboss encode esd ethereal f77 fam fbcon flac foomaticdb fortran ftp gd gdbm gif glut gpm hal imagemagick imap imlib innodb java javascript jikes joystick jpeg junit kde kdeenablefinal kdexdeltas kerberos lcms ldap leim lesstif libcaca libedit libg++ libwww mad matroska matrox memlimit mikmod mime mmx mng motif mp3 mpeg mpi msn mule mysql ncurses nls nptl odbc offensive ofx ogg oggvorbis openal opengl oss pam pcre pdflib perl php pic pie png posix python qt quicktime readline recode ruby samba sapdb sasl scanner sdl slang sockets spell spl sqlite sse sse2 ssl svg svga sysvipc tcltk tcpd theora threads tidy tiff truetype truetype-fonts type1-fonts usb v4l vcd vorbis win32codecs wmf x86 xine xml xml2 xmms xosd xpm xv xvid zlib video_cards_radeon" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS
Can you attach /var/tmp/portage/sandbox-1.2.1-r2/work/sandbox-1.2.1/config.log please?
Created attachment 57174 [details] /var/tmp/portage/sandbox-1.2.1-r2/work/sandbox-1.2.1/config.log here is /var/tmp/portage/sandbox-1.2.1-r2/work/sandbox-1.2.1/config.log, as requested
uname -a please.
Never mind on that one. I found it in the config.log. Can you unpack the sandbox tarball and then run `bash -x config.guess >& guess.log` and attach the log please?
*** Bug 90380 has been marked as a duplicate of this bug. ***
Created attachment 57190 [details] guess.log, as requested
what about running `bash -x /usr/share/gnuconfig/config.guess`
Created attachment 57199 [details] output of `bash -x /usr/share/gnuconfig/config.guess`, also as requested :-)
Both are returning i686-pc-linux-gnu as expected...
ive seen this before but only when the toolchain was a little out of whack ... what does `binutils-config -l` and `gcc-config -l` show ?
here you are: tess ~ # binutils-config -l [1] i686-pc-linux-gnu-2.15.92.0.2 * tess ~ # gcc-config -l [1] i686-pc-linux-gnu-3.3.4 [2] i686-pc-linux-gnu-3.4.3-20050110 * [3] i686-pc-linux-gnu-3.4.3-20050110-hardened [4] i686-pc-linux-gnu-3.4.3-20050110-hardenednopie [5] i686-pc-linux-gnu-3.4.3-20050110-hardenednossp
so if you do `binutils-config 1` and then `gcc-config 2` and then `source /etc/profile`, does it work ?
I've tried binutils-config 1 and gcc-config 1 (witch is i686-pc-linux-gnu-3.3.5-20050130 on my system. I have the same binutils version. (see bug #90380) ) I've found out that the ac_cv_build_alias variable is the one that's set wrong. in my case the varible is found in /var/tmp/portage/gettext-0.14.1-r1/work/gettext-0.14.1/config.log Hope this helps.
Oh. I forgot to say that running binutils-config 1, gcc-config 1 and source /etc/profile didn't work. :(
didn't work for me either.
I did emerge --resume --skipfirst after an emerge -uDv world which failed, and it updated portage for me. Now the previous error doesn't happen anymore, but I get this instead: [...] checking for strcasecmp... yes checking for strchr... yes checking for strdup... yes checking for strerror... yes checking for strndup... yes checking for strrchr... yes checking for strspn... yes checking for strstr... yes checking truncate argument type... off_t checking Checking libc version... ./configure: /usr/bin/wrappers/gcc: No such file or directory ldd: ./libctest: No such file or directory ldd: ./libctest: No such file or directory configure: creating ./config.status config.status: creating Makefile config.status: creating config.h config.status: executing depfiles commands make all-am make[1]: Entering directory `/var/tmp/portage/sandbox-1.2.1-r2/work/sandbox-1.2.1' Generating symbols.h *** Cannot find ! make[1]: *** [symbols.h] Error 1 make[1]: Leaving directory `/var/tmp/portage/sandbox-1.2.1-r2/work/sandbox-1.2.1' make: *** [all] Error 2 !!! ERROR: sys-apps/sandbox-1.2.1-r2 failed. !!! Function src_compile, Line 71, Exitcode 2 !!! emake failed !!! If you need support, post the topmost build error, NOT this status message.
try re-emerging gcc-config
No change :-(
Ok I got rid of that by removing my colorgcc setup. I think my system works now :-)
As above.
I don't run colorgcc, so this is not my problem. I run a x86 system with some packages set to ~x86 by /etc/portage/package.keywords. I've now tried emerging portage with ~x86 set, ignoring the sandbox dependency. gettext has now compiled, so i guess the portage upgrade worked. But it's a bit scary that x86 portage borks my system?
Umm.. what do you mean you upgraded portage and ignored the sandbox dependency? That means you now have no sandbox. And how does x86 portage bork your system? Do you get the i686-pc-linux- problem with every ebuild or just sandbox? Please provide emerge info and the config.guess output as above.
Sorry for the delay, haven't had time to sit still for a litte while. :) I had the problem in question, (see bug #90380). It affected all my non-binary packages. The soulution I found was to upgrade portage from x86 to ~x86 (I'm trying to keep my system x86). I ignored the sandbox dep (because sandbox wouldn't compile due to the error) and, sure enough, sandbox is no more. I then started an emerge -uav world wich stopped after a package was compiled (probably glibc or something in that department, I was sadly too stupid to take note of the previous package before I tried to fix the error). Now configure stops because the C++ compilator cannot create executables. checking for --with-cxx=<compiler>... no checking for c++... c++ checking for C++ compiler default output file name... configure: error: C++ compiler cannot create executables See `config.log' for more details. I'll attatch the config.log, please let me know if you need more...
Created attachment 57615 [details] config.log (problably needed to see what goes wrong with my C++ compiler / configure
./configure: line 1: /usr/lib/distcc/bin/c++: cannot execute binary file your current issue is unrelated to this bug which is now fixed i'd figure out why your distcc is screwed up
