CCL's |memcpy| is often not found

Question

CCL's |memcpy| is often not found

borodust opened this issue 6 years ago · 5 comments

Few users report issues with CCL's |memcpy| mappings. But sometimes it just works (I cannot reproduce the issue myself). What could be a possible reason? Would you accept a PR changing |memcpy| usages with CFFI calls?

borodust/trivial-gamekit#31

SIGNAL Undefined function X86-LINUX64::|memcpy| called with arguments

borodust/hello-gamekit#2

Error: Undefined function WIN64::|memcpy| called with arguments

borodust/notalone#3

DEFAULT-UNDEFINED-FUNCTION-CALL-RESTARTS 10242206 X86-DARWIN64::|memcpy|

Answer 1 · 2020-03-06T18:12:49.000Z

also got Error: Foreign function not found: WIN64::|memset| on Clozure Common Lisp Version 1.11.5/v1.11.5 (WindowsX8664), windows 8.1

Answer 2 · 2020-03-06T18:41:30.000Z

I think this should be reported upstream because I've had other reports where the released binaries worked, but recompiling CCL triggered this failure.

Answer 3 · 2020-03-06T18:45:53.000Z

Sure, a patch that uses cffi:foreign-funcall is OK for me.

Answer 4 · 2020-03-06T19:17:47.000Z

Seems like my problem was a bad install of ccl, was missing the win64-headers/ directory which the "#_" apparently needs to find the functions.

Answer 5 · 2020-03-06T19:24:42.000Z

@borodust can you also check if the headers were present in those bug reports ?