Re: [Clg-devel] CLG on Mac OSX
Brought to you by:
espen
From: Espen S J. <es...@cs...> - 2006-08-31 10:22:35
|
Thomas Down <th...@de...> writes: > The OSX/Darwin version of nm prints out entries for undefined > symbols, and doesn't seem to have any equivalent of the > --defined-only option. (For example output, see > http://www.derkholm.net/thomas/nm-example.txt -- let me know > if you want to see output using different options). The undefined > symbols are causing the loop in %find-types-in-library to > terminate prematurely. There's also another issue: there's an > extra '_' prepended to each symbol name. There's a little patch > which solves these two issues below. Thanks, I've applied your patch and also fixed my mistake in the loop (but I guess it isn't really necessary to check for lines with a 'T' when the -s option is given to nm). > There are a couple more minor issues I've caught: > > - In gtkobject.lisp, there's on remaining hardcoded ".so" Fixed > - Under OSX, gtk/alient.dylib needs to be linked with > libgtk and libgobject I've added a :ldflags option to the unix-dso component and updated gtk.asd with the required linker flags. > With these two issues resolved, everything compiles, and > (load "hello-world") opens a window. I'm still running into > a snag once it tries to render some text: > > 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'. -- Espen |