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 1Q7Hhi-0000yY-J9 for garchives@archives.gentoo.org; Wed, 06 Apr 2011 01:38:42 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 79EBF1C10F; Wed, 6 Apr 2011 01:38:33 +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 8A2E11C009 for ; Wed, 6 Apr 2011 01:38:04 +0000 (UTC) Received: by wwj40 with SMTP id 40so1105111wwj.10 for ; Tue, 05 Apr 2011 18:38:03 -0700 (PDT) Received: by 10.227.7.18 with SMTP id b18mr354029wbb.103.1302053883026; Tue, 05 Apr 2011 18:38:03 -0700 (PDT) Received: from [172.28.64.145] (host249-252-static.95-94-b.business.telecomitalia.it [94.95.252.249]) by mx.google.com with ESMTPS id b20sm37500wbb.16.2011.04.05.18.37.58 (version=SSLv3 cipher=OTHER); Tue, 05 Apr 2011 18:38:02 -0700 (PDT) Sender: =?UTF-8?Q?Diego_Elio_Petten=C3=B2?= Subject: [gentoo-dev] Re: GCC 4.6.0 From: Diego Elio =?ISO-8859-1?Q?Petten=F2?= To: gentoo-dev@lists.gentoo.org In-Reply-To: <20110402221112.2101b4c1@gentoo.org> References: <20110402221112.2101b4c1@gentoo.org> Content-Type: text/plain; charset="UTF-8" Date: Wed, 06 Apr 2011 03:37:55 +0200 Message-ID: <1302053875.2330.83.camel@raven.home.flameeyes.eu> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: X-Archives-Hash: 4a01810497eae26ef099f955977f6e23 Il giorno sab, 02/04/2011 alle 22.11 -0600, Ryan Hill ha scritto: > Common errors: I've been running my tinderbox with GCC 4.6 now, so I hope to help out discovering the issue asap, but in the mean time I'd like to point out that GCC 4.6 (a little more than others, afaict) could cause ./configure scripts to fail (or misdetect availability of functions). If something does not seem to build right, but doesn't appear directly related to GCC 4.6, make sure to attach the config.log of the configure execution. In particular, since with GCC 4.5 (and modern glibc) doing things such as write(fd, buf, bufsize); would have caused "return value ignored" warnings, which would have thrown off detections using -Werror, they were rewritten as int n =3D write(fd, buf, bufsize); ... too bad that this *now* causes the "unused but set" warning. --=20 Diego Elio Petten=C3=B2 =E2=80=94 Flameeyes http://blog.flameeyes.eu/