On Sat, 2020-07-25 at 10:46 +0100, Peter Robinson wrote:
On Sat, Jul 25, 2020 at 10:35 AM Neal Gompa
<ngompa13(a)gmail.com> wrote:
> 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.
I've kicked off an annobin build for the short term issue.
I agree here, we used to have the same issue with gcc-plugins back in
the day, sadly this is nothing new :-/
:( I'll raise it again with Nick and
Jakub, it's a sore point for everyone I
think and it causes far more friction than just what we see here in Fedora.
jeff