Hi -

I'm trying to build gimp with pygtk; got (AFAIK) all the current stuff.

But I'm hung up on the autogen.sh for pygtk.

I executed command ./autogen.sh --prefix=$HOME && make -j4 && make install

System response: $ ./autogen.sh --prefix=$HOME && make -j4 && make install checking for autoconf >= 2.53...
testing autoconf2.50... not found. testing autoconf... found 2.69
checking for automake >= 1.8...
testing automake-1.8... not found. testing automake-1.9... not found. testing automake-1.10... not found. testing automake-1.11... not found. ***Error***: You must have automake >= 1.8 installed to build PyGTK. Download the appropriate package for from your distribution or get the source tarball at http://ftp.gnu.org/pub/gnu/automake/automake-1.8.tar.gz

I'm a bit reluctant to downrev automake for this --

My automake is -1.12. What should I do?

-- Burnie

On 08/04/2013 09:12 AM, Michael Henning wrote:

Line 204 of autogen.sh should look like this: 1.8*) automake_progs="automake-1.8 automake-1.9 automake-1.10 automake-1.11" ;;
Add your version of automake to the end, like this: 1.8*) automake_progs="automake-1.8 automake-1.9 automake-1.10 automake-1.11 automake-1.12" ;;

That should compile for you.

If you're not doing development, it might be better to grab the latest tarball and just run configure on that, instead of running autogen. Then your automake version won't matter.

I'm actually planning to do help with development, if I can get up to speed for it. On Sat, Aug 3, 2013 at 11:04 PM, Burnie West wrote:

Hi -

I'm trying to build gimp with pygtk; got (AFAIK) all the current stuff.

But I'm hung up on the autogen.sh for pygtk.

Thanks much, Michael. Turns out I should not have dealt with pygtk at all. The current version of pygtk is 2.24.0; it dates back to October 2011. And it's already been installed.

But reading hacking:building, I inferred I might need to work on gtk+ as well; this took me into gtk+-3, with which apparently pygtk does not (yet) work.

And I already had pygtk/2.0 installed natively.

On 08/04/2013 10:41 AM, Burnie West wrote:

And I already had pygtk/2.0 installed natively.

But for some reason, even though the installation is in fact pygtk2-2.24.0, it installs in the directory pygtk/2.0 (Fedora 18), as I had noted earlier. I've very little experience with the configure script; indeed, little expreience with console scripting. But it appears the configure script cannot cope with this formulation, and I'm currently attempting to find out why.

As my current intent is to work on python plugins (a particular one in fact), building My-gimp without python support is a non-starter. I'd already successfully built babl, gegl, and gimp-2.9.0 about a year ago, but had disabled the python section (as lightningismyname had suggested) and dropped that path.

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.

On 08/04/2013 02:49 PM, Owen wrote:

This might sound stupid, but do you have pygtk, ie, what is in

