Okay, it does all seem to be related to ncurses.  I installed a
limited amount into my home directory, and mutt built fine.  Mutt
can't recognize any terminal types when starting, but I only installed
the libraries for testing.  Doing a locate on 'ncurses', I found:

/usr/local/include/ncurses.h
/usr/local/lib/libncurses++.a
/usr/local/lib/libncurses.a
/usr/local/lib/libncurses_g.a
/usr/local/man/cat3/ncurses.3x
/usr/local/man/man3/ncurses.3x


Looking into ncurses.h, I see:

/* $Id: curses.h.in,v 1.96 2000/09/16 16:11:01 tom Exp $ */


Looks like that is 5.2, yes?  5.0 on another system says:

/* $Id: curses.h.in,v 1.85 1999/10/23 12:33:54 tom Exp $ */

Sorry if I'm totally off on that.  But anyway, using
'--with-curses=/usr/local' with configure, configure craps out, ending
with:

checking for waddnwstr in -lncurses... no
checking for waddnwstr in -lncursesw... no
checking for initscr in -lncurses... no
checking for initscr... no
checking for tgoto... no
checking for tgoto in -ltermcap... yes
checking for initscr in -lcursesX... no
checking for initscr in -lcurses... no
checking for initscr in -lncurses... (cached) no
checking for initscr in -lxcurses... no
checking for initscr in -ljcurses... no
checking for initscr in -lunknown... no
configure: error: no curses library found


Am I missing something here, or should configure have found ncurses in
/usr/local/lib and/or include? 


Thanks again for the help.


-Ken

Reply via email to