yew VS iolib

It's possible, but you can observe how much trouble it can be in opsys , which doesn't depend on any C headers or do any grovelling. You may be suprised the amount of syscall instability papered over by libc.

org-view: https://github.com/nibbula/yew/blob/ea624f08ec235cf12536323c68a9805d9e668f3d/tools/view-org.lisp

I have plans to develop a shell that handles both POSIX shell script and common-lips, likely by simply passing the s-expressions to a REPL such as sbcl, but as I am very new to common-lisp I know that I will not having something fully working anytime soon, I am okay with that all is fun in learning right? I have, however, been hankering to find a new shell recently that can at least provide me with the basics of what I plan to create, a simple shell that can handle POSIX scripting and common-lisp interactively. For this I did some research and read this blog post. I have looked around at different dual shells and found that shcl and yew seem to be the most promising for my temporary use until my own shell is ready. My question here is, has anyone used either of these extensively? I am not expecting something that can give me what zsh does, I only use it for syntax highlighting anyway lol, but rather if either of these shells would be on par, interactively, with something like ksh (the shell I am most use too) i.e. basic tab completion, customizable prompt and anything else is a bonus. Does anyone here have experiences with stress testing either of these shells?

Perhaps the easiest approach is to use the foreign function interface (FFI) of your compiler and wrap the types and functions of unistd.h. One example: https://github.com/sionescu/iolib/tree/master/src/syscalls. Alternatively, you could use syscall

Looks like it's trying to use pkg-config to find the necessary flags for the library: https://github.com/sionescu/iolib/blob/master/src/syscalls/f...

The proper solution would be to install it somewhere and configure pkg-config to find it, but you could just try putting the headers in /usr/local/include and see if it finds them.

I think your system package manager has installed your SBCL/asdf in some weird way. It would be best to just uninstall it all and build SBCL from sources yourself (it has asdf bundled with it). The binary releases for FreeBSD on sbcl.org seem to be ancient versions.

Try cl-iolib it defines those signal constants and is portable across lisps. https://github.com/sionescu/iolib/blob/master/src/syscalls/ffi-types-unix.lisp

See https://github.com/sionescu/iolib/issues/63 for a discussion.