Because those symbol-calls in the .asd of iolib.common-lisp.asd do not get carried along in the building of bundling ops like monolithic-lib-op, they will not be run when they're needed.
In this particular case, it sets up a built ECL static library of iolib/syscalls to fail on load because the close function is still a function and not a generic.
This is just a FYI. I worked around this by calling (gray::redefine-cl-functions) through an eval before attempting to initialize the iolib library. Its somewhat surprising to need to setup gray streams just to use iolib/syscalls.
Because those symbol-calls in the .asd of iolib.common-lisp.asd do not get carried along in the building of bundling ops like monolithic-lib-op, they will not be run when they're needed.
In this particular case, it sets up a built ECL static library of iolib/syscalls to fail on load because the
closefunction is still a function and not a generic.This is just a FYI. I worked around this by calling
(gray::redefine-cl-functions)through an eval before attempting to initialize the iolib library. Its somewhat surprising to need to setup gray streams just to use iolib/syscalls.