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
On Tue, Mar 12, 2002 at 01:32:01PM -0800, Ken Weingold wrote:
I am trying to build mutt even with no configure options, and get this
in config.log:
configure:1109: checking for strerror in -lcposix
configure:1128: gcc -o conftest -g -O2 conftest.c -lcposix 15
/usr/bin/ld: cannot open
On Tue, Mar 12, 2002, Thomas Dickey wrote:
On Tue, Mar 12, 2002 at 01:32:01PM -0800, Ken Weingold wrote:
I am trying to build mutt even with no configure options, and get this
in config.log:
configure:1109: checking for strerror in -lcposix
configure:1128: gcc -o conftest -g -O2
On Tue, Mar 12, 2002, Thomas Dickey wrote:
Oh, so then maybe it's not related to why make crapped out. Here's
the error:
pgpkey.o: In function `pgp_ask_for_key':
/tmp/hazmat/mutt-1.3.27/pgpkey.c:701: undefined reference to `beep'
beep() is a function in the curses (or ncurses)
Ken Weingold [EMAIL PROTECTED] wrote:
Would that cause make to error out?
/tmp/hazmat/mutt-1.3.27/pgpkey.c:701: undefined reference to `beep'
resize.o: In function `mutt_resize_screen':
/tmp/hazmat/mutt-1.3.27/resize.c:79: undefined reference to
`resizeterm'
collect2: ld returned 1 exit
On Tue, Mar 12, 2002 at 03:10:27PM -0800, Ken Weingold wrote:
On Tue, Mar 12, 2002, Thomas Dickey wrote:
Oh, so then maybe it's not related to why make crapped out. Here's
the error:
pgpkey.o: In function `pgp_ask_for_key':
/tmp/hazmat/mutt-1.3.27/pgpkey.c:701: undefined
* 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
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;
* thus spaketh Ken Weingold (Mar 12 at 04:35PM):
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
