We have to talk about annobin... again

[Neal Gompa]

Hey all,

So I was trying to update libseccomp last night, and I was able to
build it for everything except aarch64 on Rawhide because it says the
compiler can't build executables[1].

Looking a bit closer, it looks like the compiler stack is out of sync
again with annobin.

Is there anything that can be done to keep the compiler teams from
submitting gcc into rawhide without doing the required rebuild cycle
to make it so annobin works?

And we're going to have the same problem with clang now that annobin
grew a clang plugin, so I would want neither LLVM nor GCC to land in
Rawhide unless those teams are literally ensuring that annobin isn't
breaking the compiler afterward.

I'm personally very tired of having the compiler break so frequently
because of that plugin. Either some kind of mechanism to hold back GCC
builds until annobin works is implemented, or I'd much rather see the
whole thing go away. Obviously, you could just *bundle* annobin into
the GCC package and build it together to ensure it never broke, but
that option was discarded already[2].

Somebody fix it. ASAP.

[1]: https://koji.fedoraproject.org/koji/taskinfo?taskID=47796366
[2]:
https://lists.fedoraproject.org/archives/list/[e-mail].o...

-- 
真実はいつも一つ！/ Always, there's only one truth!