Re: [racket-dev] module mismatch with .zos

2012-10-18 Thread Dan Liebgold
Just a quick update. I now run racket pointing to a main collects dir with only .zo files. It is working quite well! Now I'm eyeing Jay McCarthy's archive code ;) On Tue, Oct 16, 2012 at 12:23 PM, Matthew Flatt mfl...@cs.utah.edu wrote: At Tue, 16 Oct 2012 14:04:32 -0500, Robby Findler wrote:

Re: [racket-dev] module mismatch with .zos

2012-10-16 Thread Dan Liebgold
It seems like the timestamps among just the .zo and .dep files will cause us issues as well due to how Perforce works. When you sync, Perforce sets the timestamp of the file to the time of sync. If I sync all of a Racket distribution my file timestamps will not be coherent from Racket's point of

Re: [racket-dev] module mismatch with .zos

2012-10-16 Thread Eli Barzilay
A few minutes ago, Dan Liebgold wrote: It seems like the timestamps among just the .zo and .dep files will cause us issues as well due to how Perforce works. When you sync, Perforce sets the timestamp of the file to the time of sync. If I sync all of a Racket distribution my file timestamps

Re: [racket-dev] module mismatch with .zos

2012-10-16 Thread Dan Liebgold
To be clear, we don't have any steps between sync in perforce and running racket. This is for end users who don't edit or compile source. It is also part of a toolchain where Racket is just one optional piece and so we can't really spare the time to build zos at this particular point. We really do

Re: [racket-dev] module mismatch with .zos

2012-10-16 Thread Dan Liebgold
On Tue, Oct 16, 2012 at 12:04 PM, Robby Findler ro...@eecs.northwestern.edu wrote: (FWIW, it is not really wrong to consider this behavior a bug at a number of different levels (why rely on timestamps? why does compilation not produce the same thing each time?) and it is something we've

[racket-dev] module mismatch with .zos

2012-10-15 Thread Dan Liebgold
We're having trouble with .zos. We trigger the module mismatch, probably from old bytecode whose dependencies have changed: error on occasion and I'm not sure why. Can someone explain possible solutions? We distribute the Racket install and our own code with .zos and it works for most everyone,

Re: [racket-dev] module mismatch with .zos

2012-10-15 Thread Matthew Flatt
Is there any chance that the .zo file timestamps became earlier than the .rkt timestamps on end-users' machines? Users are better off with the .dep files. I think `raco make' would use them, for example. At Mon, 15 Oct 2012 15:10:18 -0700, Dan Liebgold wrote: We're having trouble with .zos. We

Re: [racket-dev] module mismatch with .zos

2012-10-15 Thread Dan Liebgold
On Mon, Oct 15, 2012 at 5:23 PM, Matthew Flatt mfl...@cs.utah.edu wrote: Is there any chance that the .zo file timestamps became earlier than the .rkt timestamps on end-users' machines? Yes that is possible... we're distributing using Perforce, which timestamps files at the time of syncing.

Re: [racket-dev] module mismatch with .zos

2012-10-15 Thread Robby Findler
On Mon, Oct 15, 2012 at 7:59 PM, Dan Liebgold dan.liebg...@gmail.com wrote: On Mon, Oct 15, 2012 at 5:23 PM, Matthew Flatt mfl...@cs.utah.edu wrote: Is there any chance that the .zo file timestamps became earlier than the .rkt timestamps on end-users' machines? Yes that is possible... we're