[Openmcl-devel] Re: building MCL for idiots (fwd)

Gary Byers gb at clozure.com
Sat Feb 28 02:18:38 UTC 2004



On Thu, 26 Feb 2004, Gary Byers wrote:
> >
> > On Thu, 26 Feb 2004, Cyrus Harmon wrote:
> >
> >>
> >>
> >> It's hard to know whether or not you're up to date on all of the
> >> various pieces. After poking around for quite a while, getting a new
> >> lisp kernel built, getting the interface database from 1.14p1, I get
> >> the following:
> >>
> >> ? (ccl:xload-level-0)
> >> Can't find #4P"ccl:xdump;xppcfasload.dfsl" so requiring
> >> "ccl:xdump;xppcfasload.lisp" instead
> >> Can't find #4P"ccl:xdump;xfasload.dfsl" so requiring
> >> "ccl:xdump;xfasload.lisp" instead
> >> Can't find #4P"ccl:xdump;heap-image.dfsl" so requiring
> >> "ccl:xdump;heap-image.lisp" instead
> >> ;Compiling
> >> "/Users/sly/src/openmcl/ccl-0.14/ccl/level-0/l0-cfm-support.lisp"...
> >> ;Compiling
> >> "/Users/sly/src/openmcl/ccl-0.14/ccl/level-0/l0-clos.lisp"...
> >> ;Compiling
> >> "/Users/sly/src/openmcl/ccl-0.14/ccl/level-0/l0-complex.lisp"...
> >> ;Compiler warnings for
> >> "/Users/sly/src/openmcl/ccl-0.14/ccl/level-0/l0-complex.lisp" :
> >> ;   Undefined function %IMAGPART, in COERCE-TO-COMPLEX-TYPE.
> >> ;   Undefined function %REALPART, in COERCE-TO-COMPLEX-TYPE.


Aside from questions of how this whole process could be simplified,
automated, or explained better, there's quite simply a bug here:
%REALPART and %IMAGPART are macros, and whatever file defines
them should be REQUIREd at compile time in ccl:level-0;l0-complex.lisp.




More information about the Openmcl-devel mailing list