After upgrading my system to Leopard this weekend, I decided to refresh Ready Lisp as well. It now contains both 32-bit and 64-bit builds of SBCL (which has been bumped to 1.0.11), so if you have a Core 2 Duo machine, you’ll be running Lisp at full 64-bit! Alas, Emacs itself cannot support 64-bit as a Carbon app, because there are no 64-bit Carbon libraries. SLIME has also been updated, to CVS latest as of today. Aquamacs is still the same version at 1.2a.

I did spend several hours trying to build a fully Universal package that would run on PowerPC as well (I have a PowerBook G4 in addition to this MacBook Pro), but it seems Leopard has broken the PowerPC port of SBCL. Some of the core OS structures have changed, such as os_context_t.

Ready Lisp is now being versioned according to the SBCL version it contains, which makes today’s release ReadyLisp-1.0.11-10.5-x86.dmg. The older version, which still works on 10.4, can be downloaded here.

NOTE: The recent loading bug for Leopard users has been fixed. Please re-download. Also, it still does not work on OS X 10.4 (Tiger) at the moment. I will have to create a separate build of SBCL for that version this weekend.

### 22 Responses to “Ready Lisp for OS X Leopard”

1. Hi,

Thanks for providing the package. Can you also have a README with it that tells you what else you’ve packaged with it.

Also, I get the following error when I start the application. I am running 10.5 on MBPro.

Thanks

Can’t locate module: :SWANK-ARGLISTS
[Condition of type SIMPLE-ERROR]

Backtrace:
0: (SWANK::MODULE-FILENAME :SWANK-ARGLISTS)
1: (SWANK:SWANK-REQUIRE :SWANK-ARGLISTS NIL)
2: (SB-INT:SIMPLE-EVAL-IN-LEXENV
(SWANK:SWANK-REQUIRE :SWANK-ARGLISTS)
#)
3: ((LAMBDA ()))
4: ((LAMBDA (SWANK-BACKEND::HOOK SWANK-BACKEND::FUN))
#
#)
5: (SWANK::SLDB-LOOP 6)
6: (SWANK::CALL-WITH-BINDINGS
((*PRINT-PRETTY* . T) (*PRINT-LEVEL* . 4) (*PRINT-LENGTH* . 10)
(*PRINT-PPRINT-DISPATCH*
. #)
(*PRINT-GENSYM* . T) (*PRINT-BASE* . 10) (*PRINT-RADIX*)
(*PRINT-ARRAY* . T) …)
#)
7: ((LAMBDA (SWANK-BACKEND::DEBUGGER-LOOP-FN))
#)
8: (SWANK::DEBUG-IN-EMACS #)
9: (INVOKE-DEBUGGER #)
10: (INVOKE-DEBUGGER #)
11: (ERROR “Can’t locate module: ~s”)
12: (SWANK::MODULE-FILENAME :SWANK-ARGLISTS)
13: (SWANK:SWANK-REQUIRE :SWANK-ARGLISTS NIL)
14: (SB-INT:SIMPLE-EVAL-IN-LEXENV
(SWANK:SWANK-REQUIRE :SWANK-ARGLISTS)
#)
15: ((LAMBDA ()))
16: ((LAMBDA (SWANK-BACKEND::HOOK SWANK-BACKEND::FUN))
#
#)
17: (SWANK::SLDB-LOOP 5)
18: (SWANK::CALL-WITH-BINDINGS
((*PRINT-PRETTY* . T) (*PRINT-LEVEL* . 4) (*PRINT-LENGTH* . 10)
(*PRINT-PPRINT-DISPATCH*
. #)
(*PRINT-GENSYM* . T) (*PRINT-BASE* . 10) (*PRINT-RADIX*)
(*PRINT-ARRAY* . T) …)
#)
19: ((LAMBDA (SWANK-BACKEND::DEBUGGER-LOOP-FN))
#)
–more–

2. That module (swank-arglists) should be bound into the core file that the SBCL in Ready Lisp starts from. Are you running with a Core2 Duo, as I am?

3. Yes, I am running it on Core 2 Duo 2.2GHz.

4. Ok, it is fixed and I’ve uploaded the new version. Let me know if there are any more troubles!

5. i cannot get this to work on macbook with osx 10.5, diskimagemounter says that it cannot mount image, any help?

6. Thanks, it works without any errors at all.

7. anonymous: Please check the validity of the disk images by using the “md5″ command, and comparing the result to what’s in the MD5SUMS.txt file on my FTP server. It sounds like your disk image got corrupted somehow.

Thanks.

9. I do not understand why it was not compiled also for powerpc processors.

Roberto

10. Awesome stuff. Thanks for putting this together. Fantastic way to get started with Lisp.

11. With regards to the image not mounting, if it downloads as a .dmg.bz2 file you might have to rename it to a .dmg file and then open it.

12. Roberto: SBCL 1.0.11 does not compile on Leopard for PowerPC. This is a problem in the SBCL sources that needs to be fixed in a future release. When it is, I’ll include PPC support.

13. John: ok, I did not know that it would not compile. I have seen 1.0.2 (IIRC) binaries, I thought it was then a kind of “permanent” support.

14. SBCL compiles for PowerPC just fine under 10.4. So expect support sometime soon.

15. I have been able to manually install the 1.0.2 binaries and have running them in Aquamacs EMACS 1.2a with slime. Now I am compiling 1.0.11 on another machine (a g5, in fact I am compiling it with itself to check everything was ok) and I will then transfer it to my powerbook g4 – if it breaks then this will mean that there is 64 bit ppc support

16. thanks for this. but I can’t exit normally, I have to force quit.

17. I’m using the 10.4 image when I start up I’m getting the following error:

Can’t locate module: :SWANK-ASDF
[Condition of type SIMPLE-ERROR]

I can post the backtrace if you want it.

If I exit from the error everything seemed to be working correctly. I download the image last night.

18. I’m not able to support the 10.4 version anymore, as I don’t have access to that OS (all of my systems have been upgraded to Leopard). The error you’re seeing sounds very familiar, and I believe it results from invalid pathnames in the pre-built core file. Unfortunately, I can think of no easy solution to this. You could try visiting http://hg.newartisans.com/readylisp, and downloading the files there, by which you might be able to create a working core file for yourself. But this route is not for the faint at heart!

19. I end up rolling my own with the latest Aquamacs, Slime, and SBCL. Generating the core file is definiately not an easy task especially for a newbie like me. However, it has been a good learning experience.

I used Ready Lisp as a guide line, and it has helped me some. My hand rolled version is not as nice as Ready Lisp, but it seems to work ok.

I would like to ask you questions on the configuration setup of Ready Lisp in more detail. If that would be ok with you drop me an email.

Thanks

20. Thanks for doing this. Could you please make the latest .dmg work for Tiger as soon as you can.

Thanks,
Raj

21. Raj, it is now much, much easier to build your own Ready Lisp. Pull the version available through Git (this is mentioned on the project page). However, it will still not run correctly on 10.4 yet. I have found a running copy of 10.4, I just haven’t had the time yet to get a copy of Ready Lisp running under that OS. Sometime soon, though, probably at the same time as the next upgrade.