[issue27398] configure warning for Python 3.5.2 during compilation

2016-09-06 Thread Nick Coghlan
Nick Coghlan added the comment: Presumably this also affects Python 3.6, as that includes the same headers during configure for the same reasons: to check if the getrandom() syscall is likely to be available. #27990 is somewhat related, in that Linux makes this a bit difficult to do

[issue27398] configure warning for Python 3.5.2 during compilation

2016-06-27 Thread Martin Panter
Martin Panter added the comment: FWIW adding a blank fourth argument in configure.ac silences this warning (and speeds up the configure run by 7%, or 4 s). But I don’t want to become an Autoconf nerd and I don’t know if this change could have negative consequences on other platforms (e.g.

[issue27398] configure warning for Python 3.5.2 during compilation

2016-06-27 Thread David
David added the comment: Forgot to mention - this is for Debian 4. A really old legacy system we're running, but where we like to use new versions of Python. -- ___ Python tracker

[issue27398] configure warning for Python 3.5.2 during compilation

2016-06-27 Thread David
New submission from David: Hi there. 3.5.1 final didn't have this problem, 3.5.2 final does have this problem. I'm compiling Python 3.5.2 under Debian, and get this warning during the ./configure step: --- configure: WARNING: linux/random.h: present but cannot be compiled