Hacker News Reader

Comment by BaculumMeumEst | Hacker News Reader

Looks cool but the install instructions fail on my mac m1:

   Aborted during step [1/3].
   Unhandled UIOP/LISP-BUILD:COMPILE-FILE-ERROR in thread # 
   <SB-THREAD:THREAD "main thread" RUNNING
                                                          
   {7005274C13}>:
     COMPILE-FILE-ERROR while
     compiling #<CL-SOURCE-FILE "log4cl" "src" "naming-sbcl">

I'm now 0/5 on the last interesting common lisp programs/libs I've tried to load on this machine: cl-cffi-gtk, cl-sdl2, nyxt, mgl, and now lem. CL is not m1-friendly it seems.

View on HN

Not sure if either of the linked issues below are from you, but it looks like the referenced file in Log4CL references internal SBCL symbols which are liable to change in versions. Last I heard, the M1 build of SBCL was a bit unique, so it might be worth opening an issue there. The sharplispers fork is the maintained one, I believe.

https://github.com/7max/log4cl/issues/41 https://github.com/sharplispers/log4cl/issues/45

Heh looking at the source someone went all out on SBCL internals

Same! https://github.com/lem-project/lem/issues/627

`ros install sbcl-bin/2.3.2` fixes the log4cl compile error issue

Reply on news.ycombinator.com