Am 29.09.2015 um 16:43 schrieb Matthias Klose: > 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.
Not quite sure what you mean by that. 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. I would guess most 3rd party packages using gtkmm*/glibmm*/libsigc++-* are using pkg-config. I don't think having two versions of the mm* packages is practical/maintainable. That said, we have over 100 packages which build-depend on the mm stack. Most of them will probably ftbfs now. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
