Thanks. They stay for a while (4 more runs by default), so they're deleted but not immediately.
Cheers, fijal On Thu, Nov 19, 2009 at 6:03 PM, Leo Trottier <[email protected]> wrote: > The .s files are typically removed when the build fails. I've managed to > grab one, I think, before it got deleted. > You'll see it fail in the log, presumably in the same way, here: > http://paste.pocoo.org/show/151704/ > I've abused paste.pocoo and posted it > here: http://paste.pocoo.org/show/151706/ > (I've also attached it) > Leo > > On Thu, Nov 19, 2009 at 4:19 AM, Maciej Fijalkowski <[email protected]> > wrote: >> >> Hey. >> >> This seems to be a problem with trackgcroot, can you put up offending >> .s file (implement_5.s) somewhere? If not, send it to me by mail, I'll >> do it. >> >> On Thu, Nov 19, 2009 at 1:13 PM, Leo Trottier <[email protected]> wrote: >> > As requested: >> > http://paste.pocoo.org/show/151641/ >> > >> > On Thu, Nov 19, 2009 at 4:06 AM, Amaury Forgeot d'Arc >> > <[email protected]> >> > wrote: >> >> >> >> 2009/11/19 Leo Trottier <[email protected]>: >> >> > [apologies for the spam, but people seem interested] >> >> > On Snow Leopard, after adding the -m32 flags recommended by Leonardo, >> >> > it >> >> > got >> >> > all the way to compilation, and then failed. I had tried to do a >> >> > c-jit >> >> > compile over the latest trunk using 32bit python. >> >> > Here is the full run log: http://paste.pocoo.org/show/151639/ >> >> >> >> Unfortunately, the log does not show all compilation output. >> >> Again you should do it manually: >> >> >> >> cd >> >> >> >> /var/folders/S+/S+mQx368HdO8O9qxkcyoQk+++TI/-Tmp-/usession-trunk-0/testing_1 >> >> make >> >> >> >> -- >> >> Amaury Forgeot d'Arc >> > >> > >> > _______________________________________________ >> > [email protected] >> > http://codespeak.net/mailman/listinfo/pypy-dev >> > > > _______________________________________________ [email protected] http://codespeak.net/mailman/listinfo/pypy-dev
