Re: [Clg-devel] CLG on Mac OSX
Brought to you by:
espen
From: Thomas D. <th...@de...> - 2006-08-31 19:59:02
|
On Thu, Aug 31, 2006 at 12:22:27PM +0200, Espen S Johnsen wrote: > > WARNING: Pango: `script_engine_init': dlsym(3) failed > > Failed to load Pango module for id: 'BasicScriptEngineFc' > > [repeated several times...] > > Pango: _pango_cairo_font_map_get_renderer: assertion `PANGO_IS_CAIRO_FONT_MAP (fontmap)' failed > > > > I'm wondering if this might be a Pango-on-OSX issue, though: > > CLG itself appears to be doing its job. > > I don't know what could cause this error, but I noticed that there is a > tool called pango-querymodules and that its man page mention something > about a 'Pango module path'. Yes, pango-querymodule runs fine, and detects all the installed pango modules. I can also run pango-view, and other GTK applications. Since the problem seems to occur when Pango tries to load its modules, I've rebuild Pango as a single shared library, with all the modules statically linked in (using the --with-included-modules option when configuring Pango). The new static Pango now works fine under CLG. I guess this suggests there's some kind of problem under OSX/Darwin when using dlopen/dlsym from within a library which was itself opened using dlopen. When running the CLG examples, I also ran into a very similar problem with GDK refusing to load its image-decoding modules. Once again the solution is to build these modules into the main library (./configure --disable-modules --with-included-loaders). Having done this, CLG is running very nicely on my Mac: http://www.derkholm.net/thomas/success.png I guess I should poke around in the OSX linker documentation to find out why the module loading isn't working. Thomas |