I recently set the "unicode" USE flag globally and rebuilt everything. So far, the only issue I've had is that sbcl 0.9.2 can't compile maxima. The symptom is debugger invoked on a SB-KERNEL::CONTROL-STACK-EXHAUSTED in thread 26717: Control stack exhausted (no more space for function call frames). This is probably due to heavily nested or infinitely recursive function calls, or a tail call that SBCL cannot or has not optimized away. Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [CONTINUE] Ignore and continue with next --eval option. 1: [ABORT ] Skip rest of --eval options. 2: Skip to toplevel READ/EVAL/PRINT loop. 3: [QUIT ] Quit SBCL (calling #'QUIT, killing the process). (SB-KERNEL::CONTROL-STACK-EXHAUSTED-ERROR) 0] sbcl built without unicode handles maxima fine. I've done a little research on Google; there are a few other issues with sbcl unicode support and maxima but I didn't see this specific one. I've attached the complete log if anyone needs it. Meanwhile, I'm rebuilding sbcl without unicode. I'm guessing this is upstream; unicode support in sbcl is quite new.
Created attachment 63028 [details] log 'USE="unicode -clisp -cmucl -gcl sbcl" emerge -v sbcl maxima " unpacked is 5 megabytes -- open it only if you need to :)
Does this problem still persist with SBCL 0.9.3? I had chance to try to reproduce this on amd64 (as x86_64) w/ sbcl 0.9.3 and unicode and it did work.
I have a similar (identical?) issue compiling Maxima with sbcl-0.9.3 with unicode on x86. ; caught STYLE-WARNING: ; The variable ME-OR-MY-ENCAPSULATION is defined but never used. ; - Providing system maxima ; (SETUP MAXIMA::PORT) ; ; caught STYLE-WARNING: ; undefined function: SETUP ; ; caught STYLE-WARNING: ; This function is undefined: ; SETUP ; ; compilation unit finished ; caught 8 STYLE-WARNING conditions ; printed 3 notes [doing purification: roots handlers stack bindings staticControl stack guard page temporarily disabled: proceed with caution debugger invoked on a SB-KERNEL::CONTROL-STACK-EXHAUSTED in thread #<THREAD "initial thread" {56DA2C9}>: Control stack exhausted (no more space for function call frames). This is probably due to heavily nested or infinitely recursive function calls, or a tail call that SBCL cannot or has not optimized away. Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [CONTINUE] Ignore and continue with next --eval option. 1: [ABORT ] Skip rest of --eval options. 2: Skip to toplevel READ/EVAL/PRINT loop. 3: [QUIT ] Quit SBCL (calling #'QUIT, killing the process). (SB-KERNEL::CONTROL-STACK-EXHAUSTED-ERROR) 0] Cheers, -- Travis
I can finally reproduce this with sbcl 0.9.6 and maxima 5.9.1
Wanted to say that the problem still exists with sbcl 0.9.9, confirmed today on X86.
It seems this issue is fixed with sbcl-0.9.11 and maxima-5.9.3 from the overlay (see bug #112754). Tested on ~amd64.
I checked maxima-5.9.3 and they're all ~arch keywords. If the sci@gentoo.org want help stablizing with a recent sbcl then we're happy to help.
