This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author hm
Recipients hm, skrah, v.claudic
Date 2012-05-23.12:07:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1337774879.94.0.352519728312.issue12271@psf.upfronthosting.co.za>
In-reply-to
Content
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
History
Date User Action Args
2012-05-23 12:08:00hmsetrecipients: + hm, skrah, v.claudic
2012-05-23 12:07:59hmsetmessageid: <1337774879.94.0.352519728312.issue12271@psf.upfronthosting.co.za>
2012-05-23 12:07:58hmlinkissue12271 messages
2012-05-23 12:07:58hmcreate