[issue31909] Missing definition of HAVE_SYSCALL_GETRANDOM

2017-10-31 Thread Ilya Kulakov
Ilya Kulakov added the comment: Not a bug in Python. -- stage: patch review -> resolved status: open -> closed ___ Python tracker ___ __

[issue31909] Missing definition of HAVE_SYSCALL_GETRANDOM

2017-10-30 Thread Ilya Kulakov
Ilya Kulakov added the comment: nvm my last question. My process is as per README: ./configure && make I'll take a further look at what's wrong. -- ___ Python tracker ___ ___

[issue31909] Missing definition of HAVE_SYSCALL_GETRANDOM

2017-10-30 Thread Ilya Kulakov
Ilya Kulakov added the comment: Just compiling Python 3.6.3 from sources on Ubuntu 16.04 Is there any reason to fall back to XML_POOR_ENTROTPY when proper source is actually available? -- ___ Python tracker ___

[issue31909] Missing definition of HAVE_SYSCALL_GETRANDOM

2017-10-30 Thread Benjamin Peterson
Benjamin Peterson added the comment: This is supposed to be handled by setup.py defining XML_POOR_ENTROTPY. Are you doing something non-standard? -- nosy: +benjamin.peterson ___ Python tracker __

[issue31909] Missing definition of HAVE_SYSCALL_GETRANDOM

2017-10-30 Thread Roundup Robot
Change by Roundup Robot : -- keywords: +patch pull_requests: +4156 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-lis

[issue31909] Missing definition of HAVE_SYSCALL_GETRANDOM

2017-10-30 Thread Ilya Kulakov
New submission from Ilya Kulakov : Python 3.5 and 3.6 in their corresponding configure.ac try to detect presence of sys_getrandom. The result is written into the `HAVE_GETRANDOM_SYSCALL` definition. libexpact checks for `HAVE_SYSCALL_GETRANDOM` and since it's not defined, does not use it. Thi