Opened 10 years ago

Closed 3 years ago

#46826 closed defect (fixed)

inkscape @0.91_1 fails building on 10.5.8 PPC

Reported by: udbraumann Owned by: dbevans (David B. Evans)
Priority: Normal Milestone:
Component: ports Version: 2.3.3
Keywords: Cc: su-v, cooljeanius (Eric Gallager)
Port: inkscape

Description

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.

Attachments (1)

main.log.gz (25.5 KB) - added by udbraumann 10 years ago.

Download all attachments as: .zip

Change History (11)

Changed 10 years ago by udbraumann

Attachment: main.log.gz added

comment:1 Changed 10 years ago by mf2k (Frank Schima)

Cc: devans@… removed
Owner: changed from macports-tickets@… to devans@…

comment:2 Changed 10 years ago by su-v

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

comment:3 Changed 10 years ago by su-v

Cc: suv-sf@… added

Cc Me!

comment:4 in reply to:  3 ; Changed 10 years ago by 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.

comment:5 in reply to:  4 ; Changed 10 years ago by 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 due to ABI incompatibilities.

Version 0, edited 10 years ago by su-v (next)

comment:6 in reply to:  5 ; Changed 10 years ago by 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?

comment:7 in reply to:  6 Changed 10 years ago by 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).

comment:8 Changed 8 years ago by cesss

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

comment:9 Changed 3 years ago by cooljeanius (Eric Gallager)

Cc: cooljeanius added

comment:10 Changed 3 years ago by mascguy (Christopher Nielsen)

Resolution: fixed
Status: newclosed

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.

Note: See TracTickets for help on using tickets.