On Thursday 02 November 2006 09:16, Stephan Hegel wrote:
> Tom Williams wrote:
> > For the record folks, I've got Gimp 2.2.11 installed in /usr (came with
> > my Linux distro) and Gimp 2.3.12 (used to have 2.3.11) installed in
> > /usr/local/gimp-2.3 and I'm able to run either version without any
> > problems, errors, or wrapper scripts (unless gimp-2.3 is a wrapper
> > script).
> That's very interesting. Could you please post the output of
> echo $LD_LIBRARY_PATH
> file /usr/local/gimp-2.3/bin/gimp-2.3
> I'm wondering how this works with multiple gimp libs.
> Kind regards,
> Gimp-user mailing list
Happily I seem to have stumbled into the same situation. I compiled from one
master partition (Slack 11) and run in an older one. /usr/local is the same
in each (same partition linked into the tree.) Gimp 2.3.12 now runs just
fine. Why I don't know. It won't run using the master partition in which it
was compiled. I did have to upgrade glib.
In answer to your questions here are the results:
/usr/local/gimp-2.3/bin/gimp-2.3: cannot open
`/usr/local/gimp-2.3/bin/gimp-2.3' (No such file or directory)
No wrappers installed.
Go figure. Hey, I have a working Gimp of recent vintage. I am not touching a
thing. And I won't upgrade to Slack 11.x until it has Gimp 2.4.x included.
Don't mess with success.
My executable is /usr/local/bin/gimp-2.3. It yields two errors on startup:
/usr/local/lib/gimp/2.0/plug-ins/poppler: error while loading shared
libraries: libpoppler-glib.so.0: cannot open shared object file: No such file
(gimp-2.3:2838): LibGimpBase-WARNING **: gimp-2.3: wire_read(): error
but it seems to run OK.
Able Indexing and Typesetting
Precision typesetting (tm) at reasonable cost.
Gimp-user mailing list