From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 2BA7213838B for ; Tue, 23 Sep 2014 13:34:08 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 83477E09AB; Tue, 23 Sep 2014 13:34:02 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 7EE5AE0807 for ; Tue, 23 Sep 2014 13:34:01 +0000 (UTC) Received: from [192.168.1.100] (c-68-49-223-78.hsd1.md.comcast.net [68.49.223.78]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mjo) by smtp.gentoo.org (Postfix) with ESMTPSA id 3AD4B33EAEC for ; Tue, 23 Sep 2014 13:34:00 +0000 (UTC) Message-ID: <542176B9.8080100@gentoo.org> Date: Tue, 23 Sep 2014 09:33:45 -0400 From: Michael Orlitzky User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.8.0 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 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] "stack-protector-strong" option results in gcc error References: <20140923024941.GA2848@waltdnes.org> <20140923085403.GA4540@waltdnes.org> In-Reply-To: <20140923085403.GA4540@waltdnes.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: d4c3780c-9307-445c-9db3-d3de60525b73 X-Archives-Hash: 17331df8bffaa034bdc3292609427ae1 On 09/23/2014 04:54 AM, Walter Dnes wrote: > > Gentoo stable appears to be gcc-4.7.3-r1. ebuilds up to gcc-4.9.1 are > present in the tree. Upgrading gcc is painful, so I appreciate the > maintainers not forcing a rebuild with every version bump. That's the > philosophy behind "stable". The tradeoff is that we have to wait longer > for "new and shiney" stuff. For those who want it, you can always > keyword a later version of gcc. > Stabilization of GCC is especially careful because if your GCC winds up broken, you might not be able to fix it (emerge won't work). And since GCC is used to build everything else on your system, it can't go stable until all upstream packages are fixed or patched to work with the new GCC. There's usually a tracker for those packages. For gcc-4.9 it's at, https://bugs.gentoo.org/show_bug.cgi?id=gcc-4.9