Robert Smith

I think the whole printing thing needs to be changed. I've never copied a printed coalton value to read. It also seems faulty to assume everything is readable by default.

I'm all for readable, just not buggy readable. (:

I should probably tone down the warnings too.

> Please see the log here: > > [quilc-failure.txt](https://github.com/quil-lang/quilc/files/9226883/quilc-failure.txt) > > > > Version: 1.26.0 > > FreeBSD 13.1 > > Do you have libffi installed on your system? It...

The issue here is that SBCL/CFFI are not finding it (libffi) in any standard search paths.

> It is installed as ```/usr/local/lib/libffi.so``` Are you certain that's findable by your SBCL+CFFI? Try, as a test, pushing `"/usr/local/lib/"` onto `cffi:*foreign-library-directories*` before loading QUILC per [this documentation](https://cffi.common-lisp.dev/manual/html_node/_002aforeign_002dlibrary_002ddirectories_002a.html).

I also notice that > Unable to load any of the alternatives: > ("libffi.so.7" "libffi32.so.7" "libffi.so.6" "libffi32.so.6" "libffi.so.5" > "libffi32.so.5") doesn't list a plain `libffi.so`, which sounds silly and wrong....

The newest CFFI has 8 listed. [Here](https://github.com/cffi/cffi/blob/master/libffi/libffi.lisp#L30) is the relevant source code. You could try vendoring CFFI to your Quicklisp `local-projects` directory. You could also add to the list of...

> Why doesn't quilc use this version? This is not QUILC's decision. This is a dependency of a dependency that QUILC uses—a quasi-standard library for interacting with C libraries—and the...

Yep, recent SBCLs need more memory while compiling. Probably a good idea to apply that patch. Sorry for the difficulties but I'm glad you got it to work out!