[issue20445] HAVE_BROKEN_NICE detected incorrectly due to configure.ac typo

[George Kouryachy]

George Kouryachy added the comment:

Oops, looks like my local build system artifact.

Thank you for your attention, all-clear.

--
resolution:  - invalid
status: open - closed

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20445
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20445] HAVE_BROKEN_NICE detected incorrectly due to configure.ac typo

[George Kouryachy]

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 rep...@bugs.python.org
http://bugs.python.org/issue20445
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20445] HAVE_BROKEN_NICE detected incorrectly due to configure.ac typo

[George Kouryachy]

George Kouryachy added the comment:

It seems to be permanent typo through all branches :(

--
versions: +Python 3.1, Python 3.2, Python 3.3, Python 3.4, Python 3.5

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20445
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com