this is probably because clisp is linked against the old libffcall. https://bugs.launchpad.net/bugs/274951 re-linking new clisp against new libffcall should fix the problem.
this is probably because clisp is linked against the old libffcall. /bugs.launchpad .net/bugs/ 274951
https:/
re-linking new clisp against new libffcall should fix the problem.