Re: [Clg-devel] CLG on Mac OSX
Brought to you by:
espen
From: Espen S J. <es...@cs...> - 2006-08-30 11:34:34
|
Thomas Down <th...@de...> writes: > I'm trying to install CLG on my Mac, under SBCL 0.9.16 (also tested > on 0.9.14). In case it matters, I've got an Intel processor -- but > I think this issue is probably a general OSX/Darwin problem. I'm using > a recent checkout from the CLG CVS repository. Thanks. Your feedback is very welcome. > I've updated asdf-extensions.lisp to understand library names ending > in .dylib rather than .so, and also fixed a few hard-coded library > names elsewhere in the lisp code. I have updated the code to not relay on hardcoded library extensions. > When linking alien.dylib, I get a linker error: > > /usr/bin/ld: Undefined symbols: > _g_closure_add_finalize_notifier > _g_closure_new_simple > _g_closure_set_meta_marshal > collect2: ld returned 1 exit status > > If I relink this against libgobject-2.0.dylib, It wasn't really necessary to call these functions from C so I have removed the code doing this. Although the problem may reappear later in the build process. > all appears to be well until: > > debugger invoked on a UNDEFINED-FUNCTION: > The function |g_value_get_type| is undefined. > [...] > (SB-KERNEL:%COERCE-CALLABLE-TO-FUN |g_value_get_type|) > > The problem is occurring while loading "gparam.fasl", offending line > seems to be: > > (REGISTER-TYPE GVALUE |g_value_get_type|) Until the long-awaited full introspection becomes available i GLib, clg uses nm to find all types in a library by searching for symbols ending with _get_type. The cause of the problem above is that nm doesn't take the same options in OSX as the GNU nm. I have checked in some untested code that may solve this. It would be nice if you could test it again and report back to the list. -- Espen |