On Tue, Nov 23, 2021 at 4:39 PM Walter Dnes <[email protected]> wrote: > > The part "Mask packages that rely on amd64 multilib" implies that > something in the package relies on multilib. This is the first time > I've run into something requiring multilib since trying to build WINE, > ages ago. And my system is no-multilib. Is there a way around this? >
I haven't used it in a while, but the SDK installer largely installs prebuilt binaries and other files from upstream, and I'm guessing that some of those are 32-bit. If all you need is adb then there is dev-util/android-tools, which I'm guessing is fine with multilib (it looks like a regular source-based package at a glance). If you need the SDK you could force it to be unmasked and maybe the parts that you need might happen to work, but I wouldn't count on it. I don't think it would break anything on your system - it would just fail to work correctly and you could unmerge it. If it wants to pull in a bunch of other masked stuff I'd hesitate to unmask anything else without a good understanding of what you're doing. -- Rich
