Peter Denno wrote:
On Saturday 09 September 2006 05:59, rd wrote:
I posted the following to comp.lang.lisp a few days
ago, and it was suggested that this list or the cffi
devel list would be more topical (and so here I am).


You came to the right place (this time). Talking to someone about on cffi about FreeBSD6 is also a good idea. If you go there and learn anything, please let us know.


I'm very inexperienced with Lisp, and I'm trying to
poke around with cells-gtk.

Playing with cells-gtk probably isn't the easiest way to learn lisp, but then doing so sound like something I'd try too ;^)

I'm using SBCL-0.9.0 on FreeBSD6, installed from the
ports system.  I downloaded cells-gtk-2006-06-30 and
followed the INSTALL instructions.

The test TEST-GTK:GTK-DEMO fails with one of the two
following errors (they alternate):

      Unable to load foreign library: libgthread-2.0.so
      Unable to load foreign library: libglib-2.0.so

Can you tell me what is returned when you evaluate this? :

(cffi-sys::%load-foreign-library "/usr/local/lib/libglib-2.0.so")

It returns T.

However, (cffi-sys::%load-foreign-library "/usr/local/lib/libgthread-2.0.so")
fails with the following:

Error opening shared object "/usr/local/lib/libgthread-2.0.so":
  /usr/local/lib/libgthread-2.0.so: Undefined symbol "pthread_attr_destroy".
   [Condition of type SIMPLE-ERROR]

So this indicates that it's CFFI (or perhaps something in the way
FreeBSD sets these libraries up)?




I manually did

      (cffi:load-foreign-library :GLIB)

and it returned T, although it complains about undefined
aliens.  After I did this, GTK-DEMO will only fail because
it can't load libgthread.

All of these libraries are in /usr/local/lib.  Any help
would be appreciated.

_______________________________________________
cells-gtk-devel site list
[email protected]
http://common-lisp.net/mailman/listinfo/cells-gtk-devel


_______________________________________________
cells-gtk-devel site list
[email protected]
http://common-lisp.net/mailman/listinfo/cells-gtk-devel

Reply via email to