[Thunar-dev] libexo fails to build

[Benedikt Meurer]

Jens Luedicke wrote:
> Hey Benny!

Hi Jens,

>  gcc -DHAVE_CONFIG_H -I. -I. -I.. -DHAVE_GNUC_VISIBILITY
> -DEXO_API_SUBJECT_TO_CHANGE -I.. -I/usr/include/gtk-2.0
> -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo
> -I/usr/include/pango-1.0 -I/usr/include/glib-2.0
> -I/usr/lib/glib-2.0/include -I/opt/xfce4-svn//include/xfce4
> -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
> -I/usr/include/pygtk-2.0 -I/usr/include/glib-2.0
> -I/usr/lib/glib-2.0/include -fno-strict-aliasing
> -I/usr/include/python2.4 -g -O2 -O0 -g3 -Werror -Wall -MT
> _exo_la-exomodule.lo -MD -MP -MF .deps/_exo_la-exomodule.Tpo -c
> exomodule.c  -fPIC -DPIC -o .libs/_exo_la-exomodule.o
> In file included from /usr/include/python2.4/Python.h:8,
>                  from /usr/include/pygtk-2.0/pygobject.h:5,
>                  from pyexo.h:28,
>                  from exomodule.c:27:
> /usr/include/python2.4/pyconfig.h:835:1: "_POSIX_C_SOURCE" redefined
> In file included from /usr/include/limits.h:26,
>                  from /usr/lib/gcc/i686-pc-linux-gnu/3.4.5/include/limits.h:122,
>                  from
> /usr/lib/gcc/i686-pc-linux-gnu/3.4.5/include/syslimits.h:7,
>                  from /usr/lib/gcc/i686-pc-linux-gnu/3.4.5/include/limits.h:11,
>                  from /usr/lib/glib-2.0/include/glibconfig.h:11,
>                  from /usr/include/glib-2.0/glib/gtypes.h:30,
>                  from /usr/include/glib-2.0/glib/gstrfuncs.h:31,
>                  from /usr/include/glib-2.0/glib/gi18n-lib.h:22,
>                  from ../exo/exo.h:32,
>                  from pyexo.h:26,
>                  from exomodule.c:27:
> /usr/include/features.h:190:1: this is the location of the previous definition

Lunars python config seems to conflict with a system header (both
defining _POSIX_C_SOURCE). pyconfig.h is just the config file generated
by Pythons configure, which explains why _POSIX_C_SOURCE is defined here
(of course it's pretty lame to install this config file, but that's how
it is).

Does it work if you include pygobject.h and pygtk/pygtk.h before
exo/exo.h in pyexo.h?

> Jens Luedicke

Benedikt