Re: [Matlisp-users] Configuration failure on Linux/SBCL

[Robbie S. <rd...@me...>]

Hi,

I did the port of matlisp to sbcl.

Unfortunately, there were some problems with the patch (it got messed up 
by the sourceforge mailing list) so it wasn't completely applied to the 
cvs tree.  Parts of the patch were correctly applied, and others not.

I have a copy of my sources up at 
http://mercury.chem.pitt.edu/~rds/matlisp.sbcl.tar.gz

If you download these sources they should work out of the box. The only 
thing you might have to do is rebuild the configure script ("autoconf 
configure.in > configure").  After this the installation directions 
should work.

There is also in there an .asd system definition file, so if you want to 
use asdf to load matlisp you can just run configure as you did before, 
symlink matlisp.asd to the right place, and "(require :matlisp)" and it 
should compile and load everything.

Let me know if you have any problems.....

--Robbie

D. Michael McFarland wrote:
> Hello,
> 
>     After a long period of little lisp activity, I've just downloaded
> the CVS version of matlisp via
> 
>     cvs -z3 -d:pserver:ano...@cv...:/cvsroot/matlisp\
>         co matlisp
> 
> to try it with SBCL running on Gentoo Linux.  The INSTALL file begins
> 
> /----
> | Requirements:
> | =============
> | Either CMUCL (version 18b), SBCL (version 0.8.5) or 
> | Allegro CL (version 5.0 or later) is required.
> 
> No mention of SBCL there...
> 
> | * Allegro CL: Matlisp should compile on Linux, Solaris, Windows.
> |               In particular, Matlisp relies on the foreign
> |               function interface of Allegro CL.
> | 
> | * CMU CL: Matlisp should compile on Linux, Solaris.
> |           In particular, Matlisp relies on the foreign function
> |           interface of CMU CL and the built-in type 
> |           kernel::complex-double-float.
> | 
> | * SBCL: Matlisp should compile on Linux and MacOS X
> |         In particular, Matlisp relies on the foreign function
> |         interface of SBCL.
> \----
> 
> ...but that last paragraph is encouraging.  The detailed instructions
> include
> 
> /----
> | 4. Configure the system.
> |    o If you're using Allegro CL, specify --with-lisp=acl.
> |    o If you're using CMU CL, specify --with-lisp=cmucl
> |    o If you're using SBCL, specify --with-lisp=sbcl
> |    o Give the name of the Lisp executable via --with-lisp-exec=<name>
> |    o Run configure:
> | 
> |    ./configure --with-lisp=<lisp> --with-lisp-exec=<exec> --prefix=`pwd`
> \----
> 
> so I tried
> 
> # ./configure --with-lisp=sbcl --with-lisp-exec=/usr/bin/sbcl --prefix=`pwd`
> 
> only to be told
> 
> checking build system type... i686-pc-linux-gnu
> checking host system type... i686-pc-linux-gnu
> checking target system type... i686-pc-linux-gnu
> configure: error: Unknown Lisp system:  sbcl.  Supported systems are acl and cmucl
> 
>     Now, I know one plays with CVS versions at his own risk, and I'm
> probably being dense to boot, but there's enough there to suggest
> matlisp ought to work with SBCL that I thought it might be worth a
> note.  Will someone please enlighten me about the status of SBCL
> compatibility, or point out where I've gone wrong in the ./configure
> line?  Thanks!
> 
> Michael
>