From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Ky9og-0004mc-8l for garchives@archives.gentoo.org; Thu, 06 Nov 2008 18:42:50 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5A31CE0357; Thu, 6 Nov 2008 18:42:49 +0000 (UTC) Received: from mta-2.ms.rz.rwth-aachen.de (mta-2.ms.rz.RWTH-Aachen.DE [134.130.7.73]) by pigeon.gentoo.org (Postfix) with ESMTP id 2A0C1E0357 for ; Thu, 6 Nov 2008 18:42:49 +0000 (UTC) Received: from ironport-out-1.rz.rwth-aachen.de ([134.130.5.40]) by mta-2.ms.rz.RWTH-Aachen.de (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTP id <0K9X00LSDDBAL3E0@mta-2.ms.rz.RWTH-Aachen.de> for gentoo-user@lists.gentoo.org; Thu, 06 Nov 2008 19:42:46 +0100 (CET) Received: from relay-2.ms.rz.rwth-aachen.de (HELO relay.rwth-aachen.de) ([134.130.7.75]) by ironport-in-1.rz.rwth-aachen.de with ESMTP; Thu, 06 Nov 2008 19:42:47 +0100 Received: from numa-i.igpm.rwth-aachen.de (numa-i.igpm.RWTH-Aachen.DE [134.130.161.252]) by relay.rwth-aachen.de (8.13.8+Sun/8.13.8/1) with ESMTP id mA6Igktf010564 for ; Thu, 06 Nov 2008 19:42:46 +0100 (CET) Received: by numa-i.igpm.rwth-aachen.de (Postfix, from userid 230) id 07381106896; Thu, 06 Nov 2008 19:42:44 +0100 (CET) Date: Thu, 06 Nov 2008 19:42:44 +0100 (CET) From: Helmut Jarausch Subject: Re: [gentoo-user] Can't emerge sandbox In-reply-to: <200811061802.14462.peter@humphrey.ukfsn.org> To: gentoo-user@lists.gentoo.org Message-id: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-version: 1.0 Content-type: TEXT/PLAIN; CHARSET=us-ascii Content-transfer-encoding: 7BIT Content-disposition: INLINE X-IronPort-AV: E=Sophos;i="4.33,559,1220220000"; d="scan'208";a="89564772" References: <200811061802.14462.peter@humphrey.ukfsn.org> X-Archives-Salt: 6020002c-cda1-481d-af03-f30ea26a5939 X-Archives-Hash: 1b59d07f4cef3d7f646edf84cc8f641d On 6 Nov, Peter Humphrey wrote: > Hello, > > Recent versions of portage have suggested an emerge -e world, so I thought > I'd try it. It got as far as sandbox, which failed with the once-common "C > compiler cannot create executables" error. Of course I > tried "FEATURES=-sandbox emerge sandbox" but that failed with the same > error. > > I wondered what is set wrongly in my environment, so I booted a minimal > installation CD and chrooted into the system, but with the same result. > > Can anyone suggest where my problem might lie? I've attached the log file. > I'm confused by the apparent references in it to the cross-compiler. Google > seems to have only old references. > > This is a dual-Opteron box with a mostly-amd64 setup - only a few packages > are ~amd64. I'm also running an emerge -eq world on another amd64 box, > which has had no problem with sandbox. Same versions of portage and sandbox > on both machines. > The lines configure:2292: i686-pc-linux-gnu-gcc -march=opteron -O2 -pipe conftest.c >&5 /usr/libexec/gcc/i686-pc-linux-gnu/ld: crt1.o: No such file: No such file or directory collect2: ld returned 1 exit status look like a misconfigured gcc. Can you emerge any package which requires the C-compiler? Try gcc-config -l and look which gcc is selected and if you can select a different one. Then - with this one selected - reemerge the probably newer version of gcc which was broken. I hope this helps, Helmut. -- Helmut Jarausch Lehrstuhl fuer Numerische Mathematik RWTH - Aachen University D 52056 Aachen, Germany