Hans Halvorson hhalvors@Princeton.EDU writes:
I upgraded to cmucl-19d (unstable), and I was having trouble accessing the cmucl-clx libraries. (Are they not installed with 19d?) So, I
Hi Hans,
With dev-lisp/cmucl-19d_pre1, dev-lisp/sbcl-0.9.18 and dev-lisp/clisp-2.41 (all committed to CVS last night), we've stopped using the Common Lisp Controller. Before with CMUCL 19c and the Common Lisp Controller, the clx subsystem, and other CMUCL subsystems (clm, gray-streams, simple-streams, hemlock etc.) were installed with ASDF system definitions.
Now you need to do things the CMUCL way, the way the upstream developers intended:
$ lisp CMU Common Lisp CVS Head 2006-10-28 01:59:57 (19D), running on localhost With core: /usr/lib/cmucl/lib/lisp.core Dumped on: Sat, 2006-10-28 02:17:51-05:00 on localhost See http://www.cons.org/cmucl/ for support information. Loaded subsystems: Python 1.1, target Intel x86 CLOS based on Gerd's PCL 2004/04/14 03:32:47 * (require :clx)
; Loading #P"/usr/lib/cmucl/lib/subsystems/clx-library.x86f". ; [GC threshold exceeded with 12,011,280 bytes in use. Commencing GC.] ; [GC completed with 2,940,480 bytes retained and 9,070,800 bytes freed.] ; [GC will next occur when at least 14,940,480 bytes are in use.] ("CLX") *
We have an upgrade guide here:
http://www.gentoo.org/proj/en/common-lisp/guide.xml
It describes how to use the Common Lisp libraries in the absence of the Common Lisp Controller. It doesn't mention the change to loading CLX for CMUCL though. I'll add a section on that tonight and also link the guide from the project page:
http://www.gentoo.org/proj/en/common-lisp/index.xml
downgraded to 19c. But now when I try to start cmucl, I get:
"Strange ... dynamic space lossage Segmentation fault."
I'm not sure what would cause that problem, especially since your CMUCL 19c ran fine under the same configuration. Could you file a bug report? Make sure to include the output of emerge --info.
Best regards,
Matt