On Thu, Jan 15, 2004 at 03:40:47PM +0100, Brad Kligerman wrote:

Hi all/

I've been trying to upgrade from GIMP 1.2.3 that was installed with RH9 to GIMP 1.3.23.
It won't configure, and I get the following...

[root@localhost gimp-1.3.23]# ./configure ......>>>>>
checking for pkg-config... (cached) /usr/bin/pkg-config checking for GTK+ - version >= 2.2.2...

Perhaps you have the old version of GTK+ residing at /usr/bin and the new version somewhere in /usr/local?

Hi,

Brad Kligerman writes:

I've been trying to upgrade from GIMP 1.2.3 that was installed with RH9 to GIMP 1.3.23.
It won't configure, and I get the following...

[root@localhost gimp-1.3.23]# ./configure ......>>>>>
checking for pkg-config... (cached) /usr/bin/pkg-config checking for GTK+ - version >= 2.2.2... *** 'pkg-config --modversion gtk+-2.0' returned 2.2.4, but GTK+ (2.2.1) *** was found! If pkg-config was correct, then it is best *** to remove the old version of GTK+. You may also be able to fix the error
*** by modifying your LD_LIBRARY_PATH enviroment variable, or by editing *** /etc/ld.so.conf. Make sure you have run ldconfig if that is *** required on your system.
*** If pkg-config was wrong, set the environment variable PKG_CONFIG_PATH *** to point to the correct configuration files no configure: error: Test for GTK+ failed. See the file 'INSTALL' for help.

I installed GTK 2.2.4 and followed all the other installation instructions. When I check the version of GTK+ with Synaptic, it shows _GTK2 - version 2.2.1-4_ and not 2.2.4. Is this where the problem is coming from. Any ideas??

Yes, that's where your problem is coming from. While pkg-config locates the new version, your linker takes the library from /usr/lib. The error message suggests the possible solutions. You can modify the linker behaviour by adjusting your LD_LIBRARY_PATH enviroment variable or by editing /etc/ld.so.conf.

Sven

Hi,

Brad Kligerman writes:

I already had edited _/etc/ld.so.conf_ and ran _ldconfig_ as suggested in the message.

So where did you put /usr/local/lib in your library search path then? Does it appear before the path holding the older version of the library?

Sven

On Thu, 2004-01-15 at 09:40, Brad Kligerman wrote:

Hi all/

I've been trying to upgrade from GIMP 1.2.3 that was installed with RH9 to GIMP 1.3.23.
It won't configure, and I get the following...

I solved this one myself. Just get GTK+2.2.4 SOURCES (not the rpm or anything), and compile with these flags. Here's how I did it:

1. remove the old version of gtk (rpm -e --force --nodeps gtk+-2.2.1 for example or whatever will remove just that. Don't remove any other gtk+ packages!!)

2. mkdir /opt/lib/gtk+-2.2.4

3. Compile and install the new gtk+-2.2.4 sources using: # ./configure --eprefix=/opt/lib/gtk+-2.2.4 --prefix=/opt/lib/gtk+-2.2.4 # make
# su
(type in your root password)
# make install

4. Next (still as root), edit /etc/ld.so.conf in a text editor and add the following line:

/opt/lib/gtk+-2.2.4/lib

5. Still as root:

# /sbin/ldconfig

NOTE: If you compile other apps that use GTK+ you might get an error about PKG_CONFIG_PATH not pointing to gtk+-2.0.pc. Do the following to fix that:

# locate gtk+-2.0.pc (take note of the path here) # export PKG_CONFIG_PATH=(path noted above w/o the *.pc filename included)

I know Gimp wants freetype libraries newer than what RH9 has but I didn't install them because it messes with XWindows on my system - the font path in the config gets blitzed. :( Gimp 1.3.23 and Gimp 2.0pre1 both work ok anyway without further packages added other than compiling/installing GTK+2.2.4. If you do like above, it should work ok. Don't know about tablet though because I don't have an art tablet or anything, just mouse.

.:: misfit-x ::.

Hi,

misfit-x writes:

Don't know about tablet though because I don't have an art tablet or anything, just mouse.

If tablet support is desired, gtk+ needs to be configured to provide it. To do so, pass the option --with-xinput=xfree to the gtk+ configure script.

Sven

On Fri, 2004-01-16 at 18:38, Brad Kligerman wrote:

checking for GTK+ - version >= 2.2.2... *** 'pkg-config --modversion gtk+-2.0' returned 2.2.4, but GTK+ (2.2.1) *** was found!
When I tried to uninstall GTK+ (2.2.1) as you suggested, it said 2.2.1 was not installed.

# rpm -qa | grep gtk+

If it shows 2.2.1 then:

# rpm -e --force gtk+-2.2.1

If that didn't work, then there's a config somewhere that's still saying there's a GTK+-2.2.1 somewhere. I have another idea... REinstall GTK+2.2.1, then uninstall it. Then reinstall (just make install in the source tree you compiled GTK+-2.2.4 in, if you still have the sources compiled (ie. didn't delete the dirs or run make clean yet)). And see if that helps.

Before I throw in the towel and go back to Photoshop, I just want to understand what my _/etc/ld.so.conf_ should look like. Mine has the following...

/opt/lib/gtk+-2.2.4/lib/pkgconfig

I would think it should be in /opt/lib/gtk+-2.2.4/lib instead?

/usr/X11R6/lib
/usr/kerberos/lib
/usr/lib/qt-3.1/lib
/usr/lib/sane

Rest of this looks good to me.

If you really really want to run PhotoShop, you can in linux using WINE (www.winehq.org). Runs slower but works - at least PS LE 5 worked for me. However, I would rather use Gimp, personally.

You can still use Gimp 1.2.x but the new 2.0pre1 is really nice. :)

Hi,

misfit-x writes:

If that didn't work, then there's a config somewhere that's still saying there's a GTK+-2.2.1 somewhere. I have another idea... REinstall GTK+2.2.1, then uninstall it. Then reinstall (just make install in the source tree you compiled GTK+-2.2.4 in, if you still have the sources compiled (ie. didn't delete the dirs or run make clean yet)). And see if that helps.

It isn't even necessary to remove the 2.2.1 version. The problem here is the wrong usage of /etc/ld.so.conf as you outlined below:

understand what my _/etc/ld.so.conf_ should look like. Mine has the following...

/opt/lib/gtk+-2.2.4/lib/pkgconfig

Just like misfit-x pointed out already, this is of course completely wrong. /etc/ld.so.conf has nothing to do with pkg-config. I would strongly suggest to take a short look at the man-pages before doing such changes. It certainly helps to know what files you are editing.

I would think it should be in /opt/lib/gtk+-2.2.4/lib instead?

This is a very unusual install prefix that was choosen for gtk+ here. But if it's indeed "/opt/lib/gtk+-2.2.4", then the value you suggested is absolutely correct.

Sven

Hi,

Brad Kligerman writes:

By hook or by crook, I finally managed to compile GIMP2.0. I still don't understand why it was such a mess, but I learned a whole bunch in the process. Thanks go out to both of you for your patience.

As for GIMP 2.0, I started it immediately after I got it compiled and everything worked fine, in fact it looks great. But since I rebooted, I get the following message:>
$ gimp-1.3
gimp-1.3: error while loading shared libraries: libgimpcolor-1.3.so.24: cannot open shared object file: No such file or directory

The file _libgimpcolor-1.3.so.24_ is in /usr/local/lib and is linked to _libgimpcolor-1.3.so.24.1.0_.
Any ideas what's going on?

You probably set LD_LIBRARY_PATH to get gimp going and your linker can't find the library now that it isn't set. You will want to read the ldconfig man-page to learn how to configure the linker path persistently.

Sven