I'll try that approach. Never really tried SBCL or Clozure CL.
> And i compile the source each time
You mean that you compile, for instance, Clisp? I tried to do it once, because FFI usage is dependent of a the flag --with-dynamic-ffi being set in the ./configure step [1][2]. I don't remember exactly why, but I got some difficulties in the build process, but I managed to do it.
This may be a little out of scope, but does anybody know about a common lisp implementation that is more FFI-friendly?
[1]: http://stackoverflow.com/questions/130636/how-to-compile-cli... [2]: http://stackoverflow.com/questions/3901698/is-there-a-way-to...
sbcl doesn't rely on the C compiler so you should have no problems building it on mac OS. Clozure CL was originally a CL specifically for the mac, so it definitely should work fine. SBCL seems to be the most popular open-source implementation, as it can generate extremely good code, often with just minimal type annotations.
By each time, I mean for updates to sbcl.
Don't install any other Common Lisp stuff SBCL doesn't depend on from the Debian repository though, except maybe ASDF. Get everything else through Quicklisp.
I have done less with ruby lately, but as I recall the only way to survive was to use RVM or apparently now chruby to get everythin and compile it up.