[gnome-builder] build: use python3-config --includes instead of --cflags

[Christian Hergert <chergert src gnome org>]

commit e07b6aa2368b158b518dce3b9182169ae08cabdd
Author: Christian Hergert <christian hergert me>
Date:   Mon May 11 13:27:40 2015 -0700

    build: use python3-config --includes instead of --cflags
    
    using --cflags causes us to get things like -D_FORTIFY_SOURCE=2. And while
    _FORTIFY_SOURCE is nice, it collides with our choices to build with things
    like -O0.
    
    In other words, we should be in control of things like optimization flags.
    
    We should consider autoharden or something soon though.

 configure.ac |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/configure.ac b/configure.ac
index dd13195..f322d5c 100644
--- a/configure.ac
+++ b/configure.ac
@@ -201,7 +201,7 @@ AC_PATH_TOOL(PYTHON3_CONFIG, "python3-config")
 AS_IF([test -z "${PYTHON3_CONFIG}"],[
   AC_MSG_ERROR([Failed to locate python3-config.])
 ])
-LIBIDE_CFLAGS="${LIBIDE_CFLAGS} `${PYTHON3_CONFIG} --cflags`"
+LIBIDE_CFLAGS="${LIBIDE_CFLAGS} `${PYTHON3_CONFIG} --includes`"
 LIBIDE_LIBS="${LIBIDE_LIBS} `${PYTHON3_CONFIG} --libs`"
 LIBIDE_LDFLAGS="${LIBIDE_LDFLAGS} `${PYTHON3_CONFIG} --ldflags`"