Hi,

I have installed distribution's 2.4 and cvs . I built cvs with --preifix=/usr/local but there is some conflict with 2.4 which refuses to run having detected the conflicting library versions. Here the beginning of ldd for 2.4

/usr/bin/gimp
bash-3.2#ldd `!!`
ldd `which gimp`
linux-gate.so.1 => (0xffffe000) libgimpwidgets-2.0.so.0 => /usr/local/lib/libgimpwidgets-2.0.so.0 (0xb7e1a000)
libgimpconfig-2.0.so.0 => /usr/local/lib/libgimpconfig-2.0.so.0 (0xb7e0b000)
libgimpmodule-2.0.so.0 => /usr/local/lib/libgimpmodule-2.0.so.0 (0xb7e06000)
libgimpcolor-2.0.so.0 => /usr/local/lib/libgimpcolor-2.0.so.0 (0xb7dfb000)
libgimpthumb-2.0.so.0 => /usr/local/lib/libgimpthumb-2.0.so.0 (0xb7df2000)
libgimpmath-2.0.so.0 => /usr/local/lib/libgimpmath-2.0.so.0 (0xb7deb000)
libgimpbase-2.0.so.0 => /usr/local/lib/libgimpbase-2.0.so.0 (0xb7dd7000)
libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0xb7a79000) libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0xb79f8000) libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0xb79e0000)
libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0xb79d9000) libpthread.so.0 => /lib/libpthread.so.0 (0xb79c1000)

bash-3.2#echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/kde/3.5/sbin:/usr/kde/3.5/bin:/usr/qt/3/bin bash-3.2#echo $LD_LIBRARY_PATH
/usr/qt/3/lib

I adapted the way I set this up last time but something did not follow.

bash-3.2#which gimp4 /usr/local/bin/gimp4
bash-3.2#cat `!!`
cat `which gimp4`
#!/bin/sh

#PATH=/usr/local/bin:$PATH #export PATH
LD_LIBRARY_PATH=/usr/local/lib
export LD_LIBRARY_PATH

/usr/local/bin/gimp-2.5 "$@"

I don't see why 2.4 is pulling from /usr/local/lib

Any help?

Thx

On Wed, 10 Sep 2008 13:12:42 +0200, Owen wrote:

Hi,

I have installed distribution's 2.4 and cvs . I built cvs with --preifix=/usr/local but there is some conflict with 2.4 which refuses to
run having detected the conflicting library versions. Here the beginning
of ldd for 2.4

bash-3.2#echo $PATH

I think all the paths are getting mixed up

/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/kde/3.5/sbin:/usr/kde/3.5/bin:/usr/qt/3/bin ^^^^^^^^^^^^^^ before ^^^^^^^

bash-3.2#echo $LD_LIBRARY_PATH
/usr/qt/3/lib

It is picking up /usr/local because that is what you path has first (or before /usr/bin )

You are starting Gimp from a console?

You need to set the PATH to see /usr/bin first and the same for LD_LIBRARY_PATH.to see /usr/lib first

export PATH=/usr/bin:$PATH and export LD_LIBRARY_PATH=/usr/lib

and when you start 2.5, do so from another console with the paths set to pick up the 2.5 libraries first.

You should actually keep away from /usr/local, the various bashrc and profile files set up paths to include /usr and /usr/local and it can get confusing.

Just build in /opt in accordance with the instructions for paths.

Yes, it's the scripts that are prepending things , I'd have though /usr/local should come after but I'll need to dig to get the order corrected.

I still don't understand what it's picking from /usr/local/lib since /usr/local/lib is not in path or ld_library_path and ldd shows it loading from /usr/local/lib first no /usr/local. I must have an incomplete idea of the loading mechanism.

Your suggestion of /opt is probably the easiest solution. Thanks. (and Micheal too)

regards.

I adapted the way I set this up last time but something did not follow.

bash-3.2#which gimp4
/usr/local/bin/gimp4
bash-3.2#cat `!!`
cat `which gimp4`
#!/bin/sh

#PATH=/usr/local/bin:$PATH #export PATH
LD_LIBRARY_PATH=/usr/local/lib
export LD_LIBRARY_PATH

/usr/local/bin/gimp-2.5 "$@"

I don't see why 2.4 is pulling from /usr/local/lib

On Thu, 11 Sep 2008 08:42:18 +0200, Sven Neumann wrote:

Hi,

On Wed, 2008-09-10 at 11:26 +0200, gg@catking.net wrote:

I have installed distribution's 2.4 and cvs . I built cvs with --preifix=/usr/local but there is some conflict with 2.4 which refuses to
run having detected the conflicting library versions.

http://gimp.org/release-notes/gimp-2.5.html mentions quite explicitly that this is not going to work. /usr/local is not a separate installation prefix.

Sven

Well that's probably the cause of the confusion, it does not _explicitly_ say " a separate prefix not in the system PATH" which would appear to be the key criterium. Separate presumes separatation from something that is not specified. I took it to mean separate from gimp-2.4 installation since that was subject.

/usr/local is a "separate" prefix from /usr and is separate from where gimp-2.4 is installed. The problem seems to result from this separate prefix being in PATH.
README says this:

If you want to keep your
older GIMP 2.x installation in parallel to GIMP 2.5, you have to choose a separate prefix which is not in your default library search path.

This is also somewhat confusing in that it seems to refer to LD_LIBRARY_PATH.

That's all probably obvious once you know but then the instructions are not for those who know. Maybe they could be 'explicit'.

Now I have just let autogen.sh do it's default /opt/gimp and it's fine.

The UI improvements are starting make Gimp a lot easier to work with and to discover. Excellent progress on that.

Thanks Sven, Mitch, Owen.... and all those who replied.