[issue10663] configure shouldn't set a default OPT

Change by Irit Katriel : -- resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python

[issue10663] configure shouldn't set a default OPT

Arfrever Frehtes Taifersar Arahesis added the comment: configure.in is old name of Autoconf input file. configure.ac is new name of Autoconf input file (and the only name to be supported in some future version of Autoconf). configure.in in CPython project was renamed to configure.ac in 2012 (c

[issue10663] configure shouldn't set a default OPT

Irit Katriel added the comment: I couldn't find a configure.in. Is this issue out of date? -- nosy: +iritkatriel ___ Python tracker ___ ___

[issue10663] configure shouldn't set a default OPT

Éric Araujo added the comment: Sounds reasonable. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue10663] configure shouldn't set a default OPT

Changes by Éric Araujo : -- nosy: +eric.araujo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue10663] configure shouldn't set a default OPT

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue10663] configure shouldn't set a default OPT

New submission from Antoine Pitrou : The configure.in sets a default OPT of "-O" if none was set by the user, but I think that's wrong. The user could simply pass optimization flags as part of CFLAGS instead, and then the contents of OPT could conflict with that of CFLAGS (which is annoying to