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 <gentoo-user+bounces-139446-garchives=archives.gentoo.org@lists.gentoo.org>)
id 1SjvI6-0001qX-25
for garchives@archives.gentoo.org; Wed, 27 Jun 2012 16:40:30 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 19C48E0534;
Wed, 27 Jun 2012 16:40:09 +0000 (UTC)
Received: from mail-lb0-f181.google.com (mail-lb0-f181.google.com [209.85.217.181])
by pigeon.gentoo.org (Postfix) with ESMTP id BB22EE083B
for <gentoo-user@lists.gentoo.org>; Wed, 27 Jun 2012 16:38:37 +0000 (UTC)
Received: by lbbgk8 with SMTP id gk8so1942860lbb.40
for <gentoo-user@lists.gentoo.org>; Wed, 27 Jun 2012 09:38:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=mime-version:sender:in-reply-to:references:from:date
:x-google-sender-auth:message-id:subject:to:content-type;
bh=0SZzHjowoHvGTkdychh2xXhWOa6Rw1m/CeYzhbB5AiM=;
b=WnMCWyLnOJcGeq/f5l/vu9WnWzUcoLnMnTxNODajuzuskcEkz/SU0lT5g1u/d78iNW
CYGIpTy5mQKobk3QGSIgBwWIYT6EsZ9IIgP+Ni8KzBiCznfSMkPWczvOGIY44Xcy6WtE
zO0+4FWvgH/tk9F0iXR8M0di0vxGWOPBfM8zJNTe973Mdubob4ilXxVQjp2VsiUnuFEN
nNoBwpyjtm3lcEyOyZ7Hj5NBbM5pBsCk8wPJtHeVxtK5sQ/jCiku3cMHtRG/nTU4s5JC
YYJda0VROqmWZh31yXfWPGrVncR5H7Fo2yoBnUBk2lE6FkNDOy7s5dnx+6KKmIunYWrC
v4VA==
Received: by 10.112.36.132 with SMTP id q4mr9922276lbj.63.1340815116607; Wed,
27 Jun 2012 09:38:36 -0700 (PDT)
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
Sender: paul.hartman@gmail.com
Received: by 10.112.77.4 with HTTP; Wed, 27 Jun 2012 09:38:16 -0700 (PDT)
In-Reply-To: <CA+czFiAHP4nKasZZ=pa9OoURwvUR+b59PZG+Bek-BK_XYExr2g@mail.gmail.com>
References: <CA+czFiDVxnHPYAGmr7cpudyZE-g9p=iLaRCCutv7H_AteJkh1w@mail.gmail.com>
<CAK2H+eeWdtx8S5DOU3uF92qvb-m4EVtN4_x=9Hov8t2abVD1SQ@mail.gmail.com>
<CA+czFiAsW0+7=4zFjekZjyTPX8kAVLx1g5OSXqDsGBV8Pke6FA@mail.gmail.com>
<CAC=wYCG0Nfh1zth+ZNpD464gM2E+fJ-UXQtA6r+Ex3vOFjAb7g@mail.gmail.com>
<CA+czFiCcVi54B6dgvmzqcR-HMWTFumjXnsvm8bp9wvtOmaRomg@mail.gmail.com>
<CAA2qdGXffqw4gpY1UpKJbM_VghX0XRrEybyXtmc33LksVpUU-w@mail.gmail.com>
<CA+czFiC5ZEo3k0hnFVpL4P6dUeYRB9sX6CRmm4CTAwKP-m_VGA@mail.gmail.com>
<CAA2qdGXHaEA8khehqTbpNrqnJaWAqhbdOq67VQ-2fc2Wceo=Rw@mail.gmail.com>
<CA+czFiAaxkGRY-6dsj_7BRL+xarrxAwr3bR3C4eNeRqCx0fv=A@mail.gmail.com>
<CA+czFiCuQPJVWo7LpnfaD6zr4WAaOnTGL9TCQeYmnvYhk6tZrQ@mail.gmail.com>
<20120603033410.GC12597@madrid> <CA+czFiB3nvcUTUh7-LRapQ0v_OHWTnL=S=AY5k__XYNXvvO0Cw@mail.gmail.com>
<CA+czFiDFt3eefK2jrSA=m5V9tonk__LRV32eXv22M6ET5=1Kiw@mail.gmail.com>
<CA+czFiBqupYV_RqSPyH4KQ+PHPxxbdA1K7GAL5zz0LYmJksodw@mail.gmail.com> <CA+czFiAHP4nKasZZ=pa9OoURwvUR+b59PZG+Bek-BK_XYExr2g@mail.gmail.com>
From: Paul Hartman <paul.hartman+gentoo@gmail.com>
Date: Wed, 27 Jun 2012 11:38:16 -0500
X-Google-Sender-Auth: Tj5xw04YAEQ-BxTiUbtldC11c1I
Message-ID: <CAEH5T2MQcaARo6mQ3gkUHC3id2MYD1bmQWyCtQ6GL06_waVT9w@mail.gmail.com>
Subject: Re: [SOLVED] Re: [gentoo-user] Just a heads-up, I think
=sys-libs/glibc-2.14.1-r3 is a stinker.
To: gentoo-user@lists.gentoo.org
Content-Type: text/plain; charset=ISO-8859-1
X-Archives-Salt: fd0a3cb6-bc3e-4ea2-967c-194c3b078aef
X-Archives-Hash: 94a6867da8b828af2cc910309589d7db
On Wed, Jun 27, 2012 at 8:58 AM, Michael Mol <mikemol@gmail.com> wrote:
> On Sat, Jun 23, 2012 at 6:08 PM, Michael Mol <mikemol@gmail.com> wrote:
>> https://bugs.gentoo.org/show_bug.cgi?id=423149
>
> As it turned out, it was my CFLAGS. Not the ones anyone usually cares
> about, either.
>
> If you build glibc with CFLAGS="${CFLAGS} -g3", your glibc will be
> very, very broken. Apparently, it's old, known and has been a problem
> for about five years.
Thanks for posting this follow-up, I never would have guessed the
additional debug info could cause such problems.