![]() ![]() (sys-apps/util-linux-2.24.1-r3:0/0::gentoo, ebuild scheduled for merge) pulled in by (sys-apps/util-linux-2.25.2-r2:0/0::gentoo, ebuild scheduled for merge) pulled in by !!! into the dependency graph, resulting in a slot conflict: !!! Multiple package instances within a single package slot have been pulled $ emerge -avDN are the packages that would be merged, in order: So, how should I approach satisfying systemd or getting rid of this persistent flag?Īlso, if I end up removing the "static-libs" flag from some of the packages that required it for a working genkernel initramfs to install systemd, wouldn't that mean that systemd is incompatible of regenerating an genkernal-next initramfs with lvm/luks (or does genkernal-next have a dependency solver, and the static requirement is incorrect)? Apparently the flag is very persistent (at least I haven't found this described in the manpages so far). So, now I'll try to disable static-libs in libudev: `echo "virtual/libudev -static-libs" > /dev/portage/e/libudev`. ![]() Now, when i run `emerge -avDN libudev complains that it's not compatible with static-libs and systemd. udev and systemd were blocking each other, so I uninstalled udev. Now I would like to install systemd, so I set it up based on the systemd target. While setting up initramfs with genkernel-next, I compiled lvm2 and cryptsetup with static-libs (which is required for static, which I've read is a requirement). So I'm setting up a system, which involves systemd, lvm and luks. Posted: Sat 6:28 am Post subject: Static-libs for genkernel-next and systemd incompatibility Gentoo Forums Forum Index Installing Gentoo ![]() Static-libs for genkernel-next and systemd incompatibility Gentoo Forums :: View topic - Static-libs for genkernel-next and systemd incompatibility ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |