<div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> If you still have the old version, try mzc on the two versions (split and unsplit), as Noel mentioned, and see if that changes anything. </blockquote><div> I have an additional collection path, but using "++collects-dir /my-path-to-collect/" does not seem do that. It returns the error: standard-module-name-resolver: collection not found: "common" in any of: (#<path:/home/orseau/.racket/<a href="http://5.0.1.2/collects">5.0.1.2/collects</a>> #<path:/usr/plt-5.0.1.2/collects>) I tried "--collects-dest" too, but same problem. I suppose I could add each lib by hand with "++lib", but there are a number of them. Isn't there a way to add a collection path to mzc? </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> (Also, and this is probably a dumb question, but you didn't change any behavior when you split things up accidentally, did you?) </blockquote><div> Dumb questions are often the most important ones of course. There have been other changes but I don't really expect them to be noticeable. Although with the change, I am now using setter generators for variables to cross the module barrier, whereas those variables were initially directly in the same module. There are not many of them though, so I'm not sure if that could change anything at all. I also wondered if there could be something related to runtime-paths, but that's just a thought. </div></div>