On Sun, Jul 8, 2018 at 8:57 PM Kevin Kofler <kevin.kofler(a)chello.at> wrote:
Annobin is causing so many issues, and its main goal of finding packages
that were not built with the correct linker flags has already been achieved
(bugs have been filed for all of them), so do we really need to keep
dragging this thing along all the time? IMHO, it is causing more problems
than it solves and so should be disabled from the default builds. It would
always be possible to enable it in a temporary side tag and do a scratch
mass-rebuild in there if there is a need for it (e.g., to recheck for
missing linker flags at some point).
Why does this debugging tool have to be enabled by default in our production
builds?
I'm increasingly annoyed by annobin these days. On top of the problems
caused by annobin _still_ being a separate source package from gcc and
breaking compilation, I'm not even sure what value it even provides.
Ordinarily, I'd be going "meh" to changes like this, but now I can't
even count on being able to build software in Rawhide anymore, and
potentially even in stable releases!
Can the compiler team just merge the bloody plugin sources into the
gcc source package so that it doesn't randomly break anymore?
*grumbles about not having auto-rebuilding+submitting of reverse deps
so this wouldn't be a problem anymore...*
--
真実はいつも一つ!/ Always, there's only one truth!