Re: Problems installing cl-http

"Paul Werkowski" <[email protected]>
Newsgroups gmane.lisp.cl-http
Message-ID <000f01c1e719$18346490$0100a8c0@MOBY>
 > [...lots of stuff snipped...]
| > ;; Loading #p"/usr/home/chris/cl-http/cmucl/defsystem.lbytef".
| > ;; Loading #p"/usr/home/chris/cl-http/cmucl/server/sysdcl.lisp".
| >
| > Type-error in KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER:
| >    #() is not of type (OR CONS
| >                           BASE-STRING
| >                           (MEMBER NIL :UNSPECIFIC :WILD)
| >                           COMMON-LISP::PATTERN)
| 
| Although not specific to your problem, I recall that a while back CMUCL
| accepted (at one time maybe even required) vectors for directories in
| pathname functions.  There may be some relics of code that handled that
| particular idiosyncrasy.  It may be sufficient just to change the type
| of the directory list from vector to list in order to solve the problem.
| 

This looks like the old version of defsystem is being used.

| I recall this from some work I did porting defsystem.lisp to other 
| platforms.
| As I now look at the sources, it does, indeed, appear to be a 
| problem with
| the defsystem code.  One quick fix to try would be to push the 
| :cmu17 feature
| *features* and see if that fixes things:
| 
|      (push :cmu17 *features*)
| 
| It should fix the defsystem part.  What I'm not sure about is 
| whether adding
| that feature will break anything in CL-HTTP.
| 

That may indeed help here, and I don't think there is anything in CL-HTTP
that sees that feature.


| A better long-term strategy might be to get a more recent version 
| of defsystem.lisp.
| IIRC, Marco Antoniotti has been working on upgrading that 
| particular facility.
| I don't know if this has been addressed in more recent versions.  
| The latest version
| I looked at still had the code only conditionalized for cmu17 and 
| not cmu18
| 

Yes, users of 18d should be getting the latest defsystem from somewhere.

Paul
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.