➜

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 Arfrever, christian.heimes, giampaolo.rodola, neologix, pitrou, python-dev, vajrasky, vstinner
Date 2013-10-25.13:13:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM1YKHua69ViCnxBOBxxdOHp584WgWcsVVxiHe3O=Za5-A@mail.gmail.com>
In-reply-to <1382682803.51.0.185640652496.issue16595@psf.upfronthosting.co.za>
Content 
> I didn't expect to see a combination of glibc with prlimit() and Kernel without prlimit(). According to man prlimit it's not suppose to fail with ENOSYS, too.

Yeah, we've seen this several times on some buildbots.
Note that actually, any syscall can fail with ENOSYS: the configure
check just checks that the libc exposes the wrapper library, but when
the libc wrapper makes the actual syscall, the kernel can return
-ENOSYS if it doesn't implement the syscall.
History
Date User Action Args
2013-10-25 13:13:36neologixsetrecipients: + neologix, pitrou, vstinner, giampaolo.rodola, christian.heimes, Arfrever, python-dev, vajrasky
2013-10-25 13:13:36neologixlinkissue16595 messages
2013-10-25 13:13:35neologixcreate