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

2014-02-01 Thread 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 __

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

2014-01-30 Thread Benjamin Peterson
Benjamin Peterson added the comment: Are you sure? The configure test sets ac_cv_broken_nice=1 if "val1 == nice(2)". That is if the call returns the same succesful value each time. -- nosy: +benjamin.peterson ___ Python tracker

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

2014-01-30 Thread 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

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

2014-01-30 Thread 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