Re: [Gimp-developer] pygtk automake problem

[Burnie West <west ieee org>]

On 08/04/2013 01:11 PM, Michael Henning wrote:
> Are you on linux? If you are, then the only things you should really
> need to build yourself are babl, gegl, and gimp. Install your distro's
> packages for everything else, and you should be good to go. If you
> have issues with python, then you may need to do this before running
> gimp's autogen.sh:
>
> export PYTHON="/usr/bin/python2"
Thanks for your help, Michael. But gimp's autogen.sh fails the same way.
The last few lines of the configure process are:
checking whether /usr/bin/python2 version is >= 2.5.0... yes
checking for /usr/bin/python2 version... 2.7
checking for /usr/bin/python2 platform... linux2
checking for /usr/bin/python2 script directory... 
${prefix}/lib/python2.7/site-packages
checking for /usr/bin/python2 extension module directory... 
${exec_prefix}/lib64/python2.7/site-packages
checking for headers required to compile python extensions... found
checking for PYGTK... no
configure: error:
*** Could not find PyGTK 2.10.4 or newer.

Yes, I'm on linux.  /usr/bin/python2, /usr/bin/python, /usr/bin/python2.7 and 
/bin/python are all python 2.7.3.

The command I used was:

./autogen.sh --prefix=$HOME --program-prefix=My- --disable-gtk-doc --enable-debug

./autogen.sh needs the arguments above; other environment variables were set per 
Hacking:Building

I had to build glib in order to build gegl.