From: Nicolas N. <Nic...@iw...> - 2003-11-25 09:20:09
|
Bob Rogers <rog...@rg...> writes: > From: rif <rif@MIT.EDU> > Date: Mon, 24 Nov 2003 16:47:47 -0500 > > A while back, Nicolas Neuss posted a bug trying to make a new CMUCL > run with the CVS ILISP. In particular, this is CMUCL post-18e CVS > 2003-08-15, and I downloaded ILISP today (24 Nov 2003). I'm getting > exactly the same error Nicolas described (see > http://sourceforge.net/mailarchive/forum.php?thread_id=3281533&forum_id=5778), > although for Nicolas, the problem eventually seemed to go away on its > own, and for me it's not. > > Any ideas or suggestions? > > Cheers, > > rif > > Sorry; I didn't see the original post, though I'm not sure why. > Probably trying to read too fast. > > Anyway, I had what appears to be the same problem with ilisp CVS and > the CMUCL November snapshot, and I think the solution was to blow away > all of the *.x86f files before starting cmucl under ilisp, then do M-x > ilisp-compile-inits. If that doesn't work, try invoking CMUCL from a > shell and compiling the relevant files manually (ilisp-pkg.lisp, > cl-ilisp.lisp, cmulisp.lisp, and find-src.lisp, in that order), loading > the new binary after each compile. > > One of these solutions worked with CMUCL, and the other worked with > SBCL 0.8.4, but I'm afraid I don't remember which was which. > > HTH, > > -- Bob Rogers > http://rgrjr.dyndns.org/ For me the solution was also something like this. If this does not work, maybe the following helps. I also had problems because ilisp used some site-wide initialization files which were compiled for an older Ilisp and older CMUCL. These existed because I once had installed Debian ilisp and "apt-get remove ilisp" did not do its clean up properly. Nicolas. |