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 doko
Recipients barry, bukzor, coconutrb, doko, jnoller, mark.dickinson, r.david.murray, sandro.tosi, skrah
Date 2011-04-26.21:45:52
SpamBayes Score 1.19281e-11
Marked as misclassified No
Message-id <1303854353.75.0.75952821771.issue8326@psf.upfronthosting.co.za>
In-reply-to
Content
> Barry A. Warsaw<barry@python.org>  added the comment:
> 
> I'm closing this as invalid for Python, since I believe this is strictly an
> Ubuntu bug caused by an out-of-date kernel on the build farm.

that's where I disagree. a configure check should not be dependent on the running kernel.  I assume in the majority of cases you won't build against a current kernel, so the a fix in python maybe could be a runtime check.  Such configure checks will fail for cross builds too.

Note that packages on Ubuntu are always built on the current kernel of the current LTS release, on Debian on current kernels of the current stable release.  So there is nothing "out-of-date".
History
Date User Action Args
2011-04-26 21:45:53dokosetrecipients: + doko, barry, mark.dickinson, jnoller, r.david.murray, skrah, sandro.tosi, coconutrb, bukzor
2011-04-26 21:45:53dokosetmessageid: <1303854353.75.0.75952821771.issue8326@psf.upfronthosting.co.za>
2011-04-26 21:45:52dokolinkissue8326 messages
2011-04-26 21:45:52dokocreate