The following USE changes are necessary to proceed:
#required by sys-apps/busybox-1.20.2[static], required by @system, required by @world (argument)
>=sys-libs/libselinux-2.1.12-r1 static-libs

Meanwhile, adding

Code:

=sys-libs/libselinux static-libs

to package.use produces another error with env-update:

Code:

--- Invalid atom in /etc/portage/package.use: =sys-libs/libselinux

So far, I've only run into this with packages and flags that seem somewhat useful, stuff that I had taken out of my make.conf for a oneshot install to break circular dependencies, like with mesa and X.

But this time, I have no idea what the use-flag "static-libs" does. It builds static libraries... and I don't know what that means for my system. If I put that flag into my make.conf, portage quits complaining, and *everything* is built as and using static libs. But... there has to be a downside to it, right? Otherwise, why would I be given that choice of dynamic or static libs?

get rid of the equals sign. It is only used for specifying the exact version, which you are not.

It also will not build everything as static. Only those with the flag. In practice, I don't think you would notice the difference. Package.use is probably a better policy though._________________First things first, but not necessarily in that order.