freenode/#clasp - IRC Chatlog
Search
23:33:14
drmeister
::notify frgo Could you describe the crash that you experience building quicklisp with clasp on BigSur? I cleared my quicklisp cache and loaded iclasp-boehm and used (load "~/quicklisp/setup.lisp") and it worked.
23:37:28
drmeister
::notify frgo Could you give me the particular quicklisp systems that you were trying to build?
23:51:31
drmeister
Ironclad with alexandria and bordeaux-threads takes 212 seconds - this is on a macbook air 1.1 GHz Quad-Core Intel Core i5
23:54:29
drmeister
::notify frgo Don't use cclasp-boehm - use iclasp-boehm. cclasp-boehm won't work for a few more months until we upgrade to llvm12. Otherwise I don't see what you are doing that would crash. Ping me when you get this and I'll dig deeper.
0:52:06
kpoeck
drmeister frgo was calling cclasp-boehm and still compiling quicklisp, see https://gist.github.com/dg1sbg/afb4c951bcdd1a8e1e3eaeb9ec549450
1:19:11
drmeister
Ah - my memory is all jumbled up. cclasp-boehm is a symbolic link for iclasp-boehm
1:20:54
drmeister
I think there must be something different about frgo's environment relative to mine that is breaking his clasp. Mine just built and builds quicklisp and ironclad with no problems.
1:21:38
drmeister
It used to be (and will be again) that cclasp-boehm links together all of the Common Lisp and C++ code into one executable.
1:22:14
drmeister
iclasp-boehm is just the C++ code and it loads a an image file that is a big faso file.
7:49:32
drmeister
I threw caution to the wind and I allocate relocated memory for entire object files into boehm memory - it doesn't slow way down. I think I'm sort of GCing code.