andrea bertagnolli

> We could distribute a ghci drop-in replacement. @jwaldmann already made this: https://github.com/jwaldmann/safe-tidal-cli . It looks good and is safe for exposing to untrusted users (e.g via flok), although doesn't...

Close as now there's Pulsar and the tidal plugin is working nicely (it changed name already: https://github.com/tidalcycles/pulsar-tidalcycles

some years passed, I know, but I'd like to know, is this stil needed? in case please describe what you did and why, otherwise I will close it.

Seems to be the same as #42 , which one should be considered?

I changed the WITH_GHC property but same result. I tried to build it by myself following the "workflow" yml but I get cabal errors... I haven't had much luck with...

Yep, I was used ghc 9.0.1, now with 8.10 I built it, copied the static folder and it started. I got another error when I evaluated the "tidal hello world",...

here's the output: ``` linux-vdso.so.1 (0x00007ffd0c57f000) libz.so.1 => /home/andrea/Downloads/binary/./c-libs/libz.so.1 (0x00007ffa4f97b000) libtinfo.so.6 => /home/andrea/Downloads/binary/./c-libs/libtinfo.so.6 (0x00007ffa4f94b000) librt.so.1 => /home/andrea/Downloads/binary/./c-libs/librt.so.1 (0x00007ffa4f940000) libutil.so.1 => /home/andrea/Downloads/binary/./c-libs/libutil.so.1 (0x00007ffa4f93b000) libdl.so.2 => /home/andrea/Downloads/binary/./c-libs/libdl.so.2 (0x00007ffa4f935000) libpthread.so.0 => /home/andrea/Downloads/binary/./c-libs/libpthread.so.0 (0x00007ffa4f910000)...

Here's the output, seems like the libraries used are not the same. with these it works ``` linux-vdso.so.1 (0x00007ffffe186000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f1c94534000) libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 (0x00007f1c94505000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1...

I removed `c-libs` and replaced it with a link to the system library folder: ``` ln -s /lib/x86_64-linux-gnu/ c-libs ``` With this it started! So maybe the solution could be...

Ok, now it works!