[New-bugs-announce] [issue20445] HAVE_BROKEN_NICE detected incorrectly due to configure.ac typo
George Kouryachy
report at bugs.python.org
Thu Jan 30 13:57:41 CET 2014
New submission from George Kouryachy:
It's declared in pyconfig.h that HAVE_BROKEN_NICE is set if nice() returns success/failure instead of the new priority.
But configure checks just opposite (as for http://hg.python.org/cpython/file/03fc7449f204/configure.ac#l4234):
if (val1 != -1 && val1 == nice(2))
exit(0);
We need "val1 != nice(2)" instead (to ensure that nicelevel is increased) or "val1 == nice(2)+2" (to check increment is proper; this can be tricky in some cases).
----------
components: Build
messages: 209712
nosy: George.Kouryachy
priority: normal
severity: normal
status: open
title: HAVE_BROKEN_NICE detected incorrectly due to configure.ac typo
type: behavior
versions: Python 2.7
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue20445>
_______________________________________
More information about the New-bugs-announce
mailing list