gh-54872: Remove default OPT=-O for non-GCC compilers#142159
Conversation
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 |
Sorry, something went wrong.
Sorry, something went wrong.
|
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 |
Sorry, something went wrong.
|
You need to run |
Sorry, something went wrong.
|
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 |
Sorry, something went wrong.
98956c5 to
cd68588
Compare
December 1, 2025 19:22
|
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 |
Sorry, something went wrong.
cd68588 to
6dc8463
Compare
December 2, 2025 08:17
|
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 |
Sorry, something went wrong.
|
This PR is stale because it has been open for 30 days with no activity. |
Sorry, something went wrong.
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.