distro wide cflags are a bad idea anyway

Posted Jan 17, 2023 17:15 UTC (Tue) by mwsealey (subscriber, #71282)
In reply to: distro wide cflags are a bad idea anyway by ballombe
Parent article: Fedora's tempest in a stack frame

I hear you just volunteered to audit every package in the repository and add a special toggle as to whether it needs -fomit-frame-pointers or no -fomit-frame-pointers.

distro wide cflags are a bad idea anyway

Posted Jan 28, 2023 21:09 UTC (Sat) by sammythesnake (guest, #17693) [Link] (2 responses)

I'm not very familiar with Fedora's organisational structure (or much more familiar with that of $other_distro that I use) but couldn't that be a choice made in a package by package basis by the relevant package maintainers?

distro wide cflags are a bad idea anyway

Posted Jan 29, 2023 12:52 UTC (Sun) by rahulsundaram (subscriber, #21946) [Link]

> I'm not very familiar with Fedora's organisational structure (or much more familiar with that of $other_distro that I use) but couldn't that be a choice made in a package by package basis by the relevant package maintainers?

Yes, Fedora already does that. For instance, Python excludes it based on the performance impact cited in the article. Defaults only apply when the maintainer hasn't changed it. It is not enforced for every package.

distro wide cflags are a bad idea anyway

Posted Jan 29, 2023 12:53 UTC (Sun) by mathstuf (subscriber, #69389) [Link]

That will just result in a whack-a-mole flurry of issues for people asking their favorite packages to turn it on/off depending on their preferences. A distro-wide with specific exclusions makes more sense IMO.