[Openmcl-devel] 0.13.x vs. 0.14.x
gb at clozure.com
Mon Jan 5 00:13:14 UTC 2004
On Sun, 4 Jan 2004, Raffael Cavallaro wrote:
> On Jan 4, 2004, at 5:13 PM, Raffael Cavallaro wrote in reply to Sven
> Van Caekenberghe:
> >> Have a look at http://homepage.mac.com/svc/DW-Bench
> > I'll get paserve set up and run some tests as soon as I get a chance.
> Hmm. Seems paserve requires defsystem, not asdf.
Recent versions of of paserve use asdf (and are conditionalized for
:openmcl-native-threads). AFAIK, those recent versions are only
available via CVS; see <http://sourceforge.net/projects/portableaserve>.
> Is there a version of
> defsystem which works with openmcl? the version I've downloaded from
> sourceforge (3.3i.1) doesn't seem to work with openmcl 0.14-031220. It
> seems that loading defsystem.lisp runs into a snag where it expects
> require to be an external symbol of the ccl package:
> No external symbol named "PROVIDE" in package #<Package "CCL">
> While executing: CCL::%PARSE-TOKEN
> I don't know enough about this to guess. Should provide be exported
> from ccl, or is defsystem making an unwarranted assumption, or do I
> need to reconditionalize all the #+:mcl to #+:openmcl? All/some of the
> Any pointers from those who have used defsystem with openmcl
The copyright notice for mk-defsystem says (in part)
;;; Use, copying, modification, merging, publishing, distribution
;;; and/or sale of this software, source and/or binary files and
;;; associated documentation files (the "Software") and of derivative
;;; works based upon this Software are permitted, as long as the
;;; following conditions are met:
;;; o this copyright notice is included intact and is prominently
;;; visible in the Software
;;; o distribution of a modification to the Software have been
;;; previously submitted to the maintainers; if the maintainers
;;; decide not to include the submitted changes, the "full
;;; name" of the re-distributed Software ("MK:DEFSYSTEM", or
;;; "MAKE:DEFSYSTEM", or "MK-DEFSYSTEM") must be changed.
I tried a few times to contact the maintainers and didn't have much
luck. I once mentioned this to Marco Antoniotti in person and, IIRC,
he said "don't worry about it, go ahead and distribute it.". I forgot.
I might actually have commit access to CLOCC; if I do, distributing
the openmcl-related changes may be a simple matter of submitting them
to myself and deciding to accept them ...
> Raffael Cavallaro, Ph.D.
> raffaelcavallaro at mac.com
More information about the Openmcl-devel