iolib VS lib-os

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.

And a lot more. Knee deep in documentation, but still finishing my other stuff first.

I have been taking the time to learn more Common Lisp lately and only have a question about how to use a certain part of asdf. I am working on a library called lib-os; essentially think of it as a UIOP with some conceptual changes and more features. First let me just say, my code runs fines that is not the issue. I have loaded each function in, it all works as expected (except detect-os which I am still working!). The issue I am having is with loading order of my code inside of ASDF. Currently I am having an issue where I need to pull some code from my implementation.lisp file to use in my kernel.lisp, (featurep ()) to be specific. For awhile the aforementioned function was inside of kernel.lisp, but once I decided to start porting some features from UIOP I moved it into the other file to keep the code related to checking CL stuff in one place. The issue is that now when I run (asdf:load-system "os") it throws a warning saying it is cutting unreachable code from all of the os-p functions, i.e. all of the functions that call (feature-p). I am confused as to why this is because I have implementation.lisp not only loading before kernel.lisp, but also listed as a depends-on for it. I have searched around, but cannot figure out what I am missing. Additionally, and this is slightly off-topic, how does one make a function callable at compile-time? setenv-if-not-p was a macro, but ASDF kept saying I need to make (getenv) callable at compile-time. Apologise for taking up so much of this subreddits time! You all, and a friend, have helped me learn a lot and I have been able to work on this because of it!