Archives

Creative Commons License
This blog is licensed under a Creative Commons License.

Fixed a few bugs in Ready Lisp

| 14 Comments | No TrackBacks

A couple of pathname issues were discovered in the release of Ready Lisp that was posted yesterday, leading to the inability to load asdf-install (or use it). These have been fixed in the new release uploaded today. If you now use asdf-install and choose a “system-wide” installation, the installed packages get saved in your Application bundle. However, due to the way that asdf-install itself works, if you then move your application bundle to another directory, symbolic links in the systems directory will get broken. So I recommend installing new packages into your home directory instead.

Also, the sources for SBCL are now included, meaning that if you use M-. (jump to definition) and pick a function like mapcar, it will drop you into the source code for SBCL’s mapcar implementation.

The new version is available here (the old link still works, it is now a reference to that one).

Lastly, I’ve created a new home page for the Ready Lisp project, which now lives here.

No TrackBacks

TrackBack URL: http://www.newartisans.com/mt/mt-tb.cgi/21

14 Comments

Good stuff, but I have two issues with it:

In Safari the file downloads as a .bz2 for some reason, and proceeds to behave weirdly when attempting to open it. I had to download it with a separate FTP client. I’m not sure where the problem lies, but I haven’t had one like this before. I’m running a clean install of Leopard.

No asdf-install. I tried to install asdf-install myself, but it wants to store fasl files in /usr/local/stow and I haven’t quite figured out how to change that yet (did you modify asdf:output-files?). Of course, a quick solution would probably be to create that dir and give my user access to it, but I would prefer to keep everything within my home dir.

Other than that it’s pretty nice, and provides a nice emacs/slime environment out of the box.

Actually, I’m not sure about the paths now, it could be that I’m stealing asdf-install from sbcl’s contrib dir.

Actually, looks like it’s looking for .lisp files in there, installing another random asdf package manually I get: The file “/usr/local/stow/sbcl-1.0.12-i386/lib/sbcl/sb-grovel/defpackage.lisp” does not exist.

And if it keep hitting 1 (for accept as if compilation had succeeded) the package seems to install and work. Hmm.

Hmm.. it looks like there are more issues with prebinding a core file than I had thought. I’ll have to think over how to solve this, without requiring the user to sit through the cycle of making creating a core file the first time.

Also, bear in mind that asdf and asdf-install are part of SBCL. You only need to require them in, not use external packages.

Yeah, I know it’s supposed to be part of SBCL, but it didn’t seem to exist, which is why I was trying to install it myself.

The version you just released works perfectly though, you rock!

When I try to run ReadyLisp, I get the following error:

*error: /usr/bin/arch takes no arguments

Process inferior-lisp exited abnormally with code 255

And it sits there polling for the tmp/slime file.

Ready Lisp will only run on Leopard (10.5). The error you are seeing occurs if you try to run on 10.4.

I really appreciate your work. I think playing with lisp can be happier because the efforts of people like you. I was desperate because I could not find the way to make SBCL support experimental thread on Mac. But Ready Lisp did it. I am very happy that I can try hunchentoot and weblocks now. Could you tell me how you make SBCL support thread on Mac? Instructions of “2.2 Customizing SBCL” in “install” file does not work in my experience.

To enabled threading in SBCL, you create a file named “customize-target-features.lisp” in the top directory of the source tree. I’ve added ftp://ftp.newartisans.com/pub/lisp/customize-target-features.lisp so you can see what I’m using.

Hm. Not working for me - Intel 10.5.1:

(swank:start-server "/var/folders/+o/+od9Gfs42RavKU+BYqD4aU++-++/-Tmp-/slime.75291" :coding-system "utf-8-unix")
dyld: shared cached file is corrupt: /var/db/dyld/dyld_shared_cache_ppc

(why is it looking for a ppc dyld cache on an intel system? it’s not running in rosetta…)

This is SBCL 1.0.12.17, an implementation of ANSI Common Lisp.
More information about SBCL is available at .

SBCL is free software, provided as is, with absolutely no warranty.
It is mostly in the public domain; some portions are provided under
BSD-style licenses.  See the CREDITS and COPYING files in the
distribution for more information.
fatal error encountered in SBCL pid 75422:
blockable signal 1 not blocked

Welcome to LDB, a low-level debugger for the Lisp runtime environment.
ldb> unknown command: ``(swank:start-server''
ldb>

Your SBCL installation is not right, I’ve never encountered an error like that. I recommend building yourself from sources.

About this Entry

This page contains a single entry by John Wiegley published on December 8, 2007 1:11 PM.

New version of Ready Lisp for Mac OS X was the previous entry in this blog.

FP techniques in Lisp: Data sharing is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.

Recent Comments

  • Curt Sampson: That there’s “no state” in Haskell is quite wrong; in read more
  • rv: Hi. I wanted to drop you a quick note to read more
  • John Wiegley: It’s here: http://ftp.newartisans.com/pub/python/modpython_gateway.py read more
  • Leon: The file “modpython_gateway.py” Is no longer available in the downloads read more
  • Kathy: Well, the article is really the sweetest on this laudable read more
  • mr.design: Hi John, I just started to read your GFTBU, it’s read more
  • yoman: “Barfin”? “Slurping”? “Slime” “Hunchentoot” ??? What in the T.F. world read more
  • John Wiegley: Something like this is slated for the next release of read more
  • womens health: According to me, Apple has implemented something called blocks, which read more
  • Bjorn Tipling: Why would you add instructions for installing an editor when read more
OpenID accepted here Learn more about OpenID
Powered by Movable Type 4.261