sbcl 1.4.1 Windows build failed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SBCL |
Fix Released
|
High
|
Unassigned |
Bug Description
Windows 10 64bit
up to date msys2 64bit
host compiler: sbcl 1.4.0
<------
; cross-compiling file "D:/ws/
While evaluating the form starting at line 52, column 0
of #P"D:/ws/
While evaluating the form starting at line 96, column 0
of #P"D:/ws/
debugger invoked on a SB-KERNEL:
#<THREAD "main thread" RUNNING {10027CA663}>:
:IMMOBILE-OBJECT fell through ECASE expression.
Wanted one of (:ASSEMBLY-ROUTINE :FOREIGN :FOREIGN-DATAREF :CODE-OBJECT
Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL.
restarts (invokable by number or by possibly-
0: [RECOMPILE] Recompile file "src/code/
1: [RETRY ] Retry EVAL of current toplevel form.
2: [CONTINUE ] Ignore error and continue loading file "D:\\ws\
3: [ABORT ] Abort loading file "D:\\ws\
4: Retry EVAL of current toplevel form.
5: Ignore error and continue loading file "D:\\ws\
6: Abort loading file "D:\\ws\
7: Abort building SBCL.
8: Exit debugger, returning to top level.
(SB!FASL:
error finding frame source: no dispatch function defined for #\!
source: NIL
0]
; compilation aborted after 0:00:00.007
------------>
I tried to analyze it, but the build is too tricky)
Somehow #! macro was not in effect when loading dump.lisp during cross-compile.
Changed in sbcl: | |
importance: | Undecided → High |
status: | New → Triaged |
Changed in sbcl: | |
status: | Fix Committed → Fix Released |
In 04f42d88803f0fd 6265ba07184de5b 98ec00d6e5