Hi,

Andrew Langdon-Davies wrote:

Having battled my way through configure, make and make install and having finally completed the process without any apparent error messages, Gimp-2 does not actually show up anywhere. What directory should it be in? If I do 'gimp', the old one starts up. All libraries are Mandrake-9.2 rpms.

The old GIMP installs the binary gimp-1.2 and the new one installs gimp-1.3 (this will eventually be gimp-2.0).

While we are not in a stable release, the gimp binary will be a symlink to gimp-1.2 - once we are stable, we will enable by default the option to have gimp point to gimp-2.0.

So - to answer your question - the GIMP binary you're looking for is gimp-1.3 - if you want to have /usr/local/bin/gimp point at this, add the argument --enable-default-binary to your call to configure.

Cheers, Dave.

On Tue, 2004-03-16 at 12:10, Andrew Langdon-Davies wrote:

And now the nitty-gritty: I've installed the Epkowa iscan plug-in for epson scanners, but when I select it from the menu gimp-1.3 crashes as follows:

gimp_composite: use=yes, verbose=no supported by gimp_composite: +mmx +sse +sse2 -3dnow -altivec -vis

GLib-ERROR **: could not allocate 1072693248 bytes aborting...

(gimp-1.3:31399): Gimp-Plug-In-WARNING **: gimp-1.3: plug_in_flush(): error: Broken pipe
plug_in_close: extension aborted before sending its extension_ack message

(The same plug-in works fine with 1.2)

What you are seeing is a plug-in crash - likely because the plug-in has not been ported to work with GIMP 2.0.

Sincerely, Brix

Hi,

Andrew Langdon-Davies wrote:

And now the nitty-gritty: I've installed the Epkowa iscan plug-in for epson scanners, but when I select it from the menu gimp-1.3 crashes as follows:
GLib-ERROR **: could not allocate 1072693248 bytes aborting...

(gimp-1.3:31399): Gimp-Plug-In-WARNING **: gimp-1.3: plug_in_flush(): error: Broken pipe
plug_in_close: extension aborted before sending its extension_ack message

(The same plug-in works fine with 1.2)

Is this at start-up? This is a 3rd party plug-in, so it's not really supported by us. I can tell you that a 1.2 plug-in that you copy directly into the plug-ins directory of 1.3 will not work, since there have been incompatible API changes between 1.2 and 2.0. You should be able to compile a 1.2 plug-in for 2.0 almost unchanged if you add -DGIMP_ENABLE_COMPAT_CRUFT -D to your CFLAGS environment variable before you compile it with gimptool (however, take this statement with a pinch of salt).

The plug-in author may prefer to port the plug-in to GTK+ 2.0, and take advantage of some of the helper widgets which have been added to libgimp since the 1.2 release, though.

Hope this helps, Dave.

On Tuesday 16 March 2004 04:28 am, Andrew Langdon-Davies wrote:

Using Mandrake-9.2. Gimp-1.2 is installed. Having battled my way through configure, make and make install and having finally completed the process without any apparent error messages, Gimp-2 does not actually show up anywhere. What directory should it be in? If I do 'gimp', the old one starts up. All libraries are Mandrake-9.2 rpms.
Andrew

In /usr/local/bin look for gimp-1.3. It is really Gimp-2.0. Copy or link that file to "gimp" in the same directory and you are in business.

I run Slackware 9.1. YMMV

John Culleton Able Typesetters and Indexers
http://wexfordpress.com