Message 69289 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	sacha
Recipients	sacha
Date	2008-07-05.19:09:05
SpamBayes Score	0.013634739
Marked as misclassified	No
Message-id	<1215284947.23.0.370691849564.issue3290@psf.upfronthosting.co.za>
In-reply-to

Content
As I understand it, python-config --cflags is intended to yield the C compiler flags needed to compile a program that uses Python headers and libraries (as opposed to the C flags needed to compile python itself). However, it seems to include irrelevant options such as -Wall and -O3, which interfere with the build (for example, by enabling optimisation in a debug build): $ python-config --cflags -I/opt/Python-2.5.1/include/python2.5 -I/opt/Python-2.5.1/include/python2.5 -fno-strict-aliasing -Wno-long-double -no-cpp-precomp -mno-fused-madd -DNDEBUG -g -O3 -Wall -Wstrict-prototypes

As I understand it, python-config --cflags is intended to yield the C
compiler flags needed to compile a program that uses Python headers and
libraries (as opposed to the C flags needed to compile python itself).

However, it seems to include irrelevant options such as -Wall and -O3,
which interfere with the build (for example, by enabling optimisation in
a debug build):

$ python-config --cflags
-I/opt/Python-2.5.1/include/python2.5
-I/opt/Python-2.5.1/include/python2.5 -fno-strict-aliasing
-Wno-long-double -no-cpp-precomp -mno-fused-madd -DNDEBUG -g -O3 -Wall
-Wstrict-prototypes

History
Date	User	Action	Args
2008-07-05 19:09:08	sacha	set	spambayes_score: 0.0136347 -> 0.013634739 recipients: + sacha
2008-07-05 19:09:07	sacha	set	spambayes_score: 0.0136347 -> 0.0136347 messageid: <1215284947.23.0.370691849564.issue3290@psf.upfronthosting.co.za>
2008-07-05 19:09:06	sacha	link	issue3290 messages
2008-07-05 19:09:05	sacha	create