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 1Hsgnm-0002LG-0B for garchives@archives.gentoo.org; Mon, 28 May 2007 15:06:30 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l4SF6GW4020576; Mon, 28 May 2007 15:06:16 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 l4SF6Fgw020571 for ; Mon, 28 May 2007 15:06:16 GMT Received: by smtp.gentoo.org (Postfix, from userid 739) id CD07064CE9; Mon, 28 May 2007 15:06:11 +0000 (UTC) Date: Mon, 28 May 2007 17:06:11 +0200 From: Bryan =?utf-8?Q?=C3=98stergaard?= To: gentoo-alpha@lists.gentoo.org Subject: Re: [gentoo-alpha] glibc 2.5+ Message-ID: <20070528150610.GK22162@woodpecker.gentoo.org> References: 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: 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 l4SF6GWJ020576 X-Archives-Salt: 1b5d5913-a446-40ac-bad6-5d0296aca673 X-Archives-Hash: 0c540b9ad07f32bb93a77f1073f0aa06 On Mon, May 28, 2007 at 04:01:15PM +0200, Davide Cittaro wrote: > Hi all, I've found that glibc 2.5+ cannot be compiled on my alpha, as =20 > reported on gentoo bugzilla by another person. >=20 > http://bugs.gentoo.org/show_bug.cgi?id=3D179353 >=20 > I have a couple of questions, then: > 1- it is safe to use '-nptlonly' flag? Not really. In the past we've found Linuxthreads to be unstable and nptlonly is much preferred for that reason (we had programs randomly crashing with Linuxthreads and no problems with NPTL). > 2- when the patched glibc will be available in portage (comment 2 of =20 > that bug has been posted one week ago)? As soon as glibc upstream fixes the problem. Meanwhile you have two different options. 1. Upgrade to binutils >=3D2.17.50.0.15 and risk possible unknown bugs from doing so. 2. Ignoring glibc-2.5 updates until upstream fixes the issue. My recommendation would be to wait and not try to work around the issue yourself. Regards, Bryan =C3=98stergaard --=20 gentoo-alpha@gentoo.org mailing list