[Matlisp-users] Problems compiling Matlisp with new CMUCL

[Nicolas N. <Nic...@iw...>]

Hello, Matlisp- and CMUCL-users.

I have recently updated to a new CMUCL version (not without problems as the
CMUCL users know).  Also Matlisp does not work out of the box (I have
finally succeeded in doing a CVS update for it [1]).

I have the following problems from the beginning:

---------------------------------------------------------------------------

(load "start.lisp")
; Loading #p"/home/neuss/CL-HOME/matlisp/start.lisp".
; Converted SETLOGICALROOT.
; Converted GETLOGICALROOT.
; Converted DEFLOGICALPATH.


Error in function LISP::SUBSTITUTE-INTO:
   Not enough wildcards in FROM pattern to match TO pattern:
  #<LISP::PATTERN :MULTI-CHAR-WILD "." :MULTI-CHAR-WILD>
   [Condition of type SIMPLE-ERROR]

Restarts:
  0: [CONTINUE] Return NIL from load of "matlisp:system.dcl".
  1:            Return NIL from load of "start.lisp".
  2: [ABORT   ] Return to Top-Level.

Debug  (type H for help)

(LISP::SUBSTITUTE-INTO #<LISP::PATTERN :MULTI-CHAR-WILD "." :MULTI-CHAR-WILD>
                       NIL
                       T)
Source: 
; File: target:code/pathname.lisp

; File has been modified since compilation:
;   target:code/pathname.lisp
; Using form offset instead of character position.
(ERROR "Not enough wildcards in FROM pattern to match ~
		       TO pattern:~%  ~S"
       PATTERN)
0] l
LISP::DIDDLE-CASE  =  T
LISP::PATTERN  =  #<LISP::PATTERN :MULTI-CHAR-WILD "." :MULTI-CHAR-WILD>
LISP::SUBS  =  NIL

0] d
(LISP::TRANSLATE-COMPONENT "SYSTEM"
                              :WILD
                              #<LISP::PATTERN
                                :MULTI-CHAR-WILD "." :MULTI-CHAR-WILD>
                              T)
1] l
LISP::DIDDLE-CASE  =  T
LISP::FROM  =  :WILD
LISP::SOURCE  =  "SYSTEM"
LISP::TO  =  #<LISP::PATTERN :MULTI-CHAR-WILD "." :MULTI-CHAR-WILD>

1] d
(TRANSLATE-PATHNAME #.(logical-pathname "MATLISP:SYSTEM.DCL")
                       #.(logical-pathname "MATLISP:**;*.*.*")
                       #p"/home/neuss/CL-HOME/matlisp/**/*.*.*")
2] 

---------------------------------------------------------------------------

Apparently something changed in CMUCL's handling of pathnames...

Nicolas.

[1] Sourceforge appears to be quite unreliable.  Would it be reasonable for
    Matlisp to switch to another server, e.g. savannah.gnu.org?  Or
    savannah.nongnu.org?