Simon Josefsson <si...@josefsson.org> writes:
> Since the CI/CD file had '|| true' I suppose it means it is a known
> problem for ArchLinux. Does anyone understand why the error above
> happens? ArchLinux shouldn't be that different, and tgetent should come
> via ncurses which is detected fine... anyway, since it is an earlier
> known problem, I wouldn't worry about it since it is not a regression.
> Would be nice to fix though, ArchLinux seems popular.
In telnet/telnet.c, the file the error occurs, we have:
#ifdef HAVE_TERMCAP_TGETENT
# include <termcap.h>
#elif defined HAVE_CURSES_TGETENT
# include <curses.h>
# ifndef _XOPEN_CURSES
# include <term.h>
# endif
#endif
In the logs for that build:
checking for tgetent in -ltermcap... no
checking whether tgetent needs support... no
checking for tgetent in -lcurses... yes
checking whether tgetent is declared... no
I don't have an Arch machine but I'm guessing that the headers there are
correct (unless the maintainers did something funky). A bandaid fix
would be to add an extern decl of 'tgetent'. But I'm thinking the
problem is probably a bad check for the function, curses, etc. in the
configure script.
IIRC Gnulib has some stuff for checking for curses, terminfo.h,
termcap.h, and so on. If so we should probably use that. Since bugs
there are more likely to be found.
Then again I didn't look into this much so I could be completely
wrong. :)
Collin
