Hi Erik,
I just tried './configure' on my Debian, no error showed up.
Have you tried:
$ sudo apt-get build-dep mutt
I'm running Debian 8 (jessie), on my system I have these .debs:
$ dpkg -l | grep ncurse
ii abook 0.6.0~pre2-3
amd64 text-based ncurses address book application
ii libncurses5:amd64 5.9+20140913-1+b1
amd64 shared libraries for terminal handling
ii libncurses5-dev:amd64 5.9+20140913-1+b1
amd64 developer's libraries for ncurses
ii libncursesw5:amd64 5.9+20140913-1+b1
amd64 shared libraries for terminal handling (wide character support)
ii libncursesw5-dev:amd64 5.9+20140913-1+b1
amd64 developer's libraries for ncursesw
ii ncurses-base 5.9+20140913-1
all basic terminal type definitions
ii ncurses-bin 5.9+20140913-1+b1
amd64 terminal-related programs and man pages
ii ncurses-term 5.9+20140913-1
all additional terminal type definitions
Thanks,
- Tim
On 2017-02-27 19:28+1100, Erik Christiansen wrote:
> On 24.02.17 13:28, on mutt-announce, Kevin J. McCarthy wrote:
> > I am pleased to announce version 1.8.0 has just been released. It is
> > available at ftp.mutt.org/pub/mutt/mutt-1.8.0.tar.gz via ftp and http.
>
> Many thanks to all for the much valued development effort.
>
> Unfortunately, installation of 1.8.0 is stalled here by apparent
> incompatibility between Mutt and the Debian installation I have:
>
> $ more /etc/issue
> Debian GNU/Linux 7 \n \l
>
> $ ./configure
> ...
> checking for waddnwstr in -lncurses... no
> checking for waddnwstr in -lncursesw... no
> checking for initscr in -lncurses... no
> checking for initscr... (cached) 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
> #######################
>
> (Repeated as root, just in case, but same result.)
>
> Maybe we should get some, then?:
>
> $ apt-cache search libncurses
> ...
> libncurses5 - shared libraries for terminal handling
> ...
> libncursesw5 - shared libraries for terminal handling (wide character
> support)
>
> and:
>
> # apt-get install libncurses5
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> libncurses5 is already the newest version.
>
> That's one ncurses library available, and there's also:
>
> $ apt-cache search ncurses
> ...
> ncurses-base - basic terminal type definitions
>
> which is also present and current:
>
> $ dpkg -l ncurses-base
> Desired=Unknown/Install/Remove/Purge/Hold
> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Name Version Architecture Description
> +++-=============-===========-==============-=========================
> ii ncurses-base 5.9-10 all basic terminal
> type definitions
>
> OK, what does the old one use?
>
> $ ldd /usr/bin/mutt | grep ncurses
> libncursesw.so.5 => /lib/i386-linux-gnu/libncursesw.so.5 (0xb76c2000)
>
> Ha, let's get that, then:
>
> # apt-get install libncursesw5
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> libncursesw5 is already the newest version.
>
> Now I am beginning to run out of ideas. There's something less than
> blindingly obvious afoot here ... or I need a higher caffeine to
> haemoglobin ratio.
>
> Erik
