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 4FD40138247 for ; Thu, 19 Dec 2013 15:23:16 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 21464E0BE6; Thu, 19 Dec 2013 15:23:11 +0000 (UTC) Received: from latimerie.flaska.net (latimerie.flaska.net [46.28.111.182]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 22D97E0BD3 for ; Thu, 19 Dec 2013 15:23:10 +0000 (UTC) Received: by latimerie.flaska.net (Postfix, from userid 1000) id D9DB760408; Thu, 19 Dec 2013 16:23:07 +0100 (CET) From: =?iso-8859-1?Q?Jan_Kundr=E1t?= To: Subject: Re: [gentoo-dev] How to support C++11 in =?iso-8859-1?Q?libraries=3F?= Date: Thu, 19 Dec 2013 16:23:08 +0100 User-Agent: Trojita/v0.3.96-154-gef050ca; Qt/4.8.5; X11; Linux; 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 Message-ID: In-Reply-To: <52B309FD.60208@gentoo.org> References: <20131218085447.56d1e133@gentoo.org> <6224179.BWgg760IdH@sed-notebook> <20131219100731.026a498e@gentoo.org> <52B309FD.60208@gentoo.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Archives-Salt: c0fc27b3-3a79-44e4-9a3c-e2ba2deec46c X-Archives-Hash: ab4ad067d55c76f284a5ceb94d4a6e8b On Thursday, 19 December 2013 16:00:13 CEST, Ian Stakenvicius wrote: > A change in profiles? 14.0/* adds that to the default CXXFLAGS in > base, new stage3's etc are all rolled with this. We recommend > migration to 14.0 profile and have a check somewhere about > "-std=3Dc++11" missing from CXXFLAGS in case it's overridden in > make.conf, so users put it in place? Before you invest any more time in this, please understand that C++98 and=20 C++11 are source-incompatible. There is no way to expect that a package=20 builds fine when you throw -std=3Dc++11 on it. And even if you patched them=20= all, you are breaking an unknown number of 3rd party software over which=20 you have exactly zero control. Also note that as of gcc 4.8, the C++11 support is still labeled as=20 experimental and upstream developers announced they will introduce ABI=20 breaks in future. With kind regards, Jan