On Fri, Apr 10, 2026 at 09:32:56PM +0200, Clemens Lang wrote: > > On 3. Apr 2026, at 12:24, Dennis Preiser <[email protected]> wrote: > > > > On Fri, Apr 03, 2026 at 06:11:38PM +0800, Kevin J. McCarthy wrote: > >> The only question is... why didn't your installation of ncursesw at least > >> create stubs for ncurses too? Most ncursesw installs will create > >> ncurses.so > >> symlinks or files containing something like "INPUT(-lncursesw)" to point to > >> the ncursesw so files. > > > > I'm trying to figure that out. > > configure ncurses with --disable-lib-suffixes.
For me, mutt is the only program that has trouble finding/using the library specified with '--with-curses=DIR'. I don't think it's due to ncurses' configure arguments, but rather to the way mutt's configure searches for and locates the curses libraries. > For example, MacPorts uses these flags: > https://github.com/macports/macports-ports/blob/master/devel/ncurses/Portfile#L34-L45 I don't use MacPorts, but after a quick look, it seems to be implemented somewhat inconsistently. From the Portfiles: mutt has | depends_lib | port:ncurses and | configure.args | --with-curses=${prefix} in contrast vifm has | depends_lib | port:ncurses but no | configure.args | --with-curses=${prefix} tin has | depends_lib | port:ncurses and | configure.args | --with-screen=ncursesw but no | configure.args | --with-curses-dir=DIR And yes, vifm´s configure supports --with-curses=DIR, and tin´s supports --with-screen=(termcap|terminfo|curses|ncurses|ncursesw|pdcurses) and --with-curses-dir=DIR. Dennis
