Kalev Lember wrote:
> The fix is simple: make sure -std=c++11 is passed to the compiler.
The default is gnu++98, so if you were using the default, you probably want
gnu++11 instead. c++11 is strict C++11 without GNU extensions.
Kevin Kofler
--
devel mailing list
devel@lists.fedoraproje
On 09/23/2015 02:56 AM, Josh Stone wrote:
> On 09/22/2015 05:49 PM, Mamoru TASAKA wrote:
>> Rather, can't be pkgconfig file in gtkmm30 modified for now to add -std=c++11
>> to Cflags?
>
> I'd guess that they really require *at least* c++11.
>
> A project might instead choose gnu++11, c++14, gnu++
On 09/22/2015 05:49 PM, Mamoru TASAKA wrote:
> Kalev Lember wrote on 09/23/2015 09:35 AM:
>> Hi,
>>
>> A quick heads up to anybody who might run into cryptic build errors when
>> building apps that use glibmm/gtkmm:
>>
>> Latest glibmm/gtkmm stack in rawhide and F23 now uses C++11 features in
>> he
Kalev Lember wrote on 09/23/2015 09:35 AM:
Hi,
A quick heads up to anybody who might run into cryptic build errors when
building apps that use glibmm/gtkmm:
Latest glibmm/gtkmm stack in rawhide and F23 now uses C++11 features in
header files. This means when building other programs that use tho
Hi,
A quick heads up to anybody who might run into cryptic build errors when
building apps that use glibmm/gtkmm:
Latest glibmm/gtkmm stack in rawhide and F23 now uses C++11 features in
header files. This means when building other programs that use those
headers, the C++ compiler needs to be in C
