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 6EDCB138A2F for ; Thu, 24 Jul 2014 22:31:13 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B0DB7E0C1E; Thu, 24 Jul 2014 22:30:23 +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 9AD31E0BB0 for ; Thu, 24 Jul 2014 22:30:16 +0000 (UTC) Received: from phjr-macbookpro.local (87-205-244-98.adsl.inetia.pl [87.205.244.98]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: phajdan.jr) by smtp.gentoo.org (Postfix) with ESMTPSA id 00FF6340960 for ; Wed, 23 Jul 2014 17:48:39 +0000 (UTC) Message-ID: <53CFF561.90508@gentoo.org> Date: Wed, 23 Jul 2014 19:48:17 +0200 From: =?UTF-8?B?IlBhd2XFgiBIYWpkYW4sIEpyLiI=?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 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 To: gentoo-dev@lists.gentoo.org Subject: [gentoo-dev] gcc-4.8 may be needed in stable for www-client/chromium-38.x X-Enigmail-Version: 1.6 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="neCwaKXdRRH50Bl0q6KB8QkErh4c1B0cM" X-Archives-Salt: a70ddbbc-282a-4944-bb5e-ef29214956ea X-Archives-Hash: 92d455d436b3289177002f34968cba89 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --neCwaKXdRRH50Bl0q6KB8QkErh4c1B0cM Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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)= =2E WDYT? Pawe=C5=82 --neCwaKXdRRH50Bl0q6KB8QkErh4c1B0cM Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQIcBAEBCgAGBQJTz/VsAAoJEE8aJVXqcZkdzJoP/0bs7KGTXOLA2ZkserDvaHyl LOFJe0iDQg0z0Ehd8dERnSIiCW/+qYABYXBibcMxMbV20eYS54s77fm64AO51mdK 871zChpWVdDPoz99vkkytRMj7aE9bo2ICAJrmpqk7/6rYfaUVYYDL+vHvQjbvmx5 kDNUJvuWgYcq5MViEtKcZysXvPoD0al/JfVw+e51c06FoNPOgM9fvkRCNjRh+CTd fAIcJmUv2YctCI/l4CHU4TNKjP7hqkiEfnr+w8y1v1Zi2DDhyXR4n+ZoGM/IQSww tK8mC8oUsIC2LtNmzg/lFoXf0WWyKtV6uvcSsXWIoNs4mxuDwIoYySUP/voDKlIe aztpmT2NQxhBNVuO0DwC/bb7QjpuP5Gm7Lswt9La+pwQpzN9v715ffiwYo6BVbKn e7s7zuCZzKvQ+toMTdvg2Z3QjgtAae9jiy+syrUIAMV7ZFmR3lJtag1lLuVoMEVb wH1AyFWokWERX+RkH6iSEvmeThxjNsVIGaK57QuSVqk6C4GsGgOkR0rHnPVzSE2Q 3Nt1z4meRdNssvH5tDJB2Y5XjQaEww1K51ML0q2kkpU17oMwSovb8URgB9G/axEy zS7uleKZvRBkQv+PNROiFC+Fo7ZWwU3+3M22kDLcesTUTcjjaFmmUeWg5HxH58wq F1nG88KyviF+Y0pp/3e1 =ruE1 -----END PGP SIGNATURE----- --neCwaKXdRRH50Bl0q6KB8QkErh4c1B0cM--