Re: [Gimp-user] Terrible time to get 2.01 running
John Dietsch wrote: On Fri, 11 Jun 2004, Greg Rundlett wrote: rob wrote: Rember you need all the -dev rpms if you want to compile stuff. It would be a much much beter idea for you to install the rpm. Ditching suse for debian would also be a good idea. I too had literally the worst experience thus far in my Linux life trying to install GIMP 2.0 on a Fedora Core distro. Some blame may go to FC and some to the GIMP website. I do NOT know enough about installing software and administering Linux systems to accurately identify what made my experience so dreadful. However, let me point out that it just 'worked' on Windows. All I had to do was download the exe installer for GTK and GIMP, install A before B, and it was done. On Fedora, I tried installing RPM, but had failed dependencies that I could *not* find. The point is this.it doesn't matter *why* it is difficult, it matters that it *is* difficult. The result is that people will not use the GIMP unless they are on Windows, or they are/have access to a Linux guru to install it. This is like deja-vu. I recently completed a thread with the exact same scenario, only using SuSe linux 9.0.My wife downloaded Gimp 2.01 on her Dell XP laptop, and it works...bingo! No problems, no configurations, no dependencies, no bulls---, it just works. I'm still screwing around trying to get it to work, but your point is 100% correct. If this extremely common situation is not resolved for the ordinary user, it will be yet one more example showing that Linux never got beyond the Geek stage. Robert Chopped Here Greg, For Fedora, you need to learn to use yum. If you installed FC from an RPM, it should already be there. Check in /etc for yum.conf . If it's not there, go to the source where you got the Fedora RPM and install yum. For the new Gimp you need to be in Fedora Core 2. As ROOT, do an update to be sure you are current with patches. yum -y update yum will check your system packages, for patches and dependancies, download the needed files, then run a test transaction to be sure it can succeed. Then it will do the installation. Running this on a regular basis will keep you up to date for any patches for vulnerabilities that have been found and corrected. To install Gimp run yum -y install gimp I hope this helps. John Dietsch ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] Terrible time to get 2.01 running
Thong Nguyen wrote: On Mon, 7 Jun 2004, Robert Krueger wrote: checking for pkg-config... /usr/local/bin/pkg-config checking for GLIB - version = 2.2.0... *** 'pkg-config --modversion glib-2.0' returned 2.2.3, but GLIB (2.3.6) *** was found! If pkg-config was correct, then it is best *** to remove the old version of GLib. 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 It seems to me that pkg-config returns one version and the linker finds another version, in this case pkg-config returns 2.2.3 and the linker finds 2.3.6. I would try to update the list of files the linker uses to find libraries to link by doing ldconfig as root. If that doesn't work then try editing /etc/ld.so.conf, or where ever that file is if you system uses this this and rearrange the paths for the libraries to list the version returned by pkg-config first. If you don't want to all that above, just set LD_LIBRARY_PATH to the directory where your 2.2.3 glib is and that should fix this problem. Of course, I've read that this method is not a good thing to do because it does something bad but I don't remember what. Hope that helps Thong OK, let's see if I miss anybody here. Thong - did all that...including LD_LIBRARY_PATH Et All - Wanky??At any rate, everything was checked at compile time of gimp. I went down the list posted on the site of dependencies, and if I didn't have that version on my 9.0 system, I built it from source. If anything complained that it needed something newer, it was added.Eventually, everything compiled correctly as source. The error I stated in the beginning was the only one left to solve, which I have brought to this forum. Tim and others - The location of the only existing glib-2.0.pc files on my system are located in /usr/local/lib/pkgconfig, and /opt/gnome/lib/pkgconfig, of which both are listed in PKG_CONFIG_PATH, so this is not the issue, it appears. I cannot locate any other file that ends with .pc and starts with glib. I cannot locate the particular file or text that seems to be confusing pkgconfig into thinking that 2.3.6 is still on the system. It was installed in the early stages of trying to solve this problem, but has since been removed. Glibc on my system is 2.3.3, which is stock for 9.1, and in compliance with gimp 2.01 requirements. As there is no other glib*.pc file on my system, the information concerning 2.3.6 is obviously coming from somewhere else, and locating this source seems to me to be the most important direction for me to take, if I had a clue as to where to look. Barring some new direction from you folks, I will start again from scratch, checking currently installed versions, adding what's missing, rechecking to see if they registered, and so on.But until proven otherwise, I firmly believe that locating the source of the information that is returning 2.3.6 to the configure script of gimp is the next step towards solving this problem. I really appreciate all of your input, truly, you have all tried to help me sort this out. I'm not giving up yet, but when I do, I'll probably fork out another $80.00 to upgrade to 9.1.As an aside, every Linux system has it's loyal followers, and I am no exception. I've installed 3-4 versions each of RedHat, Mandrake, and Suse over the last 4 years, and have had the best experience with SuSe, no doubt partly due to the advances of the system in general, but also due to system characteristics that make my life easier for the many tasks I do. At this stage of the Linux evolutionary ladder, the three I've mentioned and Debian as well are all good, solid systems. Thanks, Robert ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] Terrible time to get 2.01 running
Carol Spears wrote: On Mon, Jun 07, 2004 at 02:53:44PM -0400, Robert Krueger wrote: Hi, I am having a terrible time getting 2.01 to run in my Suse 9.0 system.I do have 1.2 working ok, but I have read everything I can on this, and spent 3 weeks on and off trying to get it to configure.I feel especially bad because we downloaded the 2.01 Windows version onto my wifes new Dell laptop with the XP system, and it's running peachy, no problems.The main problem centers around pkg-config.Here's the error. pkg-config --modversion glib-2.0' returned 2.2.3 but GLIB ( 2.3.6 ) was found! i had similar problems with debian. i did not type pkg-config --modversion glib-2.0' but figured it out some other way (i read spew too much). the way i solved it on debian was to build a cvs version of glib in /usr/local and add it to the path when i built my own deb of gtk2. the developers lied to me or have something else going on when they told me that debian gave them a working version. too much script-fu in their background, i think. carol I have the feeling that if I just eliminate the files for glib 2.3.6 or the text that pkg-config found, that it would configure without complaint. I don't know how to find and eliminate this text or files, though. Robert ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] Terrible time to get 2.01 running
Robert Krueger wrote: On Mon, Jun 07, 2004 at 02:53:44PM -0400, Robert Krueger wrote: Hi, I am having a terrible time getting 2.01 to run in my Suse 9.0 system.I do have 1.2 working ok, but I have read everything I can on this, and spent 3 weeks on and off trying to get it to configure.I feel especially bad because we downloaded the 2.01 Windows version onto my wifes new Dell laptop with the XP system, and it's running peachy, no problems.The main problem centers around pkg-config.Here's the error. pkg-config --modversion glib-2.0' returned 2.2.3 but GLIB ( 2.3.6 ) was found! As an additional note, here is the complete message: checking for pkg-config... /usr/local/bin/pkg-config checking for GLIB - version = 2.2.0... *** 'pkg-config --modversion glib-2.0' returned 2.2.3, but GLIB (2.3.6) *** was found! If pkg-config was correct, then it is best *** to remove the old version of GLib. 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 Sure would like some help... Thanks, Robert ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] Terrible time to get 2.01 running
Michael Schumacher wrote: Carol Spears wrote: On Mon, Jun 07, 2004 at 03:30:09PM -0400, Robert Krueger wrote: I have the feeling that if I just eliminate the files for glib 2.3.6 or the text that pkg-config found, that it would configure without complaint. I don't know how to find and eliminate this text or files, though. well, that is the thing about linux. you are still trying to work with the distribution. distributions break. Doesn't Suse have a tool used for package management (yast2, iirc)? Maybe removing and/or upgrading glib with this toll can help? HTH, Michael Already did that. That's why I have 2.2.3 on the system. Robert ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] Terrible time to get 2.01 running
Michael Schumacher wrote: Carol Spears wrote: On Mon, Jun 07, 2004 at 03:30:09PM -0400, Robert Krueger wrote: I have the feeling that if I just eliminate the files for glib 2.3.6 or the text that pkg-config found, that it would configure without complaint. I don't know how to find and eliminate this text or files, though. well, that is the thing about linux. you are still trying to work with the distribution. distributions break. Doesn't Suse have a tool used for package management (yast2, iirc)? Maybe removing and/or upgrading glib with this toll can help? HTH, Michael What I need is for someone to work with me to find out how to eliminate all traces of 2.3.6 so pkg-config doesn't see two versions.That's my first best-step in eliminating this problem. Robert ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] Re: Terrible time to get 2.01 running
William Skaggs wrote:
You should be looking for a file named glib-2.0.pc, and it is
probably located in a directory called pkgconfig. In Fedora the
default is /usr/lib/pkgconfig but I believe it is different in
SuSE. If pkg-config data files are located elsewhere than in
the default directory, then the environment variable
PKG_CONFIG_PATH gives a list of the possible locations.
Hope this helps,
-- Bill
Steve and Bill,
I found the file you noted in /usr/local/lib/pkgconfig.It's the
only location on my system that has this particular file, although I do
have other *.pc files in another location /opt/gnome/lib/pkgconfig.
So, if I understand this correctly, if I eliminate the glib-2.0.pc
from /usr/local/lib/pkgconfig, and then do another make install from
glib 2.2.3, it should recreate that file again in that directory, correct?
Now I'm just guessing, but there must be an alternate file with
2.3.6 version somewhere, else how is it getting that information?
BTW, here's the result from /usr/local/lib/pkgconfig/glib-2.0.pc:
prefix=/usr/local
exec_prefix=${prefix}
libdir=${exec_prefix}/lib
includedir=${prefix}/include
glib_genmarshal=glib-genmarshal
gobject_query=gobject-query
glib_mkenums=glib-mkenums
Name: GLib
Description: C Utility Library
Version: 2.2.3
Libs: -L${libdir} -lglib-2.0
Cflags: -I${includedir}/glib-2.0 -I${libdir}/glib-2.0/include
The result of this file leads me to believe there is another source
where pkgconfig is getting it's outdated info, i.e, glib 2.3.6.
Robert
___
Gimp-user mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] Terrible time to get 2.01 running
Steve M Bibayoff wrote: snip Also, what does: $ echo $PKG_CONFIG_PATH give you? Steve I apologize for the deletion. Here's what I get: /usr/local/lib/pkgconfig:/usr/lib/pkgconfig:/opt/gnome/lib/pkgconfig Even though there are multiple locations for the directory /pkgconfig, there is only one glib-2.0.pc file, in fact, there is no other *.pc file that begins with glib. Thanks Robert ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
