Bug#800371: glibmm2.4: C++11 features in headers but no -std=c++11 in pkg-config

Matthias Klose doko at debian.org
Tue Sep 29 14:43:07 UTC 2015

On 29.09.2015 13:47, Michael Biebl wrote:
> Am 28.09.2015 um 16:59 schrieb Aurelien Jarno:
>> Source: glibmm2.4
>> Version: 2.46.1-1
>> Severity: serious
>> glibmm2.4 version 2.46.1-1 started to use C++11 features in the headers
>> it exports, but pkg-config --cflags doesn't return -std=c++11. Given the
>> default is still -std=gnu++98 in GCC 5, it causes packages which use
>> these headers to fails to build.
>> A build log showing the issue can be found here:
>> https://buildd.debian.org/status/fetch.php?pkg=inkscape&arch=mips64el&ver=0.91-5%2Bb1&stamp=1443446208
> On IRC the question was raised, if random .pc files should really
> contain -std=... ?

the problem is that the new glibmm2.4 now requires c++11, while this package is 
still used in the old glibmm stack. So the proper solution would be to have your 
own glibmm package for the old stack, or have a c++98 mode for the new glibmm 
package. Does everything using the old glibmm stack uses pkg-config? If not 
you'll have to fix every client package anyway.

More information about the pkg-gnome-maintainers mailing list