I am trying to compile in openSUSE 12.3 a program which uses "waf" to build. It fails to detect Python.h because the test program is compiled with -O0 and -D_FORTIFY_SOURCE=2, and you can't use both at the same time. The FORTIFY_SOURCE part comes from waf using: "get_config_var('CFLAGS')". And from what I can see that gets the CFLAGS used to build python itself from %{_libdir}/python2.7/config/Makefile, from the python-base package. Now, I don't know the first thing about the "Python way". So, can somebody answer: - There is really some use for Python defining this CFLAGS "config_var"? - It's normal for the build systems to try to retrieve get_config_var('CFLAGS')? Why? - We really need a Makefile in python-base? - And %{_libdir}/python2.7/config/Makefile.pre and %{_libdir}/python2.7/config/Makefile.pre.in in python-devel? - Should the python package be patched to remove "%{optflags}" from %{_libdir}/python2.7/config/Makefile? Thanks. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org