On Wednesday 29 June 2005 03:59 pm, Joao S. O. Bueno Calligaris wrote:
> On Wednesday 29 June 2005 08:40, John R. Culleton wrote:
> > On Wednesday 29 June 2005 08:52 am, John R. Culleton wrote:
> > > thought it was time to rename the thread since I have gone past
> > > the problems with pygtk.
> > >
> > > If anything else comes up of interest I will report back.
> > It seems that the error reported earlier prevented final
> > compilation so I had unstable splash screens but still the same
> > old 2.2 Gimp in actuality.
> > Back to the drawing board. :<(
> Are you running the program as "gimp-2.3" ?
> "gimp" is just a symbolic link to the actual binary, and the unstable
> versions to not replace this link to themselves.
That indeed was part of the problem. The rest revolves around
intltool. Gim unstable wouldn't take version 30. So I upgraded to
version 32.1 That gave problems with both cvs downloads.
Now I have upgraded to 33 (which comes with the 2.3.1 gimp
tarball BTW) and now stable will compile and install without
I still have the 2.3.1 tarball version in a separate directory
so in an emergency I can recompile in a hurry over there.
Books with answers to marketing and publishing questions:
Book coaches, consultants and packagers:
Gimp-user mailing list