Re: tracking packages using (temporary) work-arounds to build

[Jonathan Nieder <jrnieder@gmail.com>]

Bill Allombert wrote:
>> In 2011, Matthias Klose wrote:

>>> Some packages use work-arounds to prevent build failures, because
>>> these expose bugs in the build tools; these work-arounds are usually
>>> not reverted, and not tracked, or badly tracked (changelogs
>>> commenting on "new version of gcc").
[...]
> What developers would really need is an easy way to apply patches selectively on the
> version of gcc used.

If you're talking about patches applied in debian/rules, no argument
from me. ;-)

I was guessing that the work-arounds Matthias referred to most often
are in CFLAGS rather than the upstream source files.  Especially, -O1
seems to get used from time to time to work around optimization
problems.  Various -f flags get used in the same way.  Another common
strategy is to explicitly use a specific version of gcc.

Hoping that clarifies,
Jonathan