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
broken ncurses support in current cvs and last distribution #38587
Comments
I found configure looks for ncurses.h instead of Even after fixing configure and cc: Error: /software/@sys/usr/include/ncurses/curses.h, Any ideas? |
Logged In: YES Can you report how NCURSES_EXPORT is defined on your system? |
Logged In: YES Sorry, I'm not aprogrammer, should I attach some of the |
Logged In: YES I asked the developer of ncurses. This is his first reply. From: Thomas Dickey <dickey@herndon4.his.com> My guess (because I've seen it a few times)
(It's "fixing" a place which is providing a typedef if it If it's not that - perhaps more info. (Perhaps just setting |
Logged In: YES I see. This seems to be either a bug in ncurses, or in gcc. |
Logged In: YES Second reply(I have to add I'll retry once more, but I
no - gcc is the one that "fixes" headers. It is unlikely Then it sounds like a variation of the other sort of What I'd look for: since most applications do not distinguish
#include <ncurses/curses.h>
and
#include <curses.h>
by ifdef's is that your options have only
-I/software/@sys/usr/include/ncurses
rather than
-I/software/@sys/usr/include
-I/software/@sys/usr/include/ncurses
Since the ncurses headers (unctrl.h, term.h) will have a
line like
#include <ncurses/curses.h>
it really needs both -I options. (Specifying both still
does not work around
the gcc fixincludes problem - that's why I remember that one
first).
> > (It's "fixing" a place which is providing a typedef if
it doesn't exist).
> > I modified the ifdef's to avoid this problem. The quick
fix is to remove
> > curses.h from gcc's fixed-includes. The reason why
NCURSES_EXPORT is not
> > defined is because gcc finds the wrong curses.h and
doesn't find ncurses_dll.h
> > because its fixed-include forces it into the wrong
search path.
> >
> > If it's not that - perhaps more info. (Perhaps just
setting $CPPFLAGS in
> > the environment is needed).
>
> But the message
>
> cc: Error: /software/@sys/usr/include/ncurses/curses.h,
> line 506: Missing identifier. (parnoident)
> extern NCURSES_EXPORT(int) addch (const chtype);
> /* generated */
> ---------------------------^
> cc: Error: /software/@sys/usr/include/ncurses/curses.h,
> line 507: Missing identifier. (parnoident)
> extern NCURSES_EXPORT(int) addchnstr (const chtype *,
> int); /* generated */
> ---------------------------^
> cc: Error: /software/@sys/usr/include/ncurses/curses.h,
> line 508: Missing identifier. (parnoident)
> extern NCURSES_EXPORT(int) addchstr (const chtype *);
> /* generated */
> ---------------------------^
>
> confirms that CPPFLAGS or CFLAGS point to the location
where ncurses are
> installed! Maybe the problem is that ncurses/ncurses.h are
stored as
> ncurses/curses.h?
> |
Logged In: YES Hi, I believe the configure should test for both: <ncurses.h> ncurses-5.3 and newer install into $prefix/include/ncurses/ This change should be reflected by the configure script. I believe the dist/src/Modules/_curses_panel.c calling |
Logged In: YES Well, that is not the problem you have originally reported? I If so, please close this report, and submit a new one indicating
|
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: