Showing content from http://mail.python.org/pipermail/python-dev/attachments/20140609/0209acdc/attachment.html below:
<br><br><div>On Mon Jun 09 2014 at 2:07:22 AM, Steven Stewart-Gallus <<a href="mailto:sstewartgallus00@mylangara.bc.ca">sstewartgallus00@mylangara.bc.ca</a>> wrote:</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello,<br>
<br>
I would like some help understanding the build system. I am currently<br>
working on an issue (<a href="http://bugs.python.org/issue21627" target="_blank">http://bugs.python.org/<u></u>issue21627</a>) and plan to<br>
create some common functionality in Python/setcloexec.c and<br>
Include/setcloexec.h that is conditionally compiled in on POSIX<br>
systems and not on Windows systems. I need to extract this<br>
functionality out from _Py_set_inheritable because it needs to run in<br>
the dangerous context of right after a fork and I don't believe it can<br>
throw exceptions. How can I conditionally compile some library code<br>
for certain platforms only?<br></blockquote><div><br></div><div>Do you mean other than potentially detecting something in the configure script and using an #ifdef guard? </div>
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4