On Tue, Dec 22, 2009 at 6:56 AM, Elliott Slaughter
<elliottslaughter@gmail.com> wrote:
> After what feels like beating my head against a wall for several hours, and
> getting contradictory results from various attempts to boils the failure
> down to a manageable size, I finally tried my original build recipe again,
> and it just worked. I'm not really sure what to say, other than that I'm
> really confused. I don't think the workarounds suggested by myself and
> others are necessary, so I think we can all forget about this, at least
> until this comes to haunt me again.

This is something that definitely needs to be improved in CFFI, at
least documentation-wise. Care to share your build recipe for dealing
with foreign libraries?

which presumably has a dependency on lispbuilder or cl-opengl or something else that depends on a foreign library. After than, just save the executable,

The only platform where I typically have this not work is on SBCL/Windows. I do have a little piece of initialization code to reload any foreign libraries, but obviously that didn't help me this last time. Sometimes I also put the dlls in the current directory, but again, I'm not sure whether that actually helps or not.