On Fri, 2016-04-22 at 09:22 +0100, Russel Winder wrote: > On Mon, 2016-04-18 at 19:57 +0200, Murray Cumming wrote: > […] > > On debian, it's actually coming from the libsigc++ pkg-config file, > > as > > I think you'll find when you do this: > > $ pkg-config sigc++-2.0 --cflag > > > > They have done this against our wishes: > > https://bugzilla.gnome.org/show_bug.cgi?id=755750#c13 > > This has been marked as "resolved wontfix" so clearly they are > telling > everyone already using C++14 and C++17 to "shut up and put up", which > I > guess is not untypical.
That's our upstream bug. It's wontfix because we refused to put -std=c+=11 in the pkg-config file. But debian did it themselves anyway. > Currently, using SCons, I can edit the -std=c++11 out and add my own > -std=c++14, but using CMake things are far more awkward. > > > This is very much a distro-specific problem that you should > > complain > > to > > your distro about. Sorry. I am annoyed with them, not with you. > > Thanks > > for letting me know. > > I will add a bug to the Debian archive. It seems Fedora already work > around this somehow. Fedora just didn't do this. -- Murray Cumming murr...@murrayc.com www.murrayc.com _______________________________________________ gtkmm-list mailing list gtkmm-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtkmm-list
