From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1HncOa-0000E9-00 for garchives@archives.gentoo.org; Mon, 14 May 2007 15:23:32 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l4EFNAGt018268; Mon, 14 May 2007 15:23:10 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l4EFN9PR018245 for ; Mon, 14 May 2007 15:23:09 GMT Received: by smtp.gentoo.org (Postfix, from userid 739) id DB3D764D5A; Mon, 14 May 2007 15:09:39 +0000 (UTC) Date: Mon, 14 May 2007 17:09:39 +0200 From: Bryan =?utf-8?Q?=C3=98stergaard?= To: gentoo-alpha@lists.gentoo.org Subject: Re: [gentoo-alpha] gcc 4.1.1-r3? [last update] Message-ID: <20070514150939.GF25269@woodpecker.gentoo.org> References: <46482EF2.2030509@gentoo.org> <72CC41F0-BE7D-4113-866F-5EF2E205E0F1@ifom-ieo-campus.it> <1A3BFBC6-CD85-4664-B66F-59063E372B3B@ifom-ieo-campus.it> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-alpha@gentoo.org Reply-to: gentoo-alpha@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <1A3BFBC6-CD85-4664-B66F-59063E372B3B@ifom-ieo-campus.it> User-Agent: Mutt/1.5.13 (2006-08-11) Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by robin.gentoo.org id l4EFNAHB018268 X-Archives-Salt: 0dcb441d-ad1c-4e8c-b9f6-75938d1bd9e4 X-Archives-Hash: 59d4e39f14b004135d6f07525c22eff9 On Mon, May 14, 2007 at 02:57:08PM +0200, Davide Cittaro wrote: > Hi all again! I'm sorry for this but I would like to give you an =20 > update on what's happening here. > I've done with gcc emerging, at least. I had to compile and install =20 > it manually, add a proper /etc/env.d/gcc config file, let gcc-config =20 > select the new gcc-4.1.1 and then reemerge it. It seems to work fine. =20 > I can go on with emerging an updated system, I hope. >=20 > BTW, I'm courious: how many people in this list have a DS25 or at =20 > least an ev68 processor? It seems we are very few people and it is =20 > hard to fix errors... >=20 Couple of things here.. First, adding -Wa,-mev6 to CFLAGS and CXXFLAGS is definitely not needed and I would expect it break a few things personally. Second, I've been using gcc-4.1.1-r3 for months on EV68 system(s) with no problem at all. I'm maintaining all the toolchain stuff on alpha as so far testing and keywording goes and I do most of my work on a CS20 (dual ev68AL so fairly close to your DS25 regarding specs). I haven't seen any gcc related problems personally. So I expect your problems either stems from your CFLAGS or perhaps from glibc that. Which version of glibc are you using and what USE flags are enabled? Regards, Bryan =C3=98stergaard --=20 gentoo-alpha@gentoo.org mailing list