This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author matthiaskoeppe
Recipients docs@python, matthiaskoeppe
Date 2022-01-14.18:38:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1642185496.49.0.558821862955.issue46381@roundup.psfhosted.org>
In-reply-to
Content
The documentation of
- https://docs.python.org/3.11/using/configure.html#envvar-CFLAGS
- https://docs.python.org/3.11/using/configure.html#envvar-CFLAGS_NODIST
- https://docs.python.org/3.11/using/configure.html#envvar-LDFLAGS
- https://docs.python.org/3.11/using/configure.html#envvar-LDFLAGS_NODIST
should explain more clearly that flags such as `-I`, `-L`, etc. and strict compiler flags such as `-Werror...` should not be put into `CFLAGS`, `LDFLAGS`, or it will make the resulting Python unusable for compiling user packages with extension modules via `distutils` and `setuptools`.

Various downstream packagers have provided misconfigured Pythons:
- Homebrew (https://trac.sagemath.org/ticket/31132, https://github.com/Homebrew/homebrew-core/pull/68528, resolved)
- Cygwin (https://trac.sagemath.org/ticket/33078, https://cygwin.com/pipermail/cygwin/2021-December/250302.html, resolved in a proposed package update)
- pyenv (https://trac.sagemath.org/ticket/32531, https://github.com/pyenv/pyenv/issues/2204, open)

So this appears to be a documentation / user education issue in CPython.
History
Date User Action Args
2022-01-14 18:38:16matthiaskoeppesetrecipients: + matthiaskoeppe, docs@python
2022-01-14 18:38:16matthiaskoeppesetmessageid: <1642185496.49.0.558821862955.issue46381@roundup.psfhosted.org>
2022-01-14 18:38:16matthiaskoeppelinkissue46381 messages
2022-01-14 18:38:16matthiaskoeppecreate