[issue7903] Configure script incorrect for reasonably recent OpenBSD

Martin v. Löwis added the comment: Thanks for the tests, and the patch. Committed as r78202, r78203, r78204, and r78205. -- resolution: -> fixed status: open -> closed ___ Python tracker _

[issue7903] Configure script incorrect for reasonably recent OpenBSD

Stefan Krah added the comment: On OpenBSD the ncurses.h header has been broken for quite some time, see e.g. http://bugs.python.org/issue1244610. The problem is that when _XOPEN_SOURCE_EXTENDED is defined, wchar_t is defined twice. I can confirm that it is still broken on 4.6, but it appears tha

[issue7903] Configure script incorrect for reasonably recent OpenBSD

Martin v. Löwis added the comment: Stefan, what ncurses problem are you referring to? I quite object to working around OpenBSD limitations, and would rather hope that OpenBSD fixes their POSIX support at some point. -- ___ Python tracker

[issue7903] Configure script incorrect for reasonably recent OpenBSD

Stefan Krah added the comment: In my testing of issue 3920 I missed that the original approach also fixed the ncurses.h problem, so it should be preferred over bsd3.diff. I attach a patch that reverts the recent commit and extends the xopen_source=no up to version 4.9. I've tested it on 4.4 and

[issue7903] Configure script incorrect for reasonably recent OpenBSD

Martin v. Löwis added the comment: This issue is now superseded by issue 3920. It would be good if somebody could confirm that the approach taken for 4.4 continues to work in more recent releases. -- nosy: +loewis ___ Python tracker

[issue7903] Configure script incorrect for reasonably recent OpenBSD

johns added the comment: Perhaps 1.x was never considered. OpenBSD 2.0 was released in 1996. The OS developers only support the current release version and one "minor" release back anyway. The major release number isn't significant. It's just incremented after the "minor" release is bumpe

[issue7903] Configure script incorrect for reasonably recent OpenBSD

Skip Montanaro added the comment: >> Yeah or better yet take out the versioning entirely. Perhaps. Is 1.x treated differently than 2, 3 or 4? S -- ___ Python tracker ___ _

[issue7903] Configure script incorrect for reasonably recent OpenBSD

johns added the comment: Yeah or better yet take out the versioning entirely. -- ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue7903] Configure script incorrect for reasonably recent OpenBSD

Skip Montanaro added the comment: John> Current OpenBSD is at 4.7 with a new release every six months. John> diff below: ... John> - OpenBSD/2.* | OpenBSD/3.[0123456789] | OpenBSD/4.[0123]) John> + OpenBSD/2.* | OpenBSD/3.* | OpenBSD/4.[01234567]) Wouldn't it be better to just

[issue7903] Configure script incorrect for reasonably recent OpenBSD

Stefan Krah added the comment: Thanks for reporting. This looks like a duplicate of issue3920. -- nosy: +skrah ___ Python tracker ___

[issue7903] Configure script incorrect for reasonably recent OpenBSD

New submission from johns : Current OpenBSD is at 4.7 with a new release every six months. diff below: --- configure Mon Jun 8 17:22:57 2009 +++ configure.new Wed Feb 10 16:00:34 2010 @@ -2086,7 +2086,7 @@ # On OpenBSD, select(2) is not available if _XOPEN_SOURCE is defined, # even thoug