On Tue, Mar 12, 2002, tim lupfer wrote: > * thus spaketh Thomas Dickey (Mar 12 at 06:46PM): > > > Perhaps the configure script didn't find ncurses (which is a port), or > > was fooled into trying to use the NetBSD curses library (not recommended). > > ...i'm jumping in a bit late on this conversation; but I am using > mutt with netbsd curses with no problems whatsoever (both 1.2.5 and > 1.3.x).
Well with either no path to curses on the command line or using what I found on the system, I get the problems. There is a mutt 1.3.25i installed on the system, and mutt -v says 'System: NetBSD 1.5.2 (i386) [using ncurses 5.2]'. Any way to find out what build parameters were used for it to find ncurses 5.2? Looks like it was installed as a package, actually. But /pkg/mutt-1.3.25 is a sym link to /usr/local. :-/ -Ken
