On Wed, 13 Jan 2016 12:03:06 +, Ankur Sinha wrote:
> Hiya,
>
> The subtitleeditor package seems to require C++11 enabled to build.
> Here's an error in the mock log[1] for the latest failed build[2] for
> example:
>
> /usr/include/glibmm-2.4/glibmm/error.h:41:20: note: C++11 'noexcept'
>
Hiya,
The subtitleeditor package seems to require C++11 enabled to build.
Here's an error in the mock log[1] for the latest failed build[2] for
example:
/usr/include/glibmm-2.4/glibmm/error.h:41:20: note: C++11 'noexcept'
only available with -std=c++11 or -std=gnu++11
Can I enable C++11 to get
On Wed, 2016-01-13 at 13:08 +0100, Michael Schwendt wrote:
> Yes.
Thanks Michael. Follow up question:
What is the cleanest way of doing this - replacing -ansi with
-std=c++11 in %{_optflags} while using the %configure macro?
--
Thanks,
Regards,
Ankur Sinha "FranciscoD"
On 13/01/16 15:36 +0100, Kalev Lember wrote:
Also, GCC 6 that is going to land in F24 in 2 or 3 weeks is going to
switch the global default to -std=gnu++14 or -std=c++14, I've forgotten
which.
gnu++14
Currently the default is gnu++98, so we're only changing 98 -> 14, not
c++ -> gnu++ (i.e.
On 01/13/2016 03:21 PM, Björn Esser wrote:
Am 13.01.2016 um 15:06 schrieb Ankur Sinha:
On Wed, 2016-01-13 at 13:08 +0100, Michael Schwendt wrote:
Yes.
Thanks Michael. Follow up question:
What is the cleanest way of doing this - replacing -ansi with
-std=c++11 in %{_optflags} while using the
Am 13.01.2016 um 15:06 schrieb Ankur Sinha:
On Wed, 2016-01-13 at 13:08 +0100, Michael Schwendt wrote:
Yes.
Thanks Michael. Follow up question:
What is the cleanest way of doing this - replacing -ansi with
-std=c++11 in %{_optflags} while using the %configure macro?
You can do it the
