On Mon, Apr 30, 2012 at 7:05 PM, Uwe F. Mayer uwe_f_ma...@yahoo.com wrote:
In particular the work-around for the tm structure to get by without the
tm_gmtoff and tm_zone fields may be of interest, as it allows compilation of
the rctime module on systems that don't have it, such as some versions
-
From: Alexander Belopolsky alexander.belopol...@gmail.com
To: Uwe F. Mayer uwe_f_ma...@yahoo.com
Cc: pypy-dev@python.org pypy-dev@python.org
Sent: Wednesday, June 13, 2012 5:22 PM
Subject: Re: [pypy-dev] Patches for Pypy under cygwin
On Mon, Apr 30, 2012 at 7:05 PM, Uwe F. Mayer uwe_f_ma...@yahoo.com
pypy-dev@python.org
Sent: Monday, June 11, 2012 10:27 AM
Subject: Re: [pypy-dev] Patches for Pypy under cygwin
- Original Message -
From: Armin Rigo ar...@tunes.org
Sent: Monday, June 11, 2012 4:59 AM
On Sun, Jun 10, 2012 at 11:12 AM, Amaury Forgeot d'Arc amaur...@gmail.com
wrote:
I
Hi,
On Sun, Jun 10, 2012 at 11:12 AM, Amaury Forgeot d'Arc
amaur...@gmail.com wrote:
I think memory allocated for JIT must be marked with PROT_EXEC (it contains
machine code),
so malloc() is not an option.
Exactly. On Linux it would work, because you can use mprotect() to
make even
2012/6/10 Uwe F. Mayer uwe_f_ma...@yahoo.com
How hard would it be for Pypy to use malloc() instead of mmap() for Cygwin?
I think memory allocated for JIT must be marked with PROT_EXEC (it contains
machine code),
so malloc() is not an option.
--
Amaury Forgeot d'Arc
, setup. I am willing to
pursue that if it would help the project.
--Uwe
From: Armin Rigo ar...@tunes.org
To: Uwe F. Mayer uwe_f_ma...@yahoo.com
Cc: pypy-dev@python.org pypy-dev@python.org
Sent: Sunday, June 3, 2012 2:57 AM
Subject: Re: [pypy-dev] Patches for Pypy
2012/6/7 Uwe F. Mayer uwe_f_ma...@yahoo.com
Currently the Cygwin Pypy Python standalone version build with --opt=jit
fails on os.fork() calls.
fork() on Windows... I'm surprised it works at all!
You should probably read this page:
http://cygwin.com/cygwin-ug-net/highlights.html#ov-hi-process
;
pypy-dev@python.org pypy-dev@python.org
Sent: Thursday, June 7, 2012 10:46 AM
Subject: Re: [pypy-dev] Patches for Pypy under cygwin
2012/6/7 Uwe F. Mayer uwe_f_ma...@yahoo.com
Currently the Cygwin Pypy Python standalone version build with --opt=jit fails
on os.fork() calls.
fork() on Windows
: [pypy-dev] Patches for Pypy under cygwin
2012/6/7 Uwe F. Mayer uwe_f_ma...@yahoo.com
3 [main] pypy-c 11788 fixup_mmaps_after_fork: ReadProcessMemory failed for
MAP_PRIVATE address 0xB001, Win32 error 998
Aha, looks interesting. Searching for this error message, I found that cygwin
unblocks
Hi Uwe,
On Thu, Jun 7, 2012 at 9:21 PM, Uwe F. Mayer uwe_f_ma...@yahoo.com wrote:
3 [main] pypy-c 11788 fixup_mmaps_after_fork: ReadProcessMemory failed
for MAP_PRIVATE address 0xB001, Win32 error 998
Yes, that's one of the mmap addresses used by the JIT, if available.
More to the
I edited / hacked the sources and managed to compile PyPy under Cygwin based on
Python 2.6.7 and gcc-4.5.3. If you find this of interest, the patches are
available at http://www.tux.org/~mayer/cygwin/pypy/.
In particular the work-around for the tm structure to get by without the
tm_gmtoff and
11 matches
Mail list logo
