Inkscape (0.48.4) fails to build with gtkmm 2.24.3

[Boltzmann]

On a mac osx 10.6.8 system the nstallation of inkscape @0.48.4 (or upgrade from previuos version) fails in a MacPorts base version 2.1.3 (recently upgraded)

The error message is
Error: org.macports.build for port inkscape returned: command execution failed
Please see the log file for port inkscape for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_inkscape/inkscape/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets

I had a quick view on the MacPorts bug-tracking system and decided to post the bug here, because they usually want it to be posted to the developers. Inkscape was working well (thanks!) until I upgraded my MacPorts system.

The output of /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_inkscape/inkscape/main.log is attached.

[su_v (suv-lp)]

> fails in a MacPorts base version 2.1.3 (recently upgraded)

Probably due to MacPorts' upgrading to gtkmm 2.24.3:
<https://lists.macosforge.org/pipermail/macports-changes/2013-April/089672.html>

AFAICT this is a known upstream regression in gtkmm 2.24.3:
- 697835 – gtkmm-2.24.3 breaks multiple reverse dependencies
  <https://bugzilla.gnome.org/show_bug.cgi?id=697835>

IMHO it would be better to report this for MacPorts instead of Inkscape.

[su_v (suv-lp)]

Related thread on the gtkmm mailing list:
<http://thread.gmane.org/gmane.comp.gnome.gtkmm/26896/focus=26897>

[su_v (suv-lp)]

MacPorts ticket:
[MacPorts] 38886: gtkmm 2.24.3 breaks multiple dependents
<https://trac.macports.org/ticket/38886>

[Boltzmann (stefan-bollmann)]

It seems, the gtkmm people did their job!

[su_v (suv-lp)]

Reopening - the report will be closed as 'Invalid' for project Inkscape once a newer gtkmm version has been released.

[Alex Valavanis (valavanisalex)]

We can work around this by disabling the G_DISABLE_DEPRECATED flag if gtkmm-2.24.3 is detected.

[Samuel Chase (samebchase)]

So, in the meantime trunk will build on Arch by disabling that flag?

Which lines in configure.ac should be (temporarily) modified?

[Alex Valavanis (valavanisalex)]

Hi Samuel,

Before modifying configure.ac, try

configure --enable-strict-build=no

If that fixes the problem, then I'll go ahead with a patch to automatically disable strict building if the broken version of gtkmm is found.

AV

[Alex Valavanis (valavanisalex)]

Here's a possible patch to allow deprecated glib symbols if the broken gtkmm version is detected. Because I can't reproduce the bug myself, I'll need someone else to test this!

[Samuel Chase (samebchase)]

Sorry! Just saw this. I'll test and report what happens.

[Samuel Chase (samebchase)]

Doing a --enable-strict-build=no results in the same error. WIll try the patch now.

[Samuel Chase (samebchase)]

Looks like the same errors after the patch.

[Samuel Chase (samebchase)]

Any other things I can try doing?

What if I install an older version of gtkmm until an upstream fix for this is released?

[Xavier Fung (xavier114fch)]

Same errors from bug#1181928 after updating trunk to the latest revision.

[Samuel Chase (samebchase)]

Nice. Can't wait to test this fix.

On 6/29/13, Bug Watch Updater <email address hidden> wrote:
> ** Changed in: gtkmm
> Status: New => Fix Released
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1171147
>
> Title:
> Inkscape (0.48.4) fails to build with gtkmm 2.24.3
>
> Status in gtkmm:
> Fix Released
> Status in Inkscape: A Vector Drawing Tool:
> In Progress
>
> Bug description:
> On a mac osx 10.6.8 system the nstallation of inkscape @0.48.4 (or
> upgrade from previuos version) fails in a MacPorts base version 2.1.3
> (recently upgraded)
>
> The error message is
> Error: org.macports.build for port inkscape returned: command execution
> failed
> Please see the log file for port inkscape for details:
>
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_inkscape/inkscape/main.log
> To report a bug, follow the instructions in the guide:
> http://guide.macports.org/#project.tickets
>
>
> I had a quick view on the MacPorts bug-tracking system and decided to post
> the bug here, because they usually want it to be posted to the developers.
> Inkscape was working well (thanks!) until I upgraded my MacPorts system.
>
> The output of
>
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_inkscape/inkscape/main.log
> is attached.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gtkmm/+bug/1171147/+subscriptions
>

--
Sent from my mobile device

[su_v (suv-lp)]

New upstream gtkmm package released (gtkmm 2.24.4):
<https://mail.gnome.org/archives/ftp-release-list/2013-June/msg00112.html>

Inkscape stable (<lp:inkscape/0.48.x> r9949) and trunk (<lp:inkscape> r12399) compile ok on OS X 10.7.5 using Glib 2.36.3, glibmm 2.36.2, GTK+ 2.24.19 and gtkmm 2.24.4 (strict build enabled for trunk, both available backends (X11, Quartz) tested)

@Alex - can we close this as 'Invalid' for inkscape (-> upstream problem with packaging of gtkmm 2.24.3), and hope that distros which already upgraded to gtkmm 2.24.3 will quickly replace the "flawed" gtkmm package with the latest release 2.24.4?

[Alex Valavanis (valavanisalex)]

> @Alex - can we close this as 'Invalid' for inkscape (-> upstream problem with packaging of gtkmm 2.24.3),
> and hope that distros which already upgraded to gtkmm 2.24.3 will quickly replace the "flawed" gtkmm
> package with the latest release 2.24.4?

Yes, that sounds reasonable to me. Done! :)