Philip A. Prindeville wrote:
> I'm seeing a conflict between the auto/osdef.h definitions:
>
> extern int tgetent __ARGS((char *, char *));
> extern int tgetnum __ARGS((char *));
> extern int tgetflag __ARGS((char *));
> extern char *tgoto __ARGS((char *, int, int));
> extern int tputs __ARGS((char *, int, int (*)(int)));
>
> and:
>
> #if !defined(NCURSES_TERM_H_incl)
> extern NCURSES_EXPORT(char *) tgetstr (NCURSES_CONST char *, char **);
> extern NCURSES_EXPORT(char *) tgoto (const char *, int, int);
> extern NCURSES_EXPORT(int) tgetent (char *, const char *);
> extern NCURSES_EXPORT(int) tgetflag (NCURSES_CONST char *);
> extern NCURSES_EXPORT(int) tgetnum (NCURSES_CONST char *);
> extern NCURSES_EXPORT(int) tputs (const char *, int, int (*)(int));
> #endif
>
> in ncurses-5.5:
>
> In file included from term.c:34:
> /home/philipp/alix/build_i586/staging_dir/usr/include/termcap.h:64: error:
> conflicting types for 'tgoto'
> auto/osdef.h:120: error: previous declaration of 'tgoto' was here
> /home/philipp/alix/build_i586/staging_dir/usr/include/termcap.h:65: error:
> conflicting types for 'tgetent'
> auto/osdef.h:117: error: previous declaration of 'tgetent' was here
> /home/philipp/alix/build_i586/staging_dir/usr/include/termcap.h:66: error:
> conflicting types for 'tgetflag'
> auto/osdef.h:119: error: previous declaration of 'tgetflag' was here
> /home/philipp/alix/build_i586/staging_dir/usr/include/termcap.h:67: error:
> conflicting types for 'tgetnum'
> auto/osdef.h:118: error: previous declaration of 'tgetnum' was here
> /home/philipp/alix/build_i586/staging_dir/usr/include/termcap.h:68: error:
> conflicting types for 'tputs'
> auto/osdef.h:121: error: previous declaration of 'tputs' was here
>
>
> I looked at osdef?.h.in and osdef.sh and couldn't figure out where tgoto()
> etc. were coming from.
>
> Is there a work-around?
The configure script generates osdef.h to define missing function
prototypes. Apparently it didn't see the definition in the header file
that was found during compilation. Perhaps the compiler has a different
include file search path than what was used in configure?
The error message contains "staging_dir", you may have to tell the
configure script about it, it usually looks in /usr/include.
--
hundred-and-one symptoms of being an internet addict:
125. You begin to wonder how often it REALLY is necessary to get up
and shower or bathe.
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ download, build and distribute -- http://www.A-A-P.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
