x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -DSYSCONFDIR='"/etc"' -I./fmtlib -Wall -D_ISOC99_SOURCE -D__STDC_LIMIT_MACROS -D_GNU_SOURCE -O2 -pipe -march=native -fno-diagnostics-color -c -o listview_curses.o listview_curses.cc listview_curses.cc: In member function ‘virtual void listview_curses::do_update()’: listview_curses.cc:289:13: error: ‘mvwin_wchnstr’ was not declared in this scope; did you mean ‘mvwinchnstr’? 289 | mvwin_wchnstr(this->lv_window, y, this->lv_x, row_ch, width - 1); | ^~~~~~~~~~~~~ | mvwinchnstr ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_no-multilib-20210315-144814 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-10.2.0 * clang version 11.1.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/11/bin /usr/lib/llvm/11 11.1.0 Python 3.8.8 Available Ruby profiles: [1] ruby26 (with Rubygems) [2] ruby27 (with Rubygems) * Available Rust versions: [1] rust-bin-1.50.0 [2] rust-1.50.0 * The following VMs are available for generation-2: *) AdoptOpenJDK 8.282_p08 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 system-vm The Glorious Glasgow Haskell Compilation System, version 8.10.4 timestamp(s) of HEAD at this tinderbox image: /var/db/repos/gentoo Wed Mar 24 11:50:41 UTC 2021 emerge -qpvO app-admin/lnav [ebuild N ] app-admin/lnav-0.9.0 USE="-unicode"
Created attachment 693321 [details] emerge-info.txt
Created attachment 693324 [details] app-admin:lnav-0.9.0:20210324-121055.log
Created attachment 693327 [details] emerge-history.txt
Created attachment 693330 [details] environment
Created attachment 693333 [details] etc.portage.tar.bz2
Created attachment 693336 [details] logs.tar.bz2
Created attachment 693339 [details] temp.tar.bz2
Hello Toralf, and thanks for the bug report! I am also able to reproduce this issue when I have USE="-unicode". However, it does work with USE="unicode", if that is a suitable workaround for you. I have filed this upstream: https://github.com/tstack/lnav/issues/865
*** Bug 828089 has been marked as a duplicate of this bug. ***
Is it reasonable to simply remove the unicode USE variable from the package, since it doesn't work anyway?
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f75f598ccad65de223b8962d0947be1a2b9da0e8 commit f75f598ccad65de223b8962d0947be1a2b9da0e8 Author: Randy Barlow <randy@electronsweatshop.com> AuthorDate: 2022-09-03 22:49:40 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-09-09 03:45:58 +0000 app-admin/lnav: Add 0.11.0 * Remove the unicode USE flag lnav did not build successfully when this USE flag was disabled. Since there are not many use cases for not using unicode today, this commit fixes the issue by removing the USE flag and enabling unicode support unconditionally. * Depend on openssh[ssl] See https://github.com/tstack/lnav/issues/865. * Conditionally build ssh keys This commit patches lnav so that it only build ssh keys when tests are run. This makes openssh a conditional dependency. See https://github.com/tstack/lnav/pull/1041. * Filter LTO flags Closes: https://github.com/gentoo/gentoo/pull/27130 Closes: https://bugs.gentoo.org/777981 Closes: https://bugs.gentoo.org/835636 Closes: https://bugs.gentoo.org/854123 Signed-off-by: Randy Barlow <randy@electronsweatshop.com> Signed-off-by: Sam James <sam@gentoo.org> app-admin/lnav/Manifest | 1 + .../files/lnav-0.11.0-conditional-ssh-keygen.patch | 34 +++++++++++ .../lnav/files/lnav-0.11.0-disable-tests.patch | 67 ++++++++++++++++++++++ app-admin/lnav/lnav-0.11.0.ebuild | 56 ++++++++++++++++++ app-admin/lnav/metadata.xml | 3 + 5 files changed, 161 insertions(+)
