[issue1498] Memory-mapping /dev/zero causes an error on Mac OS X

[Dan Villiom Podlaski Christiansen]

New submission from Dan Villiom Podlaski Christiansen <danchr at gmail.com>:

In the new pure modules, an attempt to memory-map ‘/dev/zero’ is made in 
‘mpatch.py’; this will fail on Mac OS X 10.5. Judging from the Python 
documentation, mapping a file descriptor of -1 will have the intended results of 
allocating a new, private region. The attached patch does that, causing the 
Mercurial build to succeed.

Assigning to Martin Geisler, who wrote the pure implementation. I hope that's 
okay?

----------
assignedto: mg
files: mpatch-pure-macosx.diff
messages: 8549
nosy: danchr, mg
priority: bug
status: unread
title: Memory-mapping /dev/zero causes an error on Mac OS X

____________________________________________________
Mercurial issue tracker <mercurial-bugs at selenic.com>
<http://www.selenic.com/mercurial/bts/issue1498>
____________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mpatch-pure-macosx.diff
Type: application/octet-stream
Size: 605 bytes
Desc: not available
Url : http://selenic.com/pipermail/mercurial-devel/attachments/20090202/53e2f14f/attachment.obj