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 vstinner
Recipients Arfrever, eric.araujo, lemburg, loewis, vstinner
Date 2011-08-22.12:57:52
SpamBayes Score 1.43735e-08
Marked as misclassified No
Message-id <>
> The whole purpose of autoconf/configure is
> to try to figure out which features are available on a platform
> and those features change with the OS version.

Hum, not exactly. autoconf checks if a function exists or if a constant exists in the C headers and in the C library. You have to check it or your program (C file) will not compile (missing function/constant).

But it's not enough. The GNU libc provides functions which are only available on some recent Linux kernels. Depending on the running kernel, the function may fail with something like "not implemented error".

See for example the discussion about accept4():

At Python level, you need to know the running kernel version to check if accept4() if available or not. Knowing if the kernel used to compile Python has accept4() or not doesn't help.

(If you use the compiled Python on an older libc (e.g. on another computer), you have another problem, but it's the problem of OS vendors, not of Python.)
Date User Action Args
2011-08-22 12:57:53vstinnersetrecipients: + vstinner, lemburg, loewis, eric.araujo, Arfrever
2011-08-22 12:57:53vstinnersetmessageid: <>
2011-08-22 12:57:53vstinnerlinkissue12794 messages
2011-08-22 12:57:52vstinnercreate