gh-54872: Remove default OPT=-O for non-GCC compilers by bobzinin · Pull Request #142159 · python/cpython
The configure script was setting OPT="-O" by default for non-GCC compilers, which could conflict with user-specified CFLAGS. This change removes the automatic default, allowing users full control over optimization flags via CFLAGS without unexpected conflicts.
The configure script was setting OPT="-O" by default for non-GCC compilers, which could conflict with user-specified CFLAGS. This change removes the automatic default, allowing users full control over optimization flags via CFLAGS without unexpected conflicts.
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool.
If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead.
gh-54972: Remove default OPT=-O for non-GCC compilers
gh-54872: Remove default OPT=-O for non-GCC compilers
All commit authors signed the Contributor License Agreement.
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool.
If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead.
You need to run make regen-configure.
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool.
If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead.
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool.
If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead.
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool.
If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead.
This PR is stale because it has been open for 30 days with no activity.