checking whether PTHREAD_MUTEX_INITIALIZER is declared... yes checking for initscr in -lncursesw... no configure: error: libncursesw not found !!! Please attach the following file when seeking support: !!! /var/tmp/portage/app-misc/vifm-0.9.1/work/vifm-0.9.1/config.log ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-systemd_abi32+64-test_20180203-182621 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.0 * Available Python interpreters, in order of preference: [1] python3.5 [2] python2.7 (fallback) java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.6.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpv app-misc/vifm [ebuild N ] app-misc/vifm-0.9.1_beta USE="extended-keys magic -X -developer -gtk -vim -vim-syntax"
Created attachment 518094 [details] emerge-info.txt
Created attachment 518096 [details] app-misc:vifm-0.9.1:20180206-015356.log
Created attachment 518098 [details] emerge-history.txt
Created attachment 518100 [details] environment
Created attachment 518102 [details] etc.portage.tbz2
Created attachment 518104 [details] logs.tbz2
Created attachment 518106 [details] temp.tbz2
No clue what's happening. By looking at your emerge-history.txt libncursesw seems installed but the linker can't find it: configure:8668: x86_64-pc-linux-gnu-gcc -o conftest -O2 -pipe -march=native -fsigned-char -Wall -pthread -Wl,-O1 -Wl,--as-needed conftest.c -lncursesw -lm >&5 ... /usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find -lncursesw I've successfully built =app-misc/vifm-0.9.1 in several machines using your configuration with both =sys-libs/ncurses-6.0-r2 and =sylibs/ncurses-6.1-r1
May or may not be relevant: for me vifm-0.9.0 and -0.9.1 are compiled successfully, but both segfault. gdb shows that: > (gdb) run > Starting program: /usr/bin/vifm > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib64/libthread_db.so.1". > [New Thread 0x7ffff65ed700 (LWP 2018)] > Thread 1 "vifm" received signal SIGSEGV, Segmentation fault. > 0x00007ffff767dcad in termattrs_sp () from /lib64/libncursesw.so.6 Shall it be this bug or I better open another one?
Created attachment 525462 [details] emerge --info app-misc/vifm
(In reply to Viacheslav Ostroukh from comment #9) > May or may not be relevant: for me vifm-0.9.0 and -0.9.1 are compiled > successfully, but both segfault. gdb shows that: > > > (gdb) run > > Starting program: /usr/bin/vifm > > [Thread debugging using libthread_db enabled] > > Using host libthread_db library "/lib64/libthread_db.so.1". > > [New Thread 0x7ffff65ed700 (LWP 2018)] > > > Thread 1 "vifm" received signal SIGSEGV, Segmentation fault. > > 0x00007ffff767dcad in termattrs_sp () from /lib64/libncursesw.so.6 > > Shall it be this bug or I better open another one? Sorry, forgot to mention: problem appeared after update of ncurses to sys-libs/ncurses-6.1-r1.
(In reply to Viacheslav Ostroukh from comment #11) > Sorry, forgot to mention: problem appeared after update of ncurses to > sys-libs/ncurses-6.1-r1. I can't reproduce the segfault here with vifm-0.9.1 and ncurses-6.1-r1. Please, fill in a separate bug and include as much information as posible (backtrace, core dump, ...) so we can report it upstream. Thanks.
Fixed, see bug #651914
