Carl, it looks like the error came from your scheme.plt package. I'm not sophisticated enough yet to need sandboxes - particularly in a scribble manual.
Doug On Thu, Mar 19, 2009 at 11:51 AM, Carl Eastlund <[email protected]>wrote: > Hmm. I believe I started getting this kind of error after recent > changes to the sandbox library, when I used sandboxes for examples in > Scribble documentation. I stopped getting the error when I started > using call-with-trusted-sandbox-configuration to construct the > appropriate sandbox. In fact, (planet cce/scheme/sandbox) exports > make-trusted-evaluator, make-trusted-module-evaluator, > make-scribble-evaluator, and make-scribble-module-evaluator that are > designed to work around this bug (and one other peculiarity of > sandboxes for Scribble examples). > > Give either method of making trusted sandboxes a try, if your packages > use sandboxed examples, and see if the problem goes away. > > --Carl > > On Thu, Mar 19, 2009 at 1:04 PM, Doug Williams > <[email protected]> wrote: > > I am getting many warnings/errors from some of the PLaneT packages that I > > don't remember seeing in the past: > > > > compile: access from an uncertified context to unexported variable from > > module: "C:\Program Files\PLT\collects\scheme\private\stxloc.ss" > > setup-plt: error: during Building docs for C:\Documents and > > Settings\dwilliams\Application Data\PLT > > Scheme\planet\300\4.1.4.900\cache\cce\scheme.plt\1\3\manual.scrbl > > setup-plt: compile: access from an uncertified context to unexported > > variable from module: "C:\Program > > Files\PLT\collects\scheme\private\stxloc.ss" > > WARNING: collected information for key multiple times: (mod-path "(planet > > schematics/sake)"); values: #(#<path:C:\Documents and > > Settings\dwilliams\Application Data\PLT > > > Scheme\planet\300\4.1.4.900\cache\schematics\sake.plt\1\0\doc\sake\Build_files.html> > > ("Build files") #t (mod-path "(planet schematics/sake)")) > > #(#<path:C:\Documents and Settings\dwilliams\Application Data\PLT > > > Scheme\planet\300\4.1.4.900\cache\schematics\sake.plt\1\0\doc\sake\The_Sake_API.html> > > ("The Sake API") #t (mod-path "(planet schematics/sake)")) > > WARNING: collected information for key multiple times: (index-entry > > (mod-path "(planet schematics/sake)")); values: (("(planet > > schematics/sake)") (#(struct:sized-element ... ...)) > > #<module-path-index-desc>) (("(planet schematics/sake)") > > (#(struct:sized-element ... ...)) #<module-path-index-desc>) > > WARNING: collected information for key multiple times: (mod-path "(planet > > schematics/sake)"); values: #(#<path:C:\Documents and > > Settings\dwilliams\Application Data\PLT > > > Scheme\planet\300\4.1.4.900\cache\schematics\sake.plt\1\0\doc\sake\Build_files.html> > > ("Build files") #t (mod-path "(planet schematics/sake)")) > > #(#<path:C:\Documents and Settings\dwilliams\Application Data\PLT > > > Scheme\planet\300\4.1.4.900\cache\schematics\sake.plt\1\0\doc\sake\The_Sake_API.html> > > ("The Sake API") #t (mod-path "(planet schematics/sake)")) > > WARNING: collected information for key multiple times: (index-entry > > (mod-path "(planet schematics/sake)")); values: (("(planet > > schematics/sake)") (#(struct:sized-element ... ...)) > > #<module-path-index-desc>) (("(planet schematics/sake)") > > (#(struct:sized-element ... ...)) #<module-path-index-desc>) > > > > I cleared out my PLaneT cache prior to loading the new version, so some > may > > be new versions of the packages. I'm not as concerned about the warnings > as > > about the first ones that seem to be errors. > > > > Is this indicative of some problem? > > > > Doug > > > > > > On Thu, Mar 19, 2009 at 5:30 AM, Eli Barzilay <[email protected]> wrote: > >> > >> Checklist items for the v4.1.5 release > >> (using the v4.1.4.900 alpha build) > >> > >> Search for your name to find relevant items, reply when you finish > >> an item (please indicate which item is done). Also, if you have > >> any commits that should have been merged, make sure that they're > >> in. > >> > >> Important: new builds are created without announcement, usually > >> whenever I see significant commits. If you need to commit changes, > >> please make sure you tell me to merge it to the release branch. > >> > >> --> Release candidates are at > >> --> http://pre.plt-scheme.org/release/installers > >> > >> Please use these installers (or source bundles) -- don't test from > >> your own svn chekout (don't test v4.1.5.1 by mistake!). To get > >> the tests directory in the normal release, you can do this: > >> cd .../collects > >> svn export http://svn.plt-scheme.org/plt/release/collects/tests > >> > >> ---------------------------------------------------------------------- > >> > >> *** Testing: > >> > >> * Kathy Gray <[email protected]> > >> - ProfJ Tests > >> - Test Engine Tests > >> > >> * Noel Welsh <[email protected]>, Chongkai Zhu <[email protected]> > >> - SRFI Tests > >> - Ensure that all claimed srfi's are in the bundle and they all load > >> into mzscheme or drscheme (as appropriate) > >> > >> * Sam Tobin-Hochstadt <[email protected]> > >> - Match Tests > >> - Typed Scheme Tests > >> > >> * Doug Williams <[email protected]> > >> - Plot Tests > >> > >> -- > >> ((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay: > >> http://www.barzilay.org/ Maze is Life! >
_________________________________________________ For list-related administrative tasks: http://list.cs.brown.edu/mailman/listinfo/plt-dev
