inkscape @0.91_1 fails building on 10.5.8 PPC

[udbraumann]

Building stops issuing this:

:info:build 2geom/solve-bezier-parametric.cpp: In function ‘void Geom::find_parametric_bezier_roots(const Geom::Point*, unsigned int, std::vector<double, std::allocator<double> >&, unsigned int)’:
:info:build 2geom/solve-bezier-parametric.cpp:77: error: ‘class std::vector<Geom
::Point, std::allocator<Geom::Point> >’ has no member named ‘data’
:info:build 2geom/solve-bezier-parametric.cpp:77: error: ‘class std::vector<Geom
::Point, std::allocator<Geom::Point> >’ has no member named ‘data’
:info:build 2geom/solve-bezier-parametric.cpp:79: error: ‘class std::vector<Geom
::Point, std::allocator<Geom::Point> >’ has no member named ‘data’
:info:build 2geom/solve-bezier-parametric.cpp:80: error: ‘class std::vector<Geom
::Point, std::allocator<Geom::Point> >’ has no member named ‘data’
:info:build make[3]: *** [2geom/solve-bezier-parametric.o] Error 1
:info:build make[3]: Leaving directory `/Volumes/Data/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_inkscape/inkscape/work/inkscape-0.91/src'

As far as I can see, gcc version 4.2.1 (Apple Inc. build 5577) residing under /usr/bin is being used.

[su-v]

Upstream report (with patch to compile 0.91 on Mac OS X 10.5.8 - only tested with i386 though):

• ​Bug #1362240: build failure on OS X 10.5 “Leopard"

[su-v]

Cc Me!

[udbraumann]

I did a

sudo port clean inkscape

followed by a

sudo port upgrade inkscape configure.compiler=macports-gcc-4.9

and now building completed successfully.

However, inkscape @0.91_1 reproducibly crashes just during startup:

$ inkscape
inkscape(43873) malloc: *** error for object 0xa02a67a8: Non-aligned pointer being freed
*** set a breakpoint in malloc_error_break to debug
inkscape(43873) malloc: *** error for object 0xa02a67a8: Non-aligned pointer being freed
*** set a breakpoint in malloc_error_break to debug
inkscape(43873) malloc: *** error for object 0xa02a67a8: Non-aligned pointer being freed
*** set a breakpoint in malloc_error_break to debug
inkscape(43873) malloc: *** error for object 0xa02a67a8: Non-aligned pointer being freed
*** set a breakpoint in malloc_error_break to debug
inkscape(43873) malloc: *** error for object 0xa02a67a8: Non-aligned pointer being freed
*** set a breakpoint in malloc_error_break to debug
inkscape(43873) malloc: *** error for object 0xa02a67a8: Non-aligned pointer being freed
*** set a breakpoint in malloc_error_break to debug
inkscape(43873) malloc: *** error for object 0xa02a67a8: Non-aligned pointer being freed
*** set a breakpoint in malloc_error_break to debug
inkscape(43873) malloc: *** error for object 0xa02a67a8: Non-aligned pointer being freed
*** set a breakpoint in malloc_error_break to debug
inkscape(43873) malloc: *** error for object 0xa02a67a8: Non-aligned pointer being freed
*** set a breakpoint in malloc_error_break to debug
inkscape(43873) malloc: *** error for object 0xa02a67a8: Non-aligned pointer being freed
*** set a breakpoint in malloc_error_break to debug
inkscape(43873) malloc: *** error for object 0xa02a67a8: Non-aligned pointer being freed
*** set a breakpoint in malloc_error_break to debug
inkscape(43873) malloc: *** error for object 0xa02a67a8: Non-aligned pointer being freed
*** set a breakpoint in malloc_error_break to debug
inkscape(43873) malloc: *** error for object 0xa02a67a8: Non-aligned pointer being freed
*** set a breakpoint in malloc_error_break to debug

(inkscape:43873): GLib-GObject-WARNING **: gvalue.c:181: cannot initialize GValue with type 'guint', the value has already been initialized as '(null)'

Emergency save activated!
Emergency save completed. Inkscape will close now.
If you can reproduce this crash, please file a bug at www.inkscape.org
with a detailed description of the steps leading to the crash, so we can fix it.

[su-v]

Replying to braumann@…:

followed by a

sudo port upgrade inkscape configure.compiler=macports-gcc-4.9

If you want to compile a C++ application with a custom compiler (i.e. not a system compiler), you would have to make sure that at least all linked C++ libraries (glibmm, atkmm, pangomm, cairomm, gtkmm, etc, and probably also ImageMagick) are compiled with the same one, else the application will crash (or be highly unstable) due to ABI incompatibilities.

[udbraumann]

Admittedly, I never have run into such ABI incompatibilities. Excuse my naive question, but are these by intention, or just by chance? There are quite a few non-system compilers available, so using some of them occasionally when building ports necessarily will lead to unstable configurations?

[su-v]

Replying to braumann@…:

Admittedly, I never have run into such ABI incompatibilities. Excuse my naive question, but are these by intention, or just by chance? There are quite a few non-system compilers available, so using some of them occasionally when building ports necessarily will lead to unstable configurations?

These ABI incompatibilities are not specific to the software this report is about (and certainly not intentionally introduced by the Inkscape developers) - search the MacPorts' mailing lists, it's a recurring topic for C++ projects in MacPorts. Anyhow - I'll let this be handled by the maintainer of Inkscape in MacPorts (as mentioned in my initial comment, there is a patch available upstream for Leopard's compiler (gcc-4.2); whether it works or not or is sufficient for PPC arch is unknown - it has only been tested on i386-based 10.5.8 systems).

[cesss]

I can confirm that the patch available upstream makes Inkscape 0.91 compile successfully on PPC Tiger.

[mascguy (Christopher Nielsen)]

Since this port has now been updated to 1.1.2, please let us know if this is still an issue.

If so, we'll reopen.