On Wed, Apr 28, 2010 at 8:17 AM, Mirko Vukovic <mirko.vuko...@gmail.com> wrote: > See below: > > On Tue, Apr 27, 2010 at 9:22 PM, Liam Healy <lhe...@common-lisp.net> wrote: >> I'm not sure what you're looking for here, but I've never >> had "GSL libraries not loadable" (not sure what you mean >> here; not found in the path?). Doesn't the form >> (cffi:use-foreign-library libgsl) >> at the end of init/init.lisp fail with some kind of reasonable >> error message if it doesn't find the libraries? What else >> is needed? >> >> Liam >> >> On Tue, Apr 27, 2010 at 8:56 AM, Mirko Vukovic <mirko.vuko...@gmail.com> >> wrote: >> ... >>> >>> Good idea. Here is another one that would be useful even for the >>> pros. A gsll-probe, that would probe the system to make sure that >>> gsll is loadable. The main thing that comes to mind, and that can >>> look scary to a newbie is if the gsl libraries are not loadable. > > I was thinking of absolute Newbies who get horrified when lisp drops > into a debugger. A way to deal with that might be to use exception > handling with `gentler' messages.
That's OK, provided it can be turned off. I'm not sure there's a general way to provide a global handler in CL though. > > And other than finding libraries, sometimes the libraries are not > loadable: with SBCL1.0.34, I got an `offset' error (don't remember > exactly what), and with 1.0.37, I could not load 64-bit libraries. Weird. I have no idea where that comes from, and I'm using a fairly recent SBCL and I've been using 64 bit for years. > > Anyways, I don't mean to throw this task to you. I'll think about an > implementation, and if I come up with something sensible, I will post > it here. OK, sounds good. > > Mirko > _______________________________________________ Gsll-devel mailing list Gsll-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/gsll-devel