https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86746
--- Comment #2 from John Ericson <John.Ericson at Obsidian dot Systems> --- I don't know about such things, but I'd hope that if so ideally `--disable-multilib` would cause a build failure, or otherwise multilib == yes anyways so my patch has no effect. I'd find it very concerning if my patch changed behavior for anyone not in my obscure situation FWIW I just cross-built my libatomic package for my disto for aarch64-unknown-linux-gnu, and it built fine. The x86_64 and aarch64 builds both were given `--disable-multilib`, and both have a lib64->lib symlink.