[issue3290] python-config --cflags includes irrelevant flags

Changes by Terry J. Reedy : -- nosy: -terry.reedy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue3290] python-config --cflags includes irrelevant flags

Matthias Klose added the comment: > However in my case I am embedding python as a scripting language > into another application. then why not filtering out these options on your own for this use case? -- ___ Python tracker

[issue3290] python-config --cflags includes irrelevant flags

Matthias Braun added the comment: It's less of a problem when building python extenions, where you are probably fine with using "just the same" as the installed python. However in my case I am embedding python as a scripting language into another application. So there is very few python relate

[issue3290] python-config --cflags includes irrelevant flags

Matthias Klose added the comment: I don't see the current behaviour as problematic. If you build python as a debug build, you get the -O0 included, if you do a normal build, you get the -Ox included. At least this is behaviour found in other '-config' programs too. So maybe add an option to

[issue3290] python-config --cflags includes irrelevant flags

Changes by Georg Brandl : -- assignee: georg.brandl -> doko nosy: +doko ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue3290] python-config --cflags includes irrelevant flags

Matthias Braun added the comment: I hacked up a proof-of-concept patch which filters out the most annoying flags (warnings, -Ox and -DNDEBUG flags). (Though IMO the only really robust solution would be not having code but just declarations in the public headers, so --includes is enough. In my

[issue3290] python-config --cflags includes irrelevant flags

Joe Neeman added the comment: It's still an issue in Python 2.6.5 as packaged by openSUSE 11.2. -- nosy: +Joe.Neeman ___ Python tracker ___ __

[issue3290] python-config --cflags includes irrelevant flags

Terry J. Reedy added the comment: Is this still an issue for current trunks? -- nosy: +tjreedy versions: +Python 2.7, Python 3.2 -Python 2.5 ___ Python tracker ___ __

[issue3290] python-config --cflags includes irrelevant flags

Erick Tryzelaar <[EMAIL PROTECTED]> added the comment: fyi, on the mac with gcc-4.2, distutils is erroring out because of the "- Wno-long-double" it is getting from "python-config --cflags", as it's no longer accepted as an argument. Fortunately this can be worked around by doing "CC=gcc-4.0 py

[issue3290] python-config --cflags includes irrelevant flags

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: Some flags for the compiler are really needed to compile the Python headers correctly, e.g. -fno-strict-aliasing in 2.6. So I think an explicit list of options reported would have to be maintained, either as a blacklist (e.g. -O, -Wall), or

[issue3290] python-config --cflags includes irrelevant flags

Georg Brandl <[EMAIL PROTECTED]> added the comment: I think you're right. However, Martin, what flags except -I can/must we keep? ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue3290] python-config --cflags includes irrelevant flags

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: Georg, what do you think? -- assignee: -> georg.brandl nosy: +georg.brandl, loewis ___ Python tracker <[EMAIL PROTECTED]> __

[issue3290] python-config --cflags includes irrelevant flags

New submission from Sacha Varma <[EMAIL PROTECTED]>: 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 i