ATM it's worked around by appending --no-as-needed. It's been reported upstream, but I doubt they care much about.
I have tiny question, since there is 3.5.2 is it fixed in it? Lazy to do verbump myself O:]
No, we still need to pass --no-as-needed. I've reported it upstream, but got no reply.
Created attachment 183604 [details, diff] Preliminary patch Patch by flameeyes, triggers another error, but here to track progress.
Flameeyes gave me a working patch, fixed in 2.8.1.