On 16. 01. 23 21:37, Fabio Valentini wrote:
Isn't the problem here that building Python extensions needs to work correctly in two - possibly conflicting - scenarios: - in RPM packages, where using system compiler flags is a MUST
Yes and packages get *all* the Fedora RPM flags that way via: - https://fedoraproject.org/wiki/Changes/SetBuildFlagsBuildCheck - %py3_build, %pyproject_wheel, etc.
- when user installs Python packages manually, for example with pip in a venv, where using system compiler flags isn't necessary (or necessarily a good idea)
This is the case this thread is about.
Just dropping everything but `-fexceptions` would certainly violate Packaging Guidelines (i.e. packages not getting built with default compiler and hardening flags) in the first scenario, wouldn't it?
Dropping it from %{extension_*flags} would not change any Fedora package except such packages that %undefine _auto_set_build_flags and don't use macros to build stuff but invoke the build manually somehow -- such packages should already be recognizable by not having annobin and package ELF notes.
-- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok _______________________________________________ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
