Ebuild installs libtool library files (*.la) files in the wrong path: >>> Completed installing net-firewall/ipset-7.10 into /var/tmp/portage/net-firewall/ipset-7.10/image * Final size of build directory: 9912 KiB (9.6 MiB) * Final size of installed tree: 868 KiB * QA Notice: Excessive files found in the / partition * /var/tmp/portage/net-firewall/ipset-7.10/image/lib64/libipset.a * ERROR: net-firewall/ipset-7.10::gentoo failed: * static archives (*.a) and libtool library files (*.la) belong in /usr/lib*, not /lib* * * Call stack: * misc-functions.sh, line 596: Called install_qa_check * misc-functions.sh, line 132: Called source 'install_symlink_html_docs' * 80libraries, line 178: Called lib_check * 80libraries, line 162: Called die * The specific snippet of code: * die "static archives (*.a) and libtool library files (*.la) belong in /usr/lib*, not /lib*" * * If you need support, post the output of `emerge --info '=net-firewall/ipset-7.10::gentoo'`, * the complete build log and the output of `emerge -pqv '=net-firewall/ipset-7.10::gentoo'`. * The complete build log is located at '/var/log/portage/net-firewall:ipset-7.10:20210222-211554.log'. * The ebuild environment file is located at '/var/tmp/portage/net-firewall/ipset-7.10/temp/environment'. * Working directory: '/var/tmp/portage/net-firewall/ipset-7.10/image' * S: '/var/tmp/portage/net-firewall/ipset-7.10/work/ipset-7.10' !!! post install failed; exiting. Reproducible: Always
The ebuild both passes --disable-static and deletes .la files, so it sounds strange this is happening at all (can't reproduce so far). Are you setting anything special through package.env? Like EXTRA_ECONF="--enable-static" allows me to reproduce but isn't something that's supported. If unsure, could you at least attach the mentioned build.log, environment file, and emerge --info then re-open as unconfirmed (if believe still a bug).
Soory, I thought I had added this issues to the tracker bug #765709, but apparently I didn't. net-firewall/ipset fails to install if slibtool is used instead of libtool.
That makes more sense, but try using the rlibtool symlink rather than slibtool directly.
This is not a slibtool or ipset bug, the build needs rlibtool to install correctly. When using slibtool directly both shared and static libraries will be explicitly built and installed while rlibtool will respect --disable-static. Only when the build uses libtool, but not autotools should slibtool{-shared,-static} be used directly.
That's what I thought wrt rlibtool, but I haven't tested slibtool much so the confirmation is welcome. I don't think there's anything to do here.
