Sorry for my persistent pesky behavior but I still need your help.

I have installed the latest version of metatilities (0.6.18) and now I
get the following restart when loading it:

component :METABANG-DYNAMIC-CLASSES not found, required by
#<ASDF:SYSTEM "cl-containers" 2009CD03>

Searching Cliki for a system called "metabang-dynamic-classes" yields
"metatilities-latest" which I already had. I downloaded it and
installed it afresh but the above message does not go away. Is there a
system called METABANG-DYNAMIC-CLASSES or is this another name for
"metatilities"? What should I do?

On Jul 2, 1:35 pm, "Leslie P. Polzer" <[email protected]>
wrote:
> Harrison Maseko wrote:
> > OK, here's the full message:
>
> > **++++ Error in (PACKAGE "WEBLOCKS"):
> >   Using package METABANG.UTILITIES results in name conflicts for these
> > symbols: ANAPHORA:ACOND ANAPHORA:IT ANAPHORA:APROG1 ANAPHORA:AIF
> > ANAPHORA:AWHEN ANAPHORA:AAND ANAPHORA:ATYPECASE ANAPHORA:ACOND ANAPHORA:IT
> > ANAPHORA:APROG1 ANAPHORA:AIF ANAPHORA:AWHEN ANAPHORA:AAND
> > ANAPHORA:ATYPECASE.
> > ; (TOP-LEVEL-FORM 2)
> > ; *** 1 error detected, no fasl file produced.
> > Warning: COMPILE-FILE warned while performing #<ASDF:COMPILE-OP NIL
> > 219CA9E3>
> >          on #<ASDF:CL-SOURCE-FILE "package" 2191059B>.
> > Warning: COMPILE-FILE failed while performing #<ASDF:COMPILE-OP NIL
> > 219CA9E3>
> >          on #<ASDF:CL-SOURCE-FILE "package" 2191059B>.
>
> Could it be that your Metatilities are too old?
>
> I have version 0.6.18 (as per metatilities.asd) and AWHEN
> is an internal symbol there.
>
> The Metatilities package had some substantial changes
> about half a year ago.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"weblocks" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/weblocks?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to