This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author neologix
Recipients alexey-smirnov, amaury.forgeotdarc, georg.brandl, neologix, petri.lehtinen, pitrou, python-dev, socketpair, vstinner
Date 2011-05-22.20:37:10
SpamBayes Score 2.1516546e-05
Marked as misclassified No
Message-id <1306096630.88.0.538255784754.issue12105@psf.upfronthosting.co.za>
In-reply-to
Content
> And apparently some buildbot doesn't like it

Linux-2.6.22-vs2.2.0.7-gentoo-i686-Intel-R-_Xeon-TM-_CPU_2.80GHz-with-gentoo-2.0.1 little-endian

O_CLOEXEC support was added to Linux 2.6.23: this means that the libc defines it while the kernel doesn't support it (it's probably defined as 0).
I could either add some voodoo configure checks to ensure that O_CLOEXEC is indeed supported, or just skip the test on Linux kernels older than 2.6.23. I prefer the later option, it's much simpler and less error-prone. Sure, it will make O_CLOEXEC available while the kernel doesn't support it on some configurations, but since it's a libc issue...
History
Date User Action Args
2011-05-22 20:37:10neologixsetrecipients: + neologix, georg.brandl, amaury.forgeotdarc, pitrou, vstinner, socketpair, python-dev, petri.lehtinen, alexey-smirnov
2011-05-22 20:37:10neologixsetmessageid: <1306096630.88.0.538255784754.issue12105@psf.upfronthosting.co.za>
2011-05-22 20:37:10neologixlinkissue12105 messages
2011-05-22 20:37:10neologixcreate