Message136609
| Author |
pitrou |
| Recipients |
alexey-smirnov, amaury.forgeotdarc, georg.brandl, neologix, petri.lehtinen, pitrou, python-dev, socketpair, vstinner |
| Date |
2011年05月23日.11:00:54 |
| SpamBayes Score |
0.0067517306 |
| Marked as misclassified |
No |
| Message-id |
<1306148451.3539.0.camel@localhost.localdomain> |
| In-reply-to |
<1306148147.49.0.474809278195.issue12105@psf.upfronthosting.co.za> |
| Content |
> I like this solution, but I don't know how to test that the kernel
> doesn't support O_CLOEXEC. My commit bff9265d677d will tell use the
> value of O_CLOEXEC on the
> "Linux-2.6.22-vs2.2.0.7-gentoo-i686-Intel-R-_Xeon-TM-_CPU_2.80GHz-with-gentoo-2.0.1 little-endian" buildbot.
If O_CLOEXEC is a #defined constant in the glibc, it can't be different
from other kernels. |
|