Re: [pypy-dev] pypy-2.0 package issue

2013-06-02 Thread David Roid
Thanks Armin! An upgrade from sqlite 3.3 to 3.6 solved this problem. Regards -David 2013/6/2 Armin Rigo > Hi David, > > On Sun, Jun 2, 2013 at 1:51 AM, David Roid wrote: > > CentOS 5.8 x64. The translation was successful with pypy-c generated, but > > subsequent packaging went wrong with foll

Re: [pypy-dev] cpython changed _sre between 2.7.3 to 2.7.4, now intmask(pattern) is negative

2013-06-02 Thread Matti Picus
Making it a r_uint did not work for me, apparently the pattern bytecode should be signed. It would seem to me we would want to be cpython compatible, that is it should be of size SRE_CODE from the _sre cpython module which has changed to 4. Maybe someone else wants t

Re: [pypy-dev] cpython changed _sre between 2.7.3 to 2.7.4, now intmask(pattern) is negative

2013-06-02 Thread Maciej Fijalkowski
pfff, just make it r_uint maybe? Also, what are legal values on CPython? On Mon, Jun 3, 2013 at 4:58 AM, Matti Picus wrote: > Running own tests on win32 gives many errors in the _sre module: > rlib/rsre/rsre_core.py:111: AssertionError > which is checking that all values of the pattern are >=0 >

[pypy-dev] cpython changed _sre between 2.7.3 to 2.7.4, now intmask(pattern) is negative

2013-06-02 Thread Matti Picus
Running own tests on win32 gives many errors in the _sre module: rlib/rsre/rsre_core.py:111: AssertionError which is checking that all values of the pattern are >=0 Here is one of many such failures: http://buildbot.pypy.org/summary/longrepr?testname=TestMatch.%28%29.test_repeated_set&builder=own-

Re: [pypy-dev] why does jit.backend.x86.test.test_fficall crash python on win32?

2013-06-02 Thread Armin Rigo
Hi Matti, On Sun, Jun 2, 2013 at 6:00 PM, Matti Picus wrote: > I have been trying to whip win32 own tests into passing, or at least to an > understanding of why they fail. Fixed in 663474f13069; it turned out to be just a stupid mistake (the random value abi=42 in the metainterp test was used al

Re: [pypy-dev] why does jit.backend.x86.test.test_fficall crash python on win32?

2013-06-02 Thread Amaury Forgeot d'Arc
2013/6/2 Matti Picus > I have been trying to whip win32 own tests into passing, or at least to > an understanding of why they fail. > I am seeing the interpreter crash on the > jit.backend.x86.test.test_fficall.py, here is a traceback > http://bpaste.net/show/cM9YptahKH0PkZjp5gtN/ > and the orig

[pypy-dev] why does jit.backend.x86.test.test_fficall crash python on win32?

2013-06-02 Thread Matti Picus
I have been trying to whip win32 own tests into passing, or at least to an understanding of why they fail. I am seeing the interpreter crash on the jit.backend.x86.test.test_fficall.py, here is a traceback http://bpaste.net/show/cM9YptahKH0PkZjp5gtN/ and the original

Re: [pypy-dev] pypy-2.0 package issue

2013-06-02 Thread Armin Rigo
Hi David, On Sun, Jun 2, 2013 at 1:51 AM, David Roid wrote: > CentOS 5.8 x64. The translation was successful with pypy-c generated, but > subsequent packaging went wrong with following error: > > > /root/pypy-2.0-src/lib_pypy/__pycache__/_cffi__gb0f282f4xe752c2be.c: In > function ‘_cffi_cons