Re: [patch] configure.ac, configure: curses/termcap on *-*-osf5.*

[Daniel Jacobowitz <drow@false.org>]

On Tue, Apr 27, 2004 at 09:50:27PM -0400, Michael Chastain wrote:
> Mark Kettenis writes:
> > Sorry, but this isn't right.  Just because ncurses doesn't work on one
> > particular system, we shouldn't treat all those systems specially.
> > Why is ncurses not working on this particular system?
> 
> You're implying that building gdb with ncurses works on *any*
> alphaev68-dec-osf5.1 system.  I doubt that it does.
> 
> There's no build reports in gdb-testers from anybody with an osf5 system
> since 2002.  And based on the build failure in gdb/1626, I don't think
> that anybody's actually tried to build on an osf5 system since the
> addition of the curses library.  (gdb 6.0 builds fine on this system.
> But gdb 6.0 does not use curses; only termcap).
> 
> Here's what I get when I build gdb 6.1 with ncurses, but using the right
> library order.  The link line is (after touching up the white-space):
> 
>   gcc -g -O2 \
>     -o gdb gdb.o libgdb.a \
>      ../bfd/libbfd.a ../readline/libreadline.a ../opcodes/libopcodes.a ./../intl/libintl.a ../libiberty/libiberty.a -lncurses -ltermcap -lm ../libiberty/libiberty.a
> 
> The unresolved externals are:
> 
>   keypad
>   cbreak
>   _setecho
>   nodelay
>   _setnonl
>   LINES
>   COLS
>   def_prog_mode
>   def_shell_mode
>   stdscr
>   _acs_map
>   curscr
>   getcury
>   getcurx
>   _ring
>   savetty
>   resetty
>   napms
>   collect2: ld returned 1 exit status

That's a mighty deficient ncurses implementation.  Are they in the
ncurses on your system and not being pulled in?  If they aren't there,
what IS?

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer