Oh! Thanks. Talk about a wild goose chase. So .. should planet be invoking setup-plt with flags that control the documentation generation more carefully in order to speed up things?
Robby On Wed, Jun 17, 2009 at 1:01 AM, Matthew Flatt<mfl...@cs.utah.edu> wrote: > At Mon, 1 Jun 2009 08:58:46 -0500, Robby Findler wrote: >> I think PLaneT does indeed work that way. Even worse, there is a bug >> somewhere that causes CM to not compile package B (or C or D ...) >> making things even worse. I got as far as figuring out that it was a >> parameter that changed (I think it was the namespace?) that somehow >> causes CM to disable itself, but I could not figure out what the right >> fix was. I believe the right fix is to be using a new instantiation of >> CM and the code seems to be doing that, but apparently it isn't. > > That doesn't seem to be a problem, actually. When A requires B, the > "skipping" messages for B come from the outer CM for A, while an inner > instance of CM is correctly compiling B. > > I changed `compiler/compiler-unit' slightly so that it "binds" the CM > trace handler that it installs to a particular port, and that avoids > the confusing printout. > > _________________________________________________ For list-related administrative tasks: http://list.cs.brown.edu/mailman/listinfo/plt-dev
