Summary: | sys-process/tini[static] requires sys-libs/llvm-libunwind[static-libs] | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Josh Klar (klardotsh) <josh> |
Component: | Current packages | Assignee: | Zac Medico <zmedico> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | williamh |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=892956 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | sys-process/tini[static] build.log without sys-libs/llvm-libunwind[static-libs] |
*** This bug has been marked as a duplicate of bug 892956 *** |
Created attachment 849778 [details] sys-process/tini[static] build.log without sys-libs/llvm-libunwind[static-libs] When building app-containers/docker on a Musl-LLVM system, sys-process/tini (which must be build with +static per Docker's ebuild requirements, at least with +container-init) fails to build unless sys-libs/llvm-libunwind is built with +static-libs. That USE dependency should be marked in tini's ebuild. I have not tested against the other libunwind to know if the same fix applies there, but I assume it would. If there's a metapackage that controls libunwind (since the two implementations are mutually exclusive by RDEPS), the fix should probably be made there; I haven't looked into those ebuilds yet. build.log of the failure attached. After oneshotting llvm-libunwind +static-libs, oneshotting tini works, and I can get back to building Docker.