On Wednesday 29 June 2005 01:14 pm, Simon Budig wrote:
John R. Culleton ([EMAIL PROTECTED]) wrote:
Earlier in my journey autogen.sh had complained about an
obsolete intltool so I installed version 32 of that package.
Did you rerun autogen.sh after updating intltool?
I removed the cvs/gimp
On Wednesday 29 June 2005 12:40, John R. Culleton wrote:
Back to the drawing board. :(
poor you :(. i am reading this thread with interest and am thinking of
having a go myself but i am reluctant to do this incase it overwrites my
current installation. can i install, or try to install the
On Tuesday 28 June 2005 23:27, Richard Nagle wrote:
Too bad one can¹t use the real epson driver... with Gimp.
it seems to me your problem is with gimp print and not gimp per se. did
you ask at the the gimp print forum as i suggested some while ago ?
sammi
On Wed, Jun 29, 2005 at 04:55:16PM +0100, sam ende wrote:
On Wednesday 29 June 2005 12:40, John R. Culleton wrote:
Back to the drawing board. :(
poor you :(. i am reading this thread with interest and am thinking of
having a go myself but i am reluctant to do this incase it overwrites my
On Wed, Jun 29, 2005 at 12:59:31PM -0300, 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.
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
On Wednesday 29 June 2005 02:41 pm, John R. Culleton wrote:
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
complaint.
I still have the 2.3.1 tarball
I am working with unstable CVS (2.3.2) and am just trying things
out. I can find plugins on my disk that have the suffix .py
which means of course that they are written in python. But often
they have identical names and functions as older script-fu
products. So how to I specify the python plug in
On Wed, Jun 29, 2005 at 05:56:35PM +, John R. Culleton wrote:
I am working with unstable CVS (2.3.2) and am just trying things
out. I can find plugins on my disk that have the suffix .py
which means of course that they are written in python. But often
they have identical names and
I tried rebuilding Gimp 2.2.6. Closer inspection of the 'gmake' output
revealed the following.
...
Making all in plug-ins
gmake[2]: Entering directory `/usr/share/src/gimp/gimp-2.2.6/plug-ins'
gmake[3]: Entering directory `/usr/share/src/gimp/gimp-2.2.6/plug-ins'
gmake[3]: Nothing to be done for
10 matches
Mail list logo
