Hej all, > Am 16.06.2020 um 13:26 schrieb adr%sdf.org@localhost <adr%SDF.ORG@localhost>: > >>>> is this anyhow related to the tmux build failure i am currently observing? >>>> >>>> ?schnipp? >>>> checking event.h usability... yes >>>> checking event.h presence... yes >>>> checking for event.h... yes >>>> checking for LIBTINFO... no >>>> checking for LIBNCURSES... no >>>> checking for LIBNCURSES... no >>>> checking for setupterm in -ltinfo... no >>>> checking for setupterm in -lncurses... no >>>> checking for setupterm in -lcurses... no >>>> checking curses.h usability... yes >>>> checking curses.h presence... yes >>>> checking for curses.h... yes >>>> configure: error: "curses not found" >>>> *** Error code 1 >>>> >>>> Stop. >>>> make[1]: stopped in /hurz/pkgsrc/misc/tmux >>>> *** Error code 1 >>>> >>>> Stop. >>>> make: stopped in /usr/pkgsrc/misc/tmux >>>> ?schnappp? >>>> >>>> this happens with and without ncurses installed (on NetBSD 9.99.66). > Hi, > > I don't use tmux, but it seams it is searching for ncurses|tinfo. > In NetBSD setupterm is in libterminfo. > > You could patch the configure script to test for setupterm in -lterminfo. > since no one came up with a better solution, i must assume i am the only one using tmux 3.1b on NetBSD. so, here is what I did, please check - it should not have any effect on other platforms. I did not figure out how to invoke autoconf in order to patch configure.ac which should be the correct way in order to submit upstream. Cheers Oskar
Attachment:
patch-configure
Description: Binary data
Attachment:
signature.asc
Description: Message signed with OpenPGP