Holger Mickler <holger.mick...@tu-dresden.de> added the comment: I just stumbled upon the same problem with Python 2.7.3 on SLES 11 SP1 amd64.
Obviously, SuSE puts the needed header file into /usr/include/ncurses/, and one can either create a symlink in /usr/include/ or apply a patch to _curses_panel.c: --- Modules/_curses_panel.c.orig 2012-05-23 13:34:17.000000000 +0200 +++ Modules/_curses_panel.c 2012-05-23 13:34:27.000000000 +0200 @@ -14,7 +14,7 @@ #include "py_curses.h" -#include <panel.h> +#include <ncurses/panel.h> static PyObject *PyCursesError; Maybe some logic could be put into the build process to automatically handle this? Apparently, configure already knows about the different locations... Regards, Holger ---------- nosy: +hm _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue12271> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
