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:147: build/release/src/core.lo] Error 2 * ERROR: dev-libs/libmpack-1.0.5::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 04:36:02 UTC 2021 emerge -qpvO dev-libs/libmpack [ebuild N ] dev-libs/libmpack-1.0.5
Created attachment 695358 [details] emerge-info.txt
Created attachment 695361 [details] dev-libs:libmpack-1.0.5:20210328-053514.log
Created attachment 695364 [details] emerge-history.txt
Created attachment 695367 [details] environment
Created attachment 695370 [details] etc.portage.tar.bz2
Created attachment 695373 [details] temp.tar.bz2
From what I understand, this package needs to run 'slibtool-shared'. Looking into the makefile, I can see, that LIBTOOL can be set for that. Since there is no 'configure' run, what's the best practice here to set LIBTOOL?
> Since there is no 'configure' run, what's the best practice here to set LIBTOOL? To my knowledge there hasn't been a consensus on how to solve this in gentoo yet. Personally I use package.env to set the correct slibtool symlink for now, but ideally it would be automatic and determined on use flags if applicable (slibtool-static for static-libs, slibtool-shared otherwise in most cases). There also might be some of these that fail for unrelated issues even when using the correct slibtool symlink.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2990abfcf26b5be52767550acc6695263bf28b85 commit 2990abfcf26b5be52767550acc6695263bf28b85 Author: orbea <orbea@riseup.net> AuthorDate: 2022-06-18 02:07:01 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-06-20 02:03:26 +0000 dev-libs/libmpack: Fix build with rlibtool The build uses libtool, but does not use autoconf meaning the libtool script is never generated and the build falls back to the system version. This is problematic with rlibtool which depends on the generated libtool to determine if it should build shared or static libraries. This patch fixes the issue by creating a minimal configure.ac only for libtool. Bug: https://bugs.gentoo.org/778899 Signed-off-by: orbea <orbea@riseup.net> Closes: https://github.com/gentoo/gentoo/pull/25950 Signed-off-by: Sam James <sam@gentoo.org> .../libmpack/files/libmpack-1.0.5-libtool.patch | 89 ++++++++++++++++++++++ dev-libs/libmpack/libmpack-1.0.5-r3.ebuild | 63 +++++++++++++++ 2 files changed, 152 insertions(+)
