#13 Problem compiling 2.0.23 on linux

closed
nobody
None
5
2004-05-02
2004-03-14
Chris Capel
No

With SuSE 9.0, the Sun JDK 1.4.2_04, and CMUCL from a
CVS snapshot at 12/2003, I run the install script on
either the binary or source version of Jabberwocky
2.0.23 and check only the CMUCL option (and the Ant
option for the source dist). I get this error in the
log window after it does a lot of work:

<0> ; Converted CREATEJAVASYNTAXLISPLAMBDALIST.
<0> ; Compiling DEFUN CREATEJAVASYNTAXLISPLAMBDALIST:
<0> ; Converted CREATEJAVALISPLAMBDALISTVAR.
<0> ; Compiling DEFUN CREATEJAVALISPLAMBDALISTVAR:
<0> ; Converted CREATEJAVALISPLAMBDALISTKEYWORDVAR.
<0> ; Compiling DEFUN CREATEJAVALISPLAMBDALISTKEYWORDVAR:
<0> ; Converted ADDTOLIST.
<0> ; Compiling DEFUN ADDTOLIST:
<0> ; Converted REPLACEINVALID.
<0> ; Compiling DEFUN REPLACEINVALID:
<0> ; Byte Compiling Top-Level Form:
<0>
<0> ; Compilation unit finished.
<0> ; 1 error
<0> ; 3 warnings
<0> ; 1 note
<0>
<0>
<0> ; cmucl/cmu.x86f written.
<0> ; Compilation finished in 0:00:05.
<0> ;; Loading
#p"/home/chris/lisp/JabberwockyBinary/cmucl/debugger.x86f".
<0> ;;; Loading
#p"/home/chris/lisp/JabberwockyBinary/cmucl/cmu.x86f".
<0>
<0>
<0> Error in function LISP::FOP-EVAL-FOR-EFFECT:
<0> Attempt to load a file having a compile-time
read error.
<0> [Condition of type SIMPLE-ERROR]
<0>
<0> Restarts:
<0> 0: [CONTINUE] Skip this form.
<0> 1: Return NIL from load of
"cmucl/cmu.x86f".
<0> 2: Return NIL from load of
"cmucl/debugger.x86f".
<0> 3: Return NIL from load of "install.lisp".
<0> 4: [ABORT ] Skip remaining initializations.
<0>
<0> Debug (type H for help)
<0>
<0> (LISP::FOP-EVAL-FOR-EFFECT)
<0> Source: Error finding source:
<0> Error in function DEBUG::GET-FILE-TOP-LEVEL-FORM:
Source file no longer exists:
<0> target:code/load.lisp.

Discussion

  • Marc Mertens
    Marc Mertens
    2004-04-22

    Logged In: YES
    user_id=13143

    I noticed that in the latest version of cmucl they moved the
    location of 'function' from the USER package to the
    COMMON-LISP-USER package, this caused a problem with the
    installation of Jabberwocky and is probably the cause of
    your problem. Normally this is resolved in version 2.0.24
    can you try this version and report back to me if your
    problem is solved

     
  • Marc Mertens
    Marc Mertens
    2004-05-02

    • status: open --> closed
     
  • Marc Mertens
    Marc Mertens
    2004-05-02

    Logged In: YES
    user_id=13143

    Problem was caused by incorrect error message when java
    1.5.x was detected instead of java.1.4.x. Added support for
    java 1.5.x and solved the error messaging problem.