Hello all, Currently on Fedora the -D_FORTIFY_SOURCE=2 compiler flag is enabled by default. However it seems that the minimum acceptable optimization option for it, is -Og and if -O0 is specified, a ton of warnings are generated: warning _FORTIFY_SOURCE requires compiling with optimization (-O) My use case is the python3-debug package, as compiling it with -Og, optimizes out a lot of information that python's gdb integration tests for. Some of the previous discussions on it [0][1]. There has been a proposal to gcc upstream to overhaul the -Og option [2] but it didn't move anywhere. So my solution to that would be to change the default compilation option for the python3-debug package to -O0 and strip out -D_FORTIFY_SOURCE=2 from CFLAGS. This provides us with an obvious solution to the issue, instead of debating about compiler semantics, however that would go against Fedora's default compilation options. Would that be an acceptable solution for this issue? AFAIK the flag cannot be disabled by conventional means, which hints that packages are not supposed to meddle with it, however I can't see any way of moving things forward. [0] https://bugzilla.redhat.com/show_bug.cgi?id=1734327 [1] https://bugzilla.redhat.com/show_bug.cgi?id=1818857 [2] https://gcc.gnu.org/legacy-ml/gcc-patches/2019-06/msg01394.html -- Regards, Charalampos Stratakis Software Engineer Python Maintenance Team, Red Hat _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
