nilsbecker

Needless to say, the current opam version of owl is also not building.

This would be a good sign that owl is indeed being actively maintained, now that the project conclusion was reverted.

ah i see that Note has it. would you recommend Note for new projects currently? is there a use case where Note is a bad idea?

actually, in the snippet above, will the events occuring in initial value of `sig_of_events` be seen? or is the initial value lost in `S.changes`?

the problem persists. going through the .out file above i find calls like `ocamlfind ocamlc -package integers -thread -package threads -principal -short-paths -strict-sequence -g -ccopt "-I/Users/nbecker/.opam/414torch/lib/integers" -thread -ccopt -I/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/ffi -c...

interestingly, git cloning this repository and building via `make` succeeds for me! during the build a file `libffi.config` is generated, which appears to be correct. it picks up the homebrew...

`opam pin`ning ctypes to the local copy succeeds in installing ctypes. the problem appears to be with the version on opam.

> I reinstalled pkg-config with `brew reinstall pkg-config`. so the issue is with brew-installed pkg-config then?

`brew reinstall pkg-config` appears to have fixed the problem for me too

hmm. now i'm getting the same error again, even after `brew reinstall pkg-config`. this is after an upgrade to ventura.