Re: [racket-dev] Places -- on by default in v5.1.1.2. (git master)

2011-04-21 Thread Eli Barzilay
Two days ago, Kevin Tew wrote: This means that parallel zo and doc builds will use places instead of processes. Report bugs as usual :) Here's a major bug: the memory consumption is *horrible*. Winooski, the main build machine, has 4 cores and 4gb ram. Things used to be pretty bad with 4

Re: [racket-dev] Places -- on by default in v5.1.1.2. (git master)

2011-04-21 Thread Matthew Flatt
At Thu, 21 Apr 2011 05:33:47 -0400, Eli Barzilay wrote: Two days ago, Kevin Tew wrote: This means that parallel zo and doc builds will use places instead of processes. Report bugs as usual :) Here's a major bug: the memory consumption is *horrible*. Ok, we'll disable for now and

[racket-dev] Places -- on by default in v5.1.1.2. (git master)

2011-04-19 Thread Kevin Tew
The configure script has been changed to enable places by default. Note: places are NOT enabled by default for the upcoming V5.1.1 release. This means that parallel zo and doc builds will use places instead of processes. Report bugs as usual :) Kevin

Re: [racket-dev] Places -- on by default in v5.1.1.2. (git master)

2011-04-19 Thread John Clements
On Apr 19, 2011, at 8:27 AM, Kevin Tew wrote: The configure script has been changed to enable places by default. Note: places are NOT enabled by default for the upcoming V5.1.1 release. This means that parallel zo and doc builds will use places instead of processes. Should I expect to

Re: [racket-dev] Places -- on by default in v5.1.1.2. (git master)

2011-04-19 Thread Kevin Tew
On 04/19/2011 10:26 AM, John Clements wrote: On Apr 19, 2011, at 8:27 AM, Kevin Tew wrote: The configure script has been changed to enable places by default. Note: places are NOT enabled by default for the upcoming V5.1.1 release. This means that parallel zo and doc builds will use places