Martin v. Löwis added the comment:
In all versions of make, make CFLAGS=... should work fine (although
that's not an environment variable).
--
nosy: +loewis
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1453
__
Guido van Rossum added the comment:
This depends on the version of Make used. See the man page for Make.
--
nosy: +gvanrossum
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1453
__
New submission from Miki Tebeka:
Setting CFLAGS environment variable do not show up in the build process,
the gcc flags do not include the CFLAGS flags.
--
components: Build
messages: 57588
nosy: tebeka
severity: normal
status: open
title: Python does not honor CFLAGS environment
Guido van Rossum added the comment:
I think you misunderstand. Passing a variable to configure makes that
setting have effect *during the configure run*.
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1453
__
Guido van Rossum added the comment:
Any standard way to add custom compilation flags?.
Beats me. I'm no autoconf expert.
--
resolution: - wont fix
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1453
Martin v. Löwis added the comment:
Any standard way to add custom compilation flags?.
See the README. Set OPT to influence the optimization flags;
set EXTRA_CFLAGS otherwise.
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1453
Miki Tebeka added the comment:
OK, let's close it then.
(However note that in two projects I've checked - vim and pcre the
CFLAGS environment variable do get reflected in the build process)
Any standard way to add custom compilation flags?.
__
Tracker [EMAIL