${prefix}/lib/python2.7/site-packages (on my system it's called dist-packages)

2.10.4 is pretty old so if its there, the version number probably isn't the problem.

I have /usr/lib64/pygtk/2.0, which is the April 01, 2011 pygtk2-2.24.0

But it is not in /usr/lib/python2.7/site-packages. There's LOTS of stuff there, the only pyg is pygment.

I made a softlink in sitepackages back to pygtk; same result. Then I recursively copied /usr/lib64/pygtk to /usr/lib/python2.7/site-packages; same result.

On 08/04/2013 03:31 PM, Burnie West wrote:

On 08/04/2013 02:49 PM, Owen wrote:

This might sound stupid, but do you have pygtk, ie, what is in

${prefix}/lib/python2.7/site-packages (on my system it's called dist-packages)

2.10.4 is pretty old so if its there, the version number probably isn't the problem.

I have /usr/lib64/pygtk/2.0, which is the April 01, 2011 pygtk2-2.24.0

But it is not in /usr/lib/python2.7/site-packages. There's LOTS of stuff there, the only pyg is pygment.

The foregoing was not quite correct. pygtk.py and related files are in /usr/lib64/python2.7/site-packages but not in /usr/lib/python2.7/site-packages.

So I tried links in /usr/lib/python2.7site-packages to the four pygtk.* entries in /usr/lib64/python2.7/site-packages.

This does not work, however. Gets the same configure failure message. For confirmation:
# updatedb
# locate pygtk.p
/usr/lib/python2.7/site-packages/pygtk.pth /usr/lib/python2.7/site-packages/pygtk.py /usr/lib/python2.7/site-packages/pygtk.pyc /usr/lib/python2.7/site-packages/pygtk.pyo /usr/lib64/python2.7/site-packages/pygtk.pth /usr/lib64/python2.7/site-packages/pygtk.py /usr/lib64/python2.7/site-packages/pygtk.pyc /usr/lib64/python2.7/site-packages/pygtk.pyo

On 08/04/2013 05:19 PM, Burnie West wrote:

On 08/04/2013 03:31 PM, Burnie West wrote: So I tried links in /usr/lib/python2.7site-packages to the four pygtk.* entries in /usr/lib64/python2.7/site-packages.

This does not work, however. Gets the same configure failure message.

For what it might be worth, the following messages appeared shortly before the failure in the configure phase of the autogen.sh execution: checking for a Python interpreter with version >= 2.5.0... python checking for python... /usr/bin/python checking for python version... 2.7
checking for python platform... linux2 checking for python script directory... ${prefix}/lib/python2.7/site-packages checking for python extension module directory... ${exec_prefix}/lib64/python2.7/site-packages checking for headers required to compile python extensions... found

On 08/04/2013 03:31 PM, Burnie West wrote:

On 08/04/2013 02:49 PM, Owen wrote:

This might sound stupid, but do you have pygtk, ie, what is in

${prefix}/lib/python2.7/site-packages (on my system it's called dist-packages)

2.10.4 is pretty old so if its there, the version number probably isn't the problem.

I have /usr/lib64/pygtk/2.0, which is the April 01, 2011 pygtk2-2.24.0

But it is not in /usr/lib/python2.7/site-packages. There's LOTS of stuff there, the only pyg is pygment.

I made a softlink in sitepackages back to pygtk; same result. Then I recursively copied /usr/lib64/pygtk to /usr/lib/python2.7/site-packages; same result.

config.log explains pygtk-2.0.pc is missing -- "Perhaps you should add the directory containing `pygtk-2.0.pc'"

The statement is true. However, no directory in my system contains that specific configuration file. I have so far not figured out precisely how to create a configuration file. Perhaps someone could show me an example? TIA

On 08/06/2013 05:13 PM, Burnie West wrote:

On 08/04/2013 03:31 PM, Burnie West wrote:

On 08/04/2013 02:49 PM, Owen wrote:

This might sound stupid, but do you have pygtk, ie, what is in

${prefix}/lib/python2.7/site-packages (on my system it's called dist-packages)

2.10.4 is pretty old so if its there, the version number probably isn't the problem.

I have /usr/lib64/pygtk/2.0, which is the April 01, 2011 pygtk2-2.24.0

But it is not in /usr/lib/python2.7/site-packages. There's LOTS of stuff there, the only pyg is pygment.

I made a softlink in sitepackages back to pygtk; same result. Then I recursively copied /usr/lib64/pygtk to /usr/lib/python2.7/site-packages; same result.

config.log explains pygtk-2.0.pc is missing -- "Perhaps you should add the directory containing `pygtk-2.0.pc'"

The statement is true. However, no directory in my system contains that specific configuration file. I have so far not figured out precisely how to create a configuration file. Perhaps someone could show me an example? TIA

Please forgive this string of messages, which I think may be related to the 'git problem' thread

Absent a response, I hand-built (with considerable reluctance) a pygtk-2.0.pc and put it in my configuration path: My pygtk-2.0.pc is

prefix=/usr/lib/python2.7/site-packages exec_prefix={prefix}
data_dir=/usr/share/doc/pygtk2-2.24.0 libdir={prefix}

Name: pygtk2 Description: Extension module for Python for GTK+-2 Version: 2.24.0

This was progress, b/c I now proceed to this error: configure: error:
*** Could not find pygtk-codegen-2.0 script. Searching on-line, I find this information from an unrelated source (https://github.com/mxcl/homebrew/issues/14888): "If "pygtk-codegen-2.0" is deprecated, then upstream scripts that call it should be updated to call "pygobject-codegen-2.0".

It is undoubtedly clear to the awesome GIMP developers - as it is clear to me - that I'm over my head here.

Please advise me - would you prefer I simply shut up or is there a path you can recommend?

-- Burnie

On 08/06/2013 11:40 PM, Owen wrote:

On Tue, 06 Aug 2013 20:07:30 -0700 Burnie West wrote:

On 08/06/2013 05:13 PM, Burnie West wrote:

On 08/04/2013 03:31 PM, Burnie West wrote:

On 08/04/2013 02:49 PM, Owen wrote:

This might sound stupid, but do you have pygtk, ie, what is in

${prefix}/lib/python2.7/site-packages (on my system it's called dist-packages)

2.10.4 is pretty old so if its there, the version number probably isn't the problem.

I have /usr/lib64/pygtk/2.0, which is the April 01, 2011 pygtk2-2.24.0

But it is not in /usr/lib/python2.7/site-packages. There's LOTS of stuff there, the only pyg is pygment.

I made a softlink in sitepackages back to pygtk; same result. Then I recursively copied /usr/lib64/pygtk to /usr/lib/python2.7/site-packages; same result.

config.log explains pygtk-2.0.pc is missing -- "Perhaps you should add the directory containing `pygtk-2.0.pc'"

The statement is true. However, no directory in my system contains that specific configuration file. I have so far not figured out precisely how to create a configuration file. Perhaps someone could show me an example? TIA

Please forgive this string of messages, which I think may be related to the 'git problem' thread

Absent a response, I hand-built (with considerable reluctance) a pygtk-2.0.pc and put it in my configuration path: My pygtk-2.0.pc is

prefix=/usr/lib/python2.7/site-packages exec_prefix={prefix}
data_dir=/usr/share/doc/pygtk2-2.24.0 libdir={prefix}

Name: pygtk2 Description: Extension module for Python for GTK+-2 Version: 2.24.0

This was progress, b/c I now proceed to this error: configure: error:
*** Could not find pygtk-codegen-2.0 script. Searching on-line, I find this information from an unrelated source (https://github.com/mxcl/homebrew/issues/14888): "If "pygtk-codegen-2.0" is deprecated, then upstream scripts that call it should be updated to call "pygobject-codegen-2.0".

It is undoubtedly clear to the awesome GIMP developers - as it is clear to me - that I'm over my head here.

I don't have past message in this thread so I don't know your OS/platform.

However, you have done the wrong thing by hand rolling a .pc file.

On this Suse-12.3 I have two packages, python-gtk and python-gtk-devel

When the ...-devel package is installed, the pc file is also installed, together with all other dependencies to support the "devel" file.

So have a look round for python-gtk-devel, or might be pygtk-dev in other distros.

On 08/06/2013 10:49 PM, Michael Schumacher wrote:

Did you install the corresponding development packages for python, pygtk and any other needed module from your distro's repository?

I'm on Fedora 18.
Found and installed pygtk2-devel, installed it together with pygtklext-devel and pygtksourceview-devel,
This resulted in configure success, although apparently my lcms installation seemed not to work.
Makes and installs fine

Thanks for your help :-)

On 08/07/2013 03:26 PM, Owen wrote:

On 08/06/2013 10:49 PM, Michael Schumacher wrote:

Did you install the corresponding development packages for python, pygtk and any other needed module from your distro's repository?

I'm on Fedora 18.
Found and installed pygtk2-devel, installed it together with pygtklext-devel and
pygtksourceview-devel,
This resulted in configure success, although apparently my lcms installation
seemed not to work.
Makes and installs fine

So, do you have the lcms development packages? There is liblcms1 and liblcms2, search for them, install the *.devel files and try again

I actually knew three years ago to install the devel files, but by this year I had forgotten.
But I did install lcms-devel and lcms-debuginfo as well as lcms2-devel and lcms-debuginfo before my successful compilation. RPM's lcms and lcms2 were already both installed. config.log mentioned several other libraries that were not available (openEXR, webkit, librsvg, poppler, gudev).
I'm still puzzlling over lcms2, though.