[New-bugs-announce] [issue10663] configure shouldn't set a default OPT

Antoine Pitrou report at bugs.python.org
Thu Dec 9 20:25:31 CET 2010


New submission from Antoine Pitrou <pitrou at free.fr>:

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 debug when you don't know what is happening exactly).

Besides, "-O" is hardly an useful default value for any compiler. I would advocate trimming down the magic and letting OPT empty/undefined if that's what the user asks for (and expects). What do you think?

----------
components: Build
messages: 123695
nosy: barry, dmalcolm, laca, pitrou
priority: normal
severity: normal
status: open
title: configure shouldn't set a default OPT
type: behavior
versions: Python 2.7, Python 3.1, Python 3.2

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue10663>
_______________________________________


More information about the New-bugs-announce mailing list