Re: Compiling and options

Thanks, both! So it wasn't my other package causing it, at least :-) If nothing else, it's news to me that people seemingly expect GCC 6 to hit Debian testing soon... We'll see how well that works out.

For now, I'll keep hacking around their hack! Maybe add some grumblings to their bugtracker later.

Thanks again

On Mon, Apr 18, 2016 at 6:57 PM, Murray Cumming <murrayc murrayc com> wrote:
On Mon, 2016-04-18 at 17:37 +0100, Russel Winder wrote:
> This appears to be just a Debian Sid thing, it does not happen with
> Fedora Rawhide or OSX/MacPorts.
> > > pkg-config glibmm-2.4 --cflags
> -std=c++11 -I/usr/include/glibmm-2.4 -I/usr/lib/x86_64-linux-
> gnu/glibmm-2.4/include -I/usr/include/glib-2.0 -I/usr/lib/x86_64
> -linux-
> gnu/glib-2.0/include -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64
> -linux-
> gnu/sigc++-2.0/include
> > > pkg-config gtkmm-3.0 --cflags
> -std=c++11 -pthread -I/usr/include/gtkmm-3.0 -I/usr/lib/x86_64-linux-
> gnu/gtkmm-3.0/include -I/usr/include/atkmm-1.6 -I/usr/include/gtk-
> 3.0/unix-print -I/usr/include/gdkmm-3.0 -I/usr/lib/x86_64-linux-
> gnu/gdkmm-3.0/include -I/usr/include/giomm-2.4 -I/usr/lib/x86_64
> -linux-
> gnu/giomm-2.4/include -I/usr/include/pangomm-1.4 -I/usr/lib/x86_64-
> linux-gnu/pangomm-1.4/include -I/usr/include/glibmm-2.4
> -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/gtk-3.0
> -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0
> -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include
> -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/
> -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz
> -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo
> -I/usr/include/cairomm-1.0 -I/usr/lib/x86_64-linux-gnu/cairomm-
> 1.0/include -I/usr/include/cairo -I/usr/include/pixman-1
> -I/usr/include/freetype2 -I/usr/include/libpng16
> -I/usr/include/sigc++-
> 2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/include/gdk
> -
> pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/glib-2.0
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include

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:

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.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]