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 3B5B51391DB for ; Tue, 29 Jul 2014 16:29:03 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2CD49E092F; Tue, 29 Jul 2014 16:28:58 +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 4F48EE08EF for ; Tue, 29 Jul 2014 16:28:57 +0000 (UTC) Received: from mail-ig0-f172.google.com (mail-ig0-f172.google.com [209.85.213.172]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: floppym) by smtp.gentoo.org (Postfix) with ESMTPSA id 384AE340194 for ; Tue, 29 Jul 2014 16:28:56 +0000 (UTC) Received: by mail-ig0-f172.google.com with SMTP id h15so5770086igd.17 for ; Tue, 29 Jul 2014 09:28:54 -0700 (PDT) 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-Received: by 10.42.76.144 with SMTP id e16mr1660622ick.10.1406651334439; Tue, 29 Jul 2014 09:28:54 -0700 (PDT) Received: by 10.64.142.17 with HTTP; Tue, 29 Jul 2014 09:28:54 -0700 (PDT) In-Reply-To: <53CFF561.90508@gentoo.org> References: <53CFF561.90508@gentoo.org> Date: Tue, 29 Jul 2014 12:28:54 -0400 Message-ID: Subject: Re: [gentoo-dev] gcc-4.8 may be needed in stable for www-client/chromium-38.x From: Mike Gilbert To: Gentoo Dev Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: c0ae5e4c-6102-4354-9646-216f583cbd2d X-Archives-Hash: 8d36097f7c7c10577f6cd6a7a7407b73 On Wed, Jul 23, 2014 at 1:48 PM, "Pawe=C5=82 Hajdan, Jr." wrote: > Looks like www-client/chromium is going to start using c++11 seriously > and require gcc-4.8+, see thread > > > This is in the dev channel for now, but given the 6 weeks release cycle > it'll go to stable in about 3 months, and every time it's a security upda= te. > > I'm trying to get Gentoo prepared now, and so what are our chances to > get gcc-4.8 to stable by that time? > > Possible alternative solutions: > > 1. Depend on clang, and force the build to use it. Possible problem with > this is that since chromium uses very bleeding edge clang, this can put > some strain on our system clang just as well. > > 2. Patch chromium to make it compile with gcc-4.7. This is almost always > technically possible, but can be a maintainability burden, especially if > upstream doesn't accept some parts of the patches. Also, there are known > problem with chromium, c++11 and gcc-4.7 > ( > , although Gentoo is not affected by this one because we have newer dbus)= . > > WDYT? > A third option that comes from the chromium-packagers ML: 3. Download and use the pre-built clang binaries from the Chromium project. I know we frown upon bundled binaries. However, I think that's really more a problem if the bundled code is used at runtime; maybe it would be ok to utilize pre-built build tools? The same could be applied to the [p]nacl toolchains; if I recall correctly, we currently disable nacl due to problems creating these from source.