inkscape-bzr, inkscape-gtk3-bzr build fails (Arch Linux)

[Stefan Husmann]

Under Arch Linux 64 bit the build fails with the attached output.

gtk3 is at 3.18.1.r36.g22b0ed6-1 from git.

[su_v (suv-lp)]

Please try to compile with '-std=c++11' added to CXXFLAGS.

Likely related to the same underlying issue as tracked in bug #1488079 (upstream latest C++ bindings having switched to C++11).

[Stefan Husmann (stefan-husmann)]

I tried that now, same error.

[su_v (suv-lp)]

Could you please attach the log of a recent build which was attempted with '-std=c++11' added to CXXFLAGS?

[Stefan Husmann (stefan-husmann)]

Sure. I attached it.

[Stefan Husmann (stefan-husmann)]

Happens also without gtk3 enabled.

[su_v (suv-lp)]

AFAICT neither of the builds of the last two logs actually use c++11 - how exactly did you attempt to add '-std=c++11' to $CXXFLAGS?

The stable Inkscape package for Archlinux seems to have switched to c++11 on Sept 29:
https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/inkscape&id=e69a9bc328780e5a18c8a91f5df9ff6fa4975dc5

[Stefan Husmann (stefan-husmann)]

I use

CXXFLAGS="`pkg-config --cflags glib` -fPIC -std=c++11" make

[su_v (suv-lp)]

The build logs have:
for GTK2:
        CXXFLAGS: -Wpointer-arith -Wcast-align -Wsign-compare -Woverloaded-virtual -Wswitch -Wno-unused-parameter -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong --param=ssp-buffer-size=4
for GTK3:
        CXXFLAGS: -Wpointer-arith -Wcast-align -Wsign-compare -Woverloaded-virtual -Wswitch -Wno-unused-parameter -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong --param=ssp-buffer-size=4

no '-std=c++11' there.

[Stefan Husmann (stefan-husmann)]

I solved the problem by setting CXXFLAGS+=" -std=c++1' globally in the build function, not just in the invokation of make.

[su_v (suv-lp)]

Thank you for investigating further, and reporting back.

We are aware of the problem, and working on a solution to set the required flag(s) within the build system automatically, see also comment 6 in bug #1488079.