rdlibtool: lconf: fstat(3,...) = 0 {.st_dev = 34, .st_ino = 12424758}. rdlibtool: lconf: stopped in "/var/tmp" (config file not found on current device). rdlibtool: error logged in slbt_lconf_open(), line 597: flow error: unexpected condition or other. rdlibtool: < returned to > slbt_get_lconf_flags(), line 640. make: *** [Makefile:60: src/encoding.lo] Error 2 * ERROR: dev-libs/libvterm-0.1.3::gentoo failed (compile phase): ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_systemd-20210320-151517 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.1 [2] x86_64-pc-linux-gnu-10.2.0 * /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 Sun Mar 28 23:35:34 UTC 2021 emerge -qpvO dev-libs/libvterm [ebuild N ] dev-libs/libvterm-0.1.3
Created attachment 695796 [details] emerge-info.txt
Created attachment 695799 [details] dev-libs:libvterm-0.1.3:20210328-235200.log
Created attachment 695802 [details] emerge-history.txt
Created attachment 695805 [details] environment
Created attachment 695808 [details] etc.portage.tar.bz2
Created attachment 695811 [details] temp.tar.bz2
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ae5676fcc57a48c25b474a14c9e21395e1b663d6 commit ae5676fcc57a48c25b474a14c9e21395e1b663d6 Author: orbea <orbea@riseup.net> AuthorDate: 2022-07-20 15:04:29 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-07-25 04:14:38 +0000 dev-libs/libvterm: Fix the build with rlibtool Bug: https://bugs.gentoo.org/779034 Closes: https://github.com/gentoo/gentoo/pull/26497 Signed-off-by: Sam James <sam@gentoo.org> .../libvterm/files/libvterm-0.1.4-slibtool.patch | 98 ++++++++++++++++++++ .../libvterm/files/libvterm-0.2-slibtool.patch | 103 +++++++++++++++++++++ dev-libs/libvterm/libvterm-0.1.4-r1.ebuild | 37 ++++++++ dev-libs/libvterm/libvterm-0.2-r1.ebuild | 40 ++++++++ 4 files changed, 278 insertions(+)
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=683eaf8be0351ac263c0b73c9806062647feafe4 commit 683eaf8be0351ac263c0b73c9806062647feafe4 Author: orbea <orbea@riseup.net> AuthorDate: 2023-08-30 00:07:16 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2023-08-30 06:41:20 +0000 dev-libs/libvterm: fix rlibtool build (Again) Not sure why the patch was never applied to the 0.3 versions. Bug: https://bugs.gentoo.org/779034 Closes: https://github.com/gentoo/gentoo/pull/32515 Signed-off-by: orbea <orbea@riseup.net> Closes: https://github.com/gentoo/gentoo/pull/32521 Signed-off-by: Sam James <sam@gentoo.org> .../libvterm/files/libvterm-0.3.2-slibtool.patch | 99 ++++++++++++++++++++++ dev-libs/libvterm/libvterm-0.3.2-r1.ebuild | 43 ++++++++++ 2 files changed, 142 insertions(+)
