On Fri, Nov 13, 2020 at 3:59 PM Jude DaShiell <jdash...@panix.com> wrote:
> Thanks for the decode, I hope I'll get better at understanding this kind > of error output in future. > > On Fri, 13 Nov 2020, Neil Bothwick wrote: > > > Date: Fri, 13 Nov 2020 18:28:32 > > From: Neil Bothwick <n...@digimed.co.uk> > > Reply-To: gentoo-user@lists.gentoo.org > > To: gentoo-user@lists.gentoo.org > > Subject: Re: [gentoo-user] systemd install attempt busybox and pam are > > fighting > > > > On Fri, 13 Nov 2020 17:40:43 -0500, Jude DaShiell wrote: > > > > > !!! The ebuild selected to satisfy "sys-apps/busybox" has unmet > > > requirements. > > > - sys-apps/busybox-1.32.0-r1::gentoo USE="ipv6 pam static systemd > > > -debug -livecd -make-symlinks -math -mdev -savedconfig (-selinux) > > > -sep-usr -syslog" ABI_X86="(64)" > > > > > > The following REQUIRED_USE flag constraints are unsatisfied: > > > pam? ( !static ) > > > > It means that if you have the pam USE flag set, the static flag must be > > unset. You can have one or the other, or neither, but not both. > > As a related comment, I highly recommend having a statically linked busybox installed on your system. It can save your bacon if something breaks. Several years ago there was a problem where "expr" was missing a dependency on gmp. gmp got upgraded without rebuilding "expr", and that resulted in "expr" not working. I tried to reinstall "expr" but emerge required "expr" to work so I was in a bind. Luckily I had a statically linked busybox on the system - I just hard-linked busybox to "/usr//bin/expr" and that was sufficient to get emerge to rebuild the proper "expr". This was a case where even booting with a live CD would have been tricky, because as soon as I'd done a chroot I would have ended up with the same broken "expr". Having a static busybox saved me a lot of hassle. -- Manuel A. McLure WW1FA <man...@mclure.org> <http://www.mclure.org> ...for in Ulthar, according to an ancient and significant law, no man may kill a cat. -- H.P. Lovecraft
