Hi Ronny,
On Thu, May 19, 2011 at 8:30 PM, Ronny Pfannschmidt
wrote:
> why not run the translation in a subprocess to begin with?
It doesn't change much, except that it would break half of the
non-standard use cases of translate.py, like --fork-before.
Armin.
__
On Thu, 2011-05-19 at 18:34 +0200, Armin Rigo wrote:
> Hi,
>
> On Thu, May 19, 2011 at 6:00 PM, Maciej Fijalkowski wrote:
> > If the only goal is to avoid doing those 2 at the same time, do
> > translate.py --source and then go to the /tmp/usession-*/testing_1
> > directory and type make
>
> We
Hi,
On Thu, May 19, 2011 at 6:00 PM, Maciej Fijalkowski wrote:
> If the only goal is to avoid doing those 2 at the same time, do
> translate.py --source and then go to the /tmp/usession-*/testing_1
> directory and type make
We should decide if it would make sense or not to just do
os.execv("make
On Thu, May 19, 2011 at 5:55 PM, David Naylor wrote:
> Hi,
>
> I'm sure you all know that translating pypy requires a large amount of RAM.
>
> It has been my experience that GCC also uses a large amount of RAM when
> compiling, about 4G. Is it possible to get python/pypy to stop once
> it has wri
Hi,
I'm sure you all know that translating pypy requires a large amount of RAM.
It has been my experience that GCC also uses a large amount of RAM when
compiling, about 4G. Is it possible to get python/pypy to stop once
it has written
the source files and then to run that build process separatel
