-
-
Notifications
You must be signed in to change notification settings - Fork 176
Description
Please confirm the following
- I agree to follow the aio-libs Code of Conduct
- I have checked the current issues for duplicates.
- I understand this is open source software provided for free and that I might not receive a timely response.
- I am positive I am NOT reporting a (potential) security
vulnerability, to the best of my knowledge. (These must be shared by
submitting this report form instead, if
any hesitation exists.)
- I am willing to submit a pull request with reporoducers as xfailing test cases or even entire fix. (Assign this issue to me.)
Describe the bug
Since #1586 the default builds are "release" (-g0 -Ofast -NDEBUG -s) or "debug" (-g3 -Og ...).
However, all Linux distributions and probably others such as homebrew and macports, don't build like this at all.
The standard behaviour for Linux is to build with something along the lines of -g -O2 and then split the debug symbols into separate packages, so out of the box the binaries are optimised enough and debug symbols that mostly work are easily available.
The usual way we do this is by setting CFLAGS to the flags we want, and expecting packages to follow them. Whilst I respect your desire for the binary wheels you ship to be built in fully optimised, is there a way to opt out of this behaviour?
To Reproduce
Build yarl, expect debug symbols in the binary.
Expected behavior
Yarl will respect CFLAGS/LDFLAGS and not forcibly add its own flags.
Logs/tracebacks
N/APython Version
$ python --versionmultidict Version
$ python -m pip show multidictpropcache Version
$ python -m pip show propcacheyarl Version
$ python -m pip show yarlOS
Linux
Additional context
No response