[hunchentoot-devel] compiling 1.1.1 specials.lisp takes too long

Edi Weitz edi at agharta.de
Sat Aug 28 20:39:02 UTC 2010


I think AllegroCL is confused here.  The name DEFCONSTANT is shadowed
in the Hunchentoot package, so there's no need for a warning and
certainly the compiler shouldn't freeze. Compiling specials.lisp
should usually take only fractions of a second.

I'd report the problem to Franz.

Edi.



On Sat, Aug 28, 2010 at 9:14 PM, Yakov Zaytsev <zaytsev.yakov at gmail.com> wrote:
> Hello,
>
> with ACL 8.2 (professional license) on windows 7 on Atom Z540 with
> 2GiBs of memory trying to
>
> (asdf:oos 'asdf:load-op :hunchentoot)
>
> ends with
>
> ;;; Compiling file c:\lisplibs\hunchentoot-1.1.1\specials.lisp
> ; While compiling (:top-level-form "specials.lisp" 1551):
> Warning: Compiling a function definition for the name defconstant as a
> defmacro.  This name is in the common-lisp
>         package and redefining it will be a violation for portable
> programs.  Replacing the current definition of
>         #<macro defconstant @ #x20107e32> may be dangerous.  The
> package common-lisp has
>         excl:package-definition-lock set, which causes the system to
> signal this violation.
>
> and it seems like it freezes there. Is it normal? How long does it
> take typically to compile that specials.lisp?
>
> TIA!
>
> _______________________________________________
> tbnl-devel site list
> tbnl-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/tbnl-devel
>
>




More information about the Tbnl-devel mailing list