[issue25171] does not build on OpenBSD with no value defined for PY_GETENTROPY

2015-10-01 Thread STINNER Victor
STINNER Victor added the comment: Thanks Remi for your fix, the compilation succeeded on the buildbot. Sorry for the regression. -- resolution: -> fixed status: open -> closed ___ Python tracker

[issue25171] does not build on OpenBSD with no value defined for PY_GETENTROPY

2015-09-30 Thread Remi Pointel
Remi Pointel added the comment: Attached is the diff to use defined(PY_GETENTROPY) instead of #define PY_GETENTROPY 1. -- Added file: http://bugs.python.org/file40631/Python_random_c ___ Python tracker

[issue25171] does not build on OpenBSD with no value defined for PY_GETENTROPY

2015-09-30 Thread Roundup Robot
Roundup Robot added the comment: New changeset e4ac5a899657 by Victor Stinner in branch 'default': Issue #25171: Fix compilation issue on OpenBSD in random.c https://hg.python.org/cpython/rev/e4ac5a899657 -- nosy: +python-dev ___ Python tracker

[issue25171] does not build on OpenBSD with no value defined for PY_GETENTROPY

2015-09-25 Thread Martin Panter
Martin Panter added the comment: Patch looks sensible to me, although I notice the rest of that module tends to prefer the #elif defined(PY_GETENTROPY) style. It looks like this might be introduced with Issue 25003. -- nosy: +haypo, martin.panter stage: -> patch review type: ->

[issue25171] does not build on OpenBSD with no value defined for PY_GETENTROPY

2015-09-18 Thread Remi Pointel
New submission from Remi Pointel: Hi, I'm trying to build Python on OpenBSD-current, but it does not build because it seems that PY_GETENTROPY does not have a value. $ make ... gcc -pthread -c -fno-strict-aliasing -Wsign-compare -Wunreachable-code -DNDEBUG -g -fwrapv -O3 -Wall