search

defun-games / claylib

A Common Lisp 2D/3D game toolkit built on top of Raylib 4.5.
zlib License
69 stars 4 forks source link

Can't save SBCL core image due to eager-future2 dependency #84

Open jangler opened 7 months ago

jangler commented 7 months ago

I was trying out claylib and attempted to build an executable, but got an error:

Can't save image with more than one executing thread
debugger invoked on a SB-IMPL::SAVE-ERROR in thread
#<THREAD "main thread" RUNNING {1001834103}>:
  Could not save core.
See also:
  The SBCL Manual, Node "Saving a Core Image"

I checked what the threads were:

0] (sb-thread:list-all-threads)

(#<SB-THREAD:THREAD "main thread" RUNNING {1001834103}>
 #<SB-THREAD:THREAD "Eager Future2 Worker" RUNNING {1004576213}>
 #<SB-THREAD:THREAD "Eager Future2 Worker" RUNNING {1004576713}>
 #<SB-THREAD:THREAD "Eager Future2 Worker" RUNNING {1004576CD3}>
 #<SB-THREAD:THREAD "Eager Future2 Worker" RUNNING {10045769F3}>
 #<SB-THREAD:THREAD "Eager Future2 Worker" RUNNING {10045764C3}>
 #<SB-THREAD:THREAD "Eager Future2 Worker" RUNNING {1004577233}>
 #<SB-THREAD:THREAD "Eager Future2 Worker" RUNNING {1004577B63}>
 #<SB-THREAD:THREAD "Eager Future2 Worker" RUNNING {1004577853}>
 #<SB-THREAD:THREAD "Eager Future2 Worker" RUNNING {1004577543}>
 #<SB-THREAD:THREAD "Eager Future2 Worker" RUNNING {1004576FB3}>)

This happens regardless of whether I actually use claylib; just including it (or eager-future2) in :depends-on is enough to cause this issue. So technically it's an upsteam issue, but eager-future2 is on a GitLab instance(?) and I'm not really interested in installing a 2FA authentication app just to report an issue to a repository that hasn't been updated in 5 years.

Let me know if I'm missing something -- I'm pretty new to CL.