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 1OnAVr-0000TV-Bx for garchives@archives.gentoo.org; Sun, 22 Aug 2010 13:23:03 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5F046E07F7; Sun, 22 Aug 2010 13:22:57 +0000 (UTC) Received: from mx.virtyou.com (mx.virtyou.com [94.23.166.77]) by pigeon.gentoo.org (Postfix) with ESMTP id 309B8E07F7 for ; Sun, 22 Aug 2010 13:22:57 +0000 (UTC) Received: from weird.localnet (p4FF041DA.dip.t-dialin.net [79.240.65.218]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.virtyou.com (Postfix) with ESMTPSA id D59C839A001 for ; Sun, 22 Aug 2010 15:22:56 +0200 (CEST) From: Alex Schuster To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] glibc 2.12.1-r1 seems to not be working correctly Date: Sun, 22 Aug 2010 15:22:54 +0200 User-Agent: KMail/1.13.5 (Linux/2.6.34-tuxonice-r2; KDE/4.5.0; x86_64; ; ) References: <17550.1282481535@ccs.covici.com> In-Reply-To: <17550.1282481535@ccs.covici.com> 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 Message-Id: <201008221522.55162.wonko@wonkology.org> Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit X-Archives-Salt: 90d4120c-365a-4efb-8f5b-ccafcd0adf4c X-Archives-Hash: 4f74d59720b5774f314c57b8d8b0d068 covici@ccs.covici.com writes: > Hi. I am running the unstable gentoo 32-bit and today I emerged -- > amoung other packages in a system update -- glibc-2.12.1-r1, however > after doing this at least one package had an undefined reference to > S_ISCHR. I tried to downgrade glibc, but apparently this is not > supported and I am a bit stumped as to how to fix this problem. Looks like a real bad problem, I'm glad I did not update yet. http://blog.flameeyes.eu/2010/08/18/compounded-issues-in-glibc-2-12 has some explanation on this. I wonder how this glibx version did make it into ~arch. > Any ideas on this would be appreciated. Don't know. Maybe wait a little and see if another new glibc fixes this, or the packages having issues with the new glibc might get updated. Wonko