[Openmcl-devel] Errror?

Bill St. Clair wws at clozure.com
Sun Aug 19 07:15:28 PDT 2012


Janusz,

That kind of warning is normal when rebuilding trunk. As long as the
build continues and produces a new image file (and kernel, if you
asked for that), all is well. You'll find that the warning won't
repeat if you use the new image to rebuild-ccl again. If it does,
that's a bug, since we want CCL to build itself without warning.

We could prevent this kind of trunk build warning by always uploading
a new image file if building with the old one produced a warning, but
we usually only upload a new image file if building with the old one
has bootstrapping problems, i.e. it errors without finishing.

-Bill

On Sun, Aug 19, 2012 at 4:18 AM, Janusz Podrazik
<info at mracpublishing.com> wrote:
> compiling to the last 1.9 M.
>
> Welcome to Clozure Common Lisp Version 1.9-dev-r15382M-trunk  (Darwinx8664)!
>
> (ccl:rebuild-ccl :full t)
> Rebuilding Clozure Common Lisp using Version 1.9-dev-r15382M-trunk
> (Darwinx8664)
> ;Building lisp-kernel ...
> ….
>
> ;Compiling "/Users/mrac/ccl/level-1/l1-clos.lisp"...;Compiler warnings for
> "ccl:l1;l1-clos.lisp.newest" :
> ;   In snap-reader-methods: Undeclared free variable *clos-optimizations-a
> ;Compiling "/Users/mrac/ccl/level-1/l1-unicode.lisp"...
> ;Compiling "/Users/mrac/ccl/level-1/l1-streams.lisp"...
> ;Compiling "/Users/mrac/ccl/level-1/l1-files.lisp"...
> ;Compiling "/Users/mrac/ccl/level-1/l1-io.lisp"...ctive* (2 references)
> ;Compiler warnings for "ccl:l1;l1-io.lisp.newest" :
> ;   In write-pname: In the call to write-perverted-string with arguments
> (name stream len :invert (if needs-escape #\|)),
> ;     5 arguments were provided, but at most 4 are accepted
>
> ;Compiling "/Users/mrac/ccl/level-1/l1-format.lisp"...
>
>
>
>
>
>
> _______________________________________________
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
> http://clozure.com/mailman/listinfo/openmcl-devel
>



More information about the Openmcl-devel mailing list