Elmo Mäntynen wrote: > Elmo Mäntynen wrote: > >> Elmo Mäntynen wrote: >> >> >>> Armin Rigo wrote: >>> >>> >>> >>>> Hi Elmo, >>>> >>>> On Wed, Jul 19, 2006 at 04:11:58PM +0300, Elmo M??ntynen wrote: >>>> >>>> >>>> >>>> >>>>> Last lines of output (python translate.py --backend=c --profopt='-c >>>>> "from richards import *;main(iterations=1)"' --text --batch >>>>> targetpypystandalone.py): >>>>> >>>>> >>>>> >>>>> >>>> I have no clue how --profopt can affect the translation itself. You >>>> don't get the same error without the --profopt option? >>>> >>>> >>>> A bientot, >>>> >>>> Armin >>>> >>>> >>>> >>>> >>> Should've tested that, will do as soon as possible. benchmark.html on >>> snake shows something that says to me that the profopt executable >>> doesn't exist, which suggests that it wasn't built. >>> >>> Elmo >>> >>> >>> >> Translation without profopt worked now, though there might have been >> something that got changed in between, will report after some more builds. >> >> > Now I got an internal compiler error from cc: > """ > [cbuild:profopt] Gathering profile data from: > /tmp/usession-11/testing_1/testing_1 -c "from richards import > *;main(iterations=1)" > > ... > [translation:ERROR] File > "/usr/lib/python2.4/distutils/unixccompiler.py", line 115, in _compile > [translation:ERROR] raise CompileError, msg > [translation:ERROR] CompileError: command 'cc' failed with exit status 1 > """ > If this really calls for a bugreport, it would be better if some one > more comfortable with the compiling process and the gcc toolset would do > it. Should I send some of the produced files? > Just to note that building without profopt works (this time its the same rev).
Elmo _______________________________________________ [email protected] http://codespeak.net/mailman/listinfo/pypy-dev
