sys-fs/multipath-tools failes in install fase with error: Files matching a file type that is not allowed Reproducible: Always Steps to Reproduce: 1. emerge sys-fs/multipath-tools Actual Results: >>> Completed installing sys-fs/multipath-tools-0.8.6 into /tmp/ramtmp/.lnv/portage/sys-fs/multipath-tools-0.8.6/image * Final size of build directory: 6552 KiB (6.3 MiB) * Final size of installed tree: 1528 KiB (1.4 MiB) Files matching a file type that is not allowed: lib/libdmmp.so.0.2.0 lib/libmultipath.so.0 lib/libmpathpersist.so.0 lib/libmpathcmd.so.0 lib/libmpathvalid.so.0 * ERROR: sys-fs/multipath-tools-0.8.6::gentoo failed: * multilib-strict check failed!
Created attachment 722635 [details] envinronment
Created attachment 722638 [details] build log
Created attachment 722641 [details] emerge info
At first, I was rather confused, because your log looks rather different to mine. All of my "building ... because of ..." lines are followed by a clear GCC inovcation: >building nvme.o because of nvme.c >x86_64-pc-linux-gnu-gcc -O2 -pipe -march=native -fdiagnostics-color=always -frecord-gcc-switches --std=gnu99 -DBIN_DIR=\"/sbin\" -DLIB_STRING=\"lib64\" -DRUN_DIR=\"run\" -MMD -MP -fPIC -I.. -I../../libmultipath/nvme -Wp,-D_FORTIFY_SOURCE=2 -c -o nvme.o nvme.c I then realised you set: >MAKEOPTS="... -s" Please don't do that. If you want quiet builds, use Portage's --quiet-build=y. At least for reporting bugs, we need verbose build logs. I need to see what's going wrong. (Also, no need to compress attachments under ~1MB.) That said, trying it myself, I still successfully built with your MAKEOPTS. Have you successfully built this before?
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9a01e5f5c63a9eb7b7e64497d19dca8cce093eed commit 9a01e5f5c63a9eb7b7e64497d19dca8cce093eed Author: Sam James <sam@gentoo.org> AuthorDate: 2021-07-12 06:39:13 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2021-07-12 06:39:13 +0000 sys-fs/multipath-tools: assorted (mostly build system) fixes * Explicitly set LIB to ${EPREFIX}/$(get_libdir) to avoid guessing. * No longer set SYSTEMD in emake (upstream now use pkgconfig for this) * Respect PKG_CONFIG (now respects the 'PKGCONFIG' variable upstream) * Unrestrict tests (add missing cmocka dependency first). Passing here. * Don't compress man pages Bug: https://bugs.gentoo.org/801121 Closes: https://bugs.gentoo.org/780660 Signed-off-by: Sam James <sam@gentoo.org> ...ltipath-tools-0.8.6-no-compress-man-pages.patch | 226 +++++++++++++++++++++ .../multipath-tools-0.8.6-r1.ebuild | 88 ++++++++ 2 files changed, 314 insertions(+)
Created attachment 727572 [details] build log without -s flag
(In reply to Marco Clocchiatti from comment #6) > Created attachment 727572 [details] > build log without -s flag sorry. sys-fs/multipath-tools-0.8.6-r1 works fine for me (but it needs ~amd64 accept keyword).
(In reply to Marco Clocchiatti from comment #7) > (In reply to Marco Clocchiatti from comment #6) > > Created attachment 727572 [details] > > build log without -s flag > > sorry. > > sys-fs/multipath-tools-0.8.6-r1 works fine for me (but it needs ~amd64 > accept keyword). Thank you!
ppc64 stable
x86 done
arm64 done
ppc stable
amd64 stable. Closing.
