simple-error | A Rust library that provides a simple error | Architecture library

Your supposition is correct, this wrapper function that you are using calls ioctl with a pointer to your value instead of the value.

Have you tried simply (sb-unix:unix-ioctl fd cl-i2c-lli:+i2c-slave+ addr)?

that first warning seems pretty clear to me, tbh. in (setf foo 'bar), foo is not known to refer to a variable. it hasn't been locally bound as a lexical variable by a form like lambda or let, and it hasn't been globally bound as a special variable by a form like defvar or defparameter. if you want this to appear as a top-level form, you should write (defparameter *foo* 'bar) (note that common lisp convention is to surround the names of special variables in earmuffs). if you want to do this within the body of a function or for a finite scope, you should do (let ((foo 'bar)) (do-stuff-with foo)).

as to your second problem, in addition to the fact that database is unbound, you have the wrong quote character. ’ is not an ascii single-quote, and as such, is being parsed as a symbol. the compiler sees your form as: (setf database |’| ((b1 shape green) ...)), which is not a valid setf form. to fix this, figure out how to type the character ', and/or don't copy-paste code from formatted documents into plain text files.

Slot names are symbols, so the package matters when using SLOT-VALUE / WITH-SLOTS. In this case the references slots appears to be named by an internal symbol in the package MITO.CLASS.COLUMN.

The inspector doesn't show the package name (because it's rarely needed), but you can see that the slot definition is of type MITO.DAO.COLUMN:DAO-TABLE-COLUMN-CLASS, so you can use CLOSER-MOP:CLASS-SLOTS to find the slot definition:

The Common Lisp standard only mentions tracing of functions. In compiled implementations, macro expansion usually takes place at compile time and thus tracing of macros is usually not supported.

But some Common Lisp implementations can trace macros via a Lisp interpreter (!):

CLISP can trace macros:

My guess would be that your keyword->symbol function interns into the wrong package, because the read in there is executed from a different one:

Because Common Lisp allows you to write functions even if the compiler can’t determine a smallest function type for them, the compiler is not always able to check if a function has a certain type. Therefore the only sane behaviour is to not check the type.

Secondarily, such a minimal type may not exist. Consider this function:

While symbol number is a type specifier, list (number) is not.

Please use

According to https://ecls-list.narkive.com/xACoJUbf/c-build-program-and-eval the compiler isn't loaded by default, you need to use

You are missing commas before the parts that are to be evaluated: