New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
curses configure checks fail if only /usr/include/ncursesw/curses.h is installed #59473
Comments
the curses configure checks fail if only /usr/include/ncursesw/curses.h is installed (on a Debian/Ubuntu system, uninstall the libncurses5-dev package, and install the libncursesw5-dev package). The attached patch adds -I/usr/include/ncursesw to CPPFLAGS for the tests. I assume that most buildbot systems still have an /usr/include/curses.h installed, so the tests do the intended thing, because the features tested are the same in ncurses and ncursesw, but basically the wrong headers are used for these tests if both /usr/include/curses.h and /usr/include/ncursesw/curses.h are installed. |
New changeset 707761d59a4a by doko in branch 'default':
|
can be closed if we don't bother to use the "wrong" header for the checks |
and only add the dir for the curses.h and nurses.h header checks |
and a variant, which moves all curses header related check together (curses3.diff) |
I have a similar issue on Solaris and a patch[1] to fix it attached to bpo-3786. |
Matthias, do not use hack if cross-build |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: