On Sun, 2015-03-15 at 13:37 -0400, Ken Brown wrote: > This sounds like a packaging error on my part. First of all, lisp.dll > is new with the latest clisp; it was part of my solution to the dynamic > loading problem. But from what you say, it sounds like I should put it > in /usr/bin. In fact, I should rename it to cyglisp.dll, with a > corresponding /usr/lib/liblisp.dll.a, so that applications can link > against it with '-llisp'. Would this solve the problem?
I'm not all that familiar with clisp. Is there a single binary that loads these dynamic modules, or multiple binaries? > In retrospect, I should have made the new clisp a test release, to avoid > breaking things. Sorry about that. No worries. -- Yaakov
