Hello Jez, First of all – I should have looked into this problem a long time ago and still haven't found the time. I will be away until next week, but then we can work this out together (unless you fix it before that time).
As for your setup, I remember having problems with --opt=0 and so I'm using --opt=2 for now. You can test your setup on the de6baf124c33 changeset (last one before merging with default, still based on sources from around march). Until I come back next week, the only tip I can give is that RPythonGetThreadIdent is being called, when it should not be with ootype typesystem (i.e. the jvm backend). Good luck! Michał On Sun, Jul 1, 2012 at 11:09 AM, Jez <[email protected]> wrote: > On Sun, Jul 1, 2012 at 1:35 AM, Maciej Fijalkowski <[email protected]>wrote: > >> On Sun, Jul 1, 2012 at 2:45 AM, Jez <[email protected]> wrote: >> >>> Hi, >>> >>> I am thinking about contributing to the JVM backend, and I'm trying to >>> build the basic translator for a start. I'm trying out the jvm-improvements >>> branch since there has been some recent work done there, but I can't seem >>> to get it to build. Here's my setup: 32-bit Ubuntu, OpenJDK 6, building >>> with `python translate.py --opt=0 --backend=jvm targetpypystandalone.py`. >>> The translation fails with: >>> >>> [translation:ERROR] File >>> "/mnt/hgfs/jez/src/pypy/pypy/translator/jvm/database.py", line 493, in >>> lltype_to_cts >>> [translation:ERROR] raise AssertionError("Untranslatable type %s!" % >>> OOT) >>> [translation:ERROR] AssertionError: Untranslatable type * Struct >>> timespec { c_tv_sec, c_tv_nsec }! >>> >>> Am I doing something wrong, or is this failure expected? >>> >>> Jez >>> >>> _______________________________________________ >>> pypy-dev mailing list >>> [email protected] >>> http://mail.python.org/mailman/listinfo/pypy-dev >>> >>> >> Hi Jez >> >> As a general note - the branches might fail. As a specific note - I can >> probably help you with this particular problem in a few days. This is some >> timing thing (not sure what) exposed in an ootype unfriendly way. Do you >> want more info about this problem to try to fix yourself? >> >> Cheers, >> fijal >> > > Hey Fijal, > > Yeah, I don't mind taking a stab at it myself if you could tell me where > to start :) > > Cheers, > Jez > > > _______________________________________________ > pypy-dev mailing list > [email protected] > http://mail.python.org/mailman/listinfo/pypy-dev > >
_______________________________________________ pypy-dev mailing list [email protected] http://mail.python.org/mailman/listinfo/pypy-dev
