Re: NetBSD build problems - -lcposix?
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
Re: NetBSD build problems - -lcposix?
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 -lcposix: No such file or directory that's normal (the script is checking if strerror() is in the cposix library, which doesn't happen for many platforms - a special case so it can add -lcposix to the library list if needed). -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: NetBSD build problems - -lcposix?
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 conftest.c -lcposix 15 /usr/bin/ld: cannot open -lcposix: No such file or directory that's normal (the script is checking if strerror() is in the cposix library, which doesn't happen for many platforms - a special case so it can add -lcposix to the library list if needed). 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' collect2: ld returned 1 exit status *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop.
Re: NetBSD build problems - -lcposix?
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) library. Huh. Would that cause make to error out? I now get this. I think the difference was using 'gcc3'. I get undefined reference all over the place, btw. /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 status gmake[2]: *** [mutt] Error 1 gmake[2]: Leaving directory `/tmp/hazmat/mutt-1.3.27' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/tmp/hazmat/mutt-1.3.27' gmake: *** [all-recursive-am] Error 2 -Ken
Re: NetBSD build problems - -lcposix?
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 status gmake[2]: *** [mutt] Error 1 gmake[2]: Leaving directory `/tmp/hazmat/mutt-1.3.27' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/tmp/hazmat/mutt-1.3.27' gmake: *** [all-recursive-am] Error 2 You are not supplying sufficient information for this list to tell you what is wrong. All the above messages mean is that function beep() could not be found. It doesn't tell us WHY it could not be found. Perhaps it is not found because you are linking to a deficient curses library. Perhaps your ncurses is not up to date. Perhaps the correct location of ncurses has not been determined. These are things that are very difficult to tell from so far away out on the net, as we are. Perhaps you could post the entire output from make, or maybe even the output from configure if you so desire. -- David DeSimone | The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid. -- Gilbert K. Chesterson Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: NetBSD build problems - -lcposix?
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 reference to `beep' beep() is a function in the curses (or ncurses) library. Huh. Would that cause make to error out? I now get this. I think the difference was using 'gcc3'. I get undefined reference all over the place, btw. yes - I don't see the whole log of course, but the warnings you're seeing are due to the link either missing the curses library altogether or having the wrong library. The NetBSD curses library for instance is an incomplete subset of X/Open curses (especially compared to ncurses ;-) 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). /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 status gmake[2]: *** [mutt] Error 1 gmake[2]: Leaving directory `/tmp/hazmat/mutt-1.3.27' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/tmp/hazmat/mutt-1.3.27' gmake: *** [all-recursive-am] Error 2 -Ken -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: NetBSD build problems - -lcposix?
* 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). -- timothy lupfer http://sadlittleboy.com
Re: NetBSD build problems - -lcposix?
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
Re: NetBSD build problems - -lcposix?
* 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 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. :-/ I haven't been following this thread very closely, so you will have to pardon my ignorance. What type of problems are you having? compilation or running? is /usr/pkg/lib included in /etc/ld.so.conf? ./configure --with-curses=/usr/pkg might be of some benefit if you are having compilation problems. slang is also an option if ncurses won't fly. -- timothy lupfer http://sadlittleboy.com
