Will attach patch..
Created attachment 139097 [details, diff] inkscape-glib-2.15.patch
Reporting this upstream instead would make a lot more sense...
I'm not sure what upstream to blame here. I'm actually leaning towards glib here. I added a comment to a relevant g_assert bug. The deal here is that g_assert moved to a different header that isn't included in glib/gmessages.h and inkscape is seemingly trying to keep the amount of include files to a minimum (I assume for compile time sake or something) and ends up not seeing the declaration as it's not in gmessages.h anymore. With such a widely used macro/function as g_assert is, the header move is definitely an annoyance, but not sure if a bug that must be corrected from glib side
I just bumped inkscape to version 0.46 and I looked through some header files and it looks like they include the pre-2.15 and post 2.15 files - so this could be fixed... could someone with latest inkscape and glib test if it works? Thanks in advance.
(In reply to comment #4) > I just bumped inkscape to version 0.46 and I looked through some header files > and it looks like they include the pre-2.15 and post 2.15 files - so this could > be fixed... could someone with latest inkscape and glib test if it works? Works fine with glib-2.16.1 (from the gnome overlay). Thanks!
Thanks for the test - so this bug can be closed.
*** Bug 213634 has been marked as a duplicate of this bug. ***
Do you consider fixing 0.45.* too, or do we need to make sure that inkscape-0.46 gets stabilized before glib-2.16, once we are that far?
(In reply to comment #8) > Do you consider fixing 0.45.* too, or do we need to make sure that > inkscape-0.46 gets stabilized before glib-2.16, once we are that far? I'd prefer not to patch 0.45* and stabilize 0.46 with/before glib-2.16.
*** Bug 218743 has been marked as a duplicate of this bug. ***