From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1ORtCF-0006o9-74 for garchives@archives.gentoo.org; Thu, 24 Jun 2010 20:38:51 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id AF86BE09C2; Thu, 24 Jun 2010 20:38:19 +0000 (UTC) Received: from mail-ww0-f53.google.com (mail-ww0-f53.google.com [74.125.82.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 7419FE09C2 for ; Thu, 24 Jun 2010 20:38:19 +0000 (UTC) Received: by wwb17 with SMTP id 17so333187wwb.40 for ; Thu, 24 Jun 2010 13:38:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:reply-to:to:subject:date :user-agent:references:in-reply-to:mime-version:content-type :content-transfer-encoding:message-id; bh=d5oFZzD/ztZbDCjf62o93nO1Ayc7NV64USFonGD+B9M=; b=oAqfWE0hpYfPJNhsPfX71DCpMqRWDlOSzywH5gyyCECrkMtLXd6fgnuE+mScYV6Tcx 0k0ZTSIPiyZlDZa6lIdbHVTzgaDaXrg0s5+kkz6EK584Xjnsvgsb4lwn9RFd8Jlw192z ZndSIk/yen+RluFXaCIRstUhIFpqr91jN6lnk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:reply-to:to:subject:date:user-agent:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; b=Y7boISMGBhCy7WuehvTk43Jx94CKBvoTEYeld225MekPI04/hjvYafFRw4npSzqTrQ cUOspBzHehz4R9JE9OE+R499LqbrJC+MmDq3S0bTS6X6VvAUoxq9/3kKxxCC+CMYUvFg qx++AlbqPadhXSThQGn8e2ydwgzPPy32DRGfU= Received: by 10.216.85.141 with SMTP id u13mr4250440wee.105.1277411898752; Thu, 24 Jun 2010 13:38:18 -0700 (PDT) Received: from (230.3.169.217.in-addr.arpa [217.169.3.230]) by mx.google.com with ESMTPS id n61sm310793wed.30.2010.06.24.13.38.17 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 24 Jun 2010 13:38:17 -0700 (PDT) From: Mick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] gcc build fails during emerge system on new 64-bit install Date: Thu, 24 Jun 2010 21:38:17 +0100 User-Agent: KMail/1.12.4 (Linux/2.6.33-gentoo-r2; KDE/4.3.5; x86_64; ; ) References: <20100623233324.GA11305@waltdnes.org> In-Reply-To: <20100623233324.GA11305@waltdnes.org> 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: multipart/signed; boundary="nextPart1419032.ALDGMHtMo0"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201006242138.18010.michaelkintzios@gmail.com> X-Archives-Salt: b34f575f-80ec-4cd2-8b4d-9aa40f026f0a X-Archives-Hash: 2ceea244c3be2480ad8ac1bf325d95ef --nextPart1419032.ALDGMHtMo0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable On Thursday 24 June 2010 00:33:24 Walter Dnes wrote: > This is my first attempt at 64-bit mode. I have a shiny new Intel i3 > with 8 gigs ram on an MSI motherboard. I got it custom-built locally in > north Toronto, rather than ordering from Dell. The MSI motherboard has > PS/2 ports (YES!!!) so I don't have to tearfully throw away my genuine > IBM PS/2 "clickety-clack" keyboard. I selected the profile... >=20 > default/linux/amd64/10.0/no-multilib >=20 > ...to go whole-hog 64-bit. Does leaving IA32_EMULATION on cause a > problem? I thought that you can't have IA32_emulation without multilib ...=20 Is there a reason why you don't go for a usual desktop profile with multili= b? =20 I'll repeat the advice I was given in this list sometime around last Christ= mas=20 (but can't find the thread now): you're bound to find some pesky applicatio= n=20 which is only available in 32bit and then you'll curse for having to=20 reinstall. > # > # Executable file formats / Emulations > # > CONFIG_BINFMT_ELF=3Dy > CONFIG_COMPAT_BINFMT_ELF=3Dy > CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=3Dy > # CONFIG_HAVE_AOUT is not set > CONFIG_BINFMT_MISC=3Dy > CONFIG_IA32_EMULATION=3Dy > # CONFIG_IA32_AOUT is not set > CONFIG_COMPAT=3Dy > CONFIG_COMPAT_FOR_U64_ALIGNMENT=3Dy > CONFIG_SYSVIPC_COMPAT=3Dy > CONFIG_NET=3Dy > CONFIG_COMPAT_NETLINK_MESSAGES=3Dy >=20 > I've attached the tail-end of the build log file of gcc-4.4.3-r2, as > well as output from "emerge --info" and "emerge -pqv". I have a quite > conservative make.conf. Any ideas about the problem, or even better, a > solution? Have you tried setting -j1 and trying emerging it once more? =2D-=20 Regards, Mick --nextPart1419032.ALDGMHtMo0 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) iEYEABECAAYFAkwjwjoACgkQVTDTR3kpaLaC5gCffrh9XvsmnPg9gbrZPFphyJ3H FU8An1GzzKEJgK0ZDzKmGFKlOdswz0iI =YSdW -----END PGP SIGNATURE----- --nextPart1419032.ALDGMHtMo0--