upstream bug: https://bugs.launchpad.net/inkscape/+bug/1158787 If gtk+ is compiled with USE="quartz", it does not link against libpangoft2-1.0. This causes link errors with inkscape: Undefined symbols for architecture x86_64: "_pango_fc_font_get_type", referenced from: Inkscape::Extension::Internal::CairoRenderContext::renderGlyphtext(_PangoFont*, Geom::Matrix const*, std::vector<Inkscape::Extension::Internal::CairoGlyphInfo, std::allocator<Inkscape::Extension::Internal::CairoGlyphInfo> > const&, SPStyle const*)in libinkscape.a(cairo-render-context.o) "_FcPatternGetDouble", referenced from: Inkscape::Extension::Internal::CairoRenderContext::renderGlyphtext(_PangoFont*, Geom::Matrix const*, std::vector<Inkscape::Extension::Internal::CairoGlyphInfo, std::allocator<Inkscape::Extension::Internal::CairoGlyphInfo> > const&, SPStyle const*)in libinkscape.a(cairo-render-context.o) "_FcPatternAddBool", referenced from: FactorySubstituteFunc(_FcPattern*, void*) in libinkscape.a(FontFactory.o) "_pango_ft2_font_map_new", referenced from: font_factory::font_factory()in libinkscape.a(FontFactory.o) "_pango_ft2_font_map_set_resolution", referenced from: font_factory::font_factory()in libinkscape.a(FontFactory.o) "_pango_ft2_font_map_create_context", referenced from: font_factory::font_factory()in libinkscape.a(FontFactory.o) "_pango_ft2_font_map_set_default_substitute", referenced from: font_factory::font_factory()in libinkscape.a(FontFactory.o) "_pango_ft2_font_get_face", referenced from: font_instance::MapUnicodeChar(unsigned int)in libinkscape.a(FontInstance.o) font_instance::InitTheFace() in libinkscape.a(FontInstance.o) ld: symbol(s) not found for architecture x86_64 The attached patches fix this for me by explicitly pulling in the pangoft2 libs via pkg-config --libs in inkscape's configure. Reproducible: Always
Created attachment 342904 [details, diff] make inkscape's configure look for pangoft2
Created attachment 342906 [details, diff] adjust ebuild
Fixed upstream. Will be in 0.48.5 and 0.49.
inkscape-0.48.5 is in portage now, so may be this bug is fixed?
(In reply to Nikoli from comment #4) > inkscape-0.48.5 is in portage now, so may be this bug is fixed? Indeed, the upstream fix works as advertised. This bug can be closed. Thanks, Michael