Inkscape 0.92.0 now available on MacPorts
barry at barrys-emacs.org
Tue Jan 31 21:12:41 UTC 2017
Problem: port install inkscape +quartz builds without error but crashes when run reliably.
I tried to build a debugable version and that does not crash. Incase you can see why here is the script I used to do the build.
I do not understand the MacPorts build in enough detail to see the exact FLAGS and config options used.
I’m guessing that there is a subtle difference in the details of the build that lead to the SEGV when built with MacPorts.
Any ideas what to try next?
export CXXFLAGS="-std=c++11 -g -O0"
--disable-strict-build | tee build-config.log
make 2>&1 | tee build-make.log
> On 28 Jan 2017, at 18:32, Barry Scott <barry at barrys-emacs.org> wrote:
>> On 27 Jan 2017, at 17:07, Brandon Allbery <allbery.b at gmail.com <mailto:allbery.b at gmail.com>> wrote:
>> On Fri, Jan 27, 2017 at 6:33 AM, Barry Scott <barry at barrys-emacs.org <mailto:barry at barrys-emacs.org>> wrote:
>> Error: Failed to archivefetch gtkmm: gtk2 must be installed with +quartz.
>> Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_gtkmm/gtkmm/main.log for details.
>> Error: Follow https://guide.macports.org/#project.tickets <https://guide.macports.org/#project.tickets> to report a bug.
>> Error: Processing of port inkscape failed
>> I guess a missing dependency on gtk2 somewhere?
>> No, it means you already have gtk2 installed but with +x11 (which is the default). Sadly gtk2 does not support having both x11 and quartz variants active at the same time, and the two are not even source compatible because of things like <gdk/x11.h> as part of its X11 API.
>> Your options boil down to: either have a separate MacPorts installation somewhere other than /opt.local with a gtk2 +quartz and programs that require that, or remove all dependents of gtk2, reinstall gtk2 +quartz, reinstall the dependencies you removed, and hope they're all compatible with gtk2 +quartz. :/
> I followed some instructions on building the dependencies one by one with +quartz on and can now install Inkscape.
> I’m beginning to understand this +x11 vs. +quartz build situation I think.
> However that just gets to the 100% repeatable crash that seems to be well known (lldb bt):
> * thread #1: tid = 0x37abb8, 0x00007fffb65870f3 libsystem_c.dylib`_UTF8_mbsnrtowcs + 287, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x0)
> * frame #0: 0x00007fffb65870f3 libsystem_c.dylib`_UTF8_mbsnrtowcs + 287
> frame #1: 0x00007fffb6581f02 libsystem_c.dylib`__collate_mbstowcs + 123
> frame #2: 0x00007fffb65ab79c libsystem_c.dylib`strcoll_l + 76
> frame #3: 0x0000000102d50f99 libglib-2.0.0.dylib`g_utf8_collate + 105
> frame #4: 0x0000000100286d73 inkscape`font_factory::GetUIStyles(_PangoFontFamily*) + 221
> frame #5: 0x000000010028c4c8 inkscape`Inkscape::FontLister::update_font_list(SPDocument*) + 1490
> I will dig deeper if I can figure how to get source line and debug symbols for Inkscape under McPorts.
> (Locale not init’ed maybe? Bad args to g_utf8_collate?)
> I’m still researching how build Inkscape against MacPort dependencies.
>> brandon s allbery kf8nh sine nomine associates
>> allbery.b at gmail.com <mailto:allbery.b at gmail.com> ballbery at sinenomine.net <mailto:ballbery at sinenomine.net>
>> unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net <http://sinenomine.net/>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the macports-users