Re: [Gimp-user] Terrible time to get 2.01 running

2004-07-18 Thread Jake
On Sunday 18 July 2004 12:25, Sven Neumann wrote: I am sorry but SuSE 9.0 isn't recent and there shouldn't be a problem to install GIMP on a more recent version of SuSE I installed Gimp 2 on SUSE 9 without problems. I don't see anybody on the SUSE lists reporting problems with Gimp on 9.1.

Re: [Gimp-user] Terrible time to get 2.01 running

2004-07-17 Thread Steve Litt
On Saturday 12 June 2004 02:17 am, Michael Schumacher wrote: Greg Rundlett wrote: With other platforms or distros, you're potentially going to run into blockers. These are issues that GIMP developers/testers/volunteers might want to address in a) an install script (if that is even

Re: [Gimp-user] Terrible time to get 2.01 running

2004-07-17 Thread Carol Spears
On Sat, Jul 17, 2004 at 12:57:55PM -0400, Steve Litt wrote: On Saturday 12 June 2004 02:17 am, Michael Schumacher wrote: Greg Rundlett wrote: With other platforms or distros, you're potentially going to run into blockers. These are issues that GIMP developers/testers/volunteers might

Re: [Gimp-user] Terrible time to get 2.01 running

2004-07-17 Thread Sven Neumann
Hi, Steve Litt [EMAIL PROTECTED] writes: When we developers use a tool or library to make our work easier, it's our job to make it easy for the user to install that tool or library. We developers? I am sorry but I don't remember you being a GIMP developer. Perhaps you are using a different

Re: [Gimp-user] Terrible time to get 2.01 running

2004-06-13 Thread Robert Krueger
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

Re: [Gimp-user] Terrible time to get 2.01 running

2004-06-13 Thread Carol Spears
On Sun, Jun 13, 2004 at 01:36:18PM -0400, Robert Krueger wrote: On Fri, 11 Jun 2004, Greg Rundlett wrote: 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

Re: [Gimp-user] Terrible time to get 2.01 running

2004-06-13 Thread Greg Rundlett
Maybe you want to try another distro. On my Debian box, I typed apt-get install gimp and it got installed. No problem there. Somewhere I read recently that if you switch to Debian, you'll be asking yourself Why didn't I do this sooner?I can vouch for that. A lot of times you see somebody

Re: [Gimp-user] Terrible time to get 2.01 running

2004-06-12 Thread Michael Schumacher
Greg Rundlett wrote: With other platforms or distros, you're potentially going to run into blockers. These are issues that GIMP developers/testers/volunteers might want to address in a) an install script (if that is even possible) or b) an install guide. I expect the more 'polished' software

Re: [Gimp-user] Terrible time to get 2.01 running

2004-06-12 Thread Sven Neumann
Hi, Greg Rundlett [EMAIL PROTECTED] writes: I don't know. I guess I don't know where to find this info so if there is somewhere else on the net (e.g. tldp.org) where I can quickly learn the essentials that I'm going to need but are beyond the scope of the gimp.org download page, then it

Re: [Gimp-user] Terrible time to get 2.01 running

2004-06-12 Thread Carol Spears
On Fri, Jun 11, 2004 at 09:36:19PM -0400, Greg Rundlett wrote: Greg Rundlett [EMAIL PROTECTED] writes: My hope is that the 'tricks' to installing on these notoriously difficult distributions can be added to GIMP.org. For example: Compiling from source is not recommended unless you know about

Re: [Gimp-user] Terrible time to get 2.01 running

2004-06-12 Thread John Dietsch
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

Re: [Gimp-user] Terrible time to get 2.01 running

2004-06-11 Thread Greg Rundlett
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

Re: [Gimp-user] Terrible time to get 2.01 running

2004-06-11 Thread Sven Neumann
Hi, Greg Rundlett [EMAIL PROTECTED] writes: My hope is that the 'tricks' to installing on these notoriously difficult distributions can be added to GIMP.org. For example: Compiling from source is not recommended unless you know about X, Y, and Z. To learn more about X, Y, and Z, go here.

Re: [Gimp-user] Terrible time to get 2.01 running

2004-06-11 Thread Greg Rundlett
Greg Rundlett [EMAIL PROTECTED] writes: My hope is that the 'tricks' to installing on these notoriously difficult distributions can be added to GIMP.org. For example: Compiling from source is not recommended unless you know about X, Y, and Z. To learn more about X, Y, and Z, go here. You need

Re: [Gimp-user] Terrible time to get 2.01 running

2004-06-08 Thread rob
Why is package config in /usr/local/bin ? Are you installing the whole of gnome from source to try and get this to work? This will cause problems in the future as you won't be able to automatically upgrade. Did you install glib from source or rpm? Removing the version glib that everything is

Re: [Gimp-user] Terrible time to get 2.01 running

2004-06-08 Thread Jean-Luc Coulon (f5ibh)
Le 07.06.2004 22:49:39, Robert Krueger a écrit : 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

Re: [Gimp-user] Terrible time to get 2.01 running

2004-06-08 Thread Robert Krueger
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

Re: [Gimp-user] Terrible time to get 2.01 running

2004-06-08 Thread Sven Neumann
Hi, Robert Krueger [EMAIL PROTECTED] writes: 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

Re: [Gimp-user] Terrible time to get 2.01 running

2004-06-07 Thread Carol Spears
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

Re: [Gimp-user] Terrible time to get 2.01 running

2004-06-07 Thread Robert Krueger
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.

Re: [Gimp-user] Terrible time to get 2.01 running

2004-06-07 Thread Carol Spears
On Mon, Jun 07, 2004 at 03:30:09PM -0400, Robert Krueger wrote: Carol Spears wrote: On Mon, Jun 07, 2004 at 02:53:44PM -0400, Robert Krueger wrote: 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

Re: [Gimp-user] Terrible time to get 2.01 running

2004-06-07 Thread Steve M Bibayoff
Hello, Carol Spears [EMAIL PROTECTED] wrote: take advantage of the linux origins of the software. building your ownglib is very easy. it does not even need a lot of disc space. Easy to build glibc, but much easier to hose your whole system(everything) if glibc isn't built right. Also,

Re: [Gimp-user] Terrible time to get 2.01 running

2004-06-07 Thread Michael Schumacher
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,

Re: [Gimp-user] Terrible time to get 2.01 running

2004-06-07 Thread Robert Krueger
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.

Re: [Gimp-user] Terrible time to get 2.01 running

2004-06-07 Thread Michael Schumacher
Steve M Bibayoff wrote: Hello, Carol Spears [EMAIL PROTECTED] wrote: take advantage of the linux origins of the software. building your ownglib is very easy. it does not even need a lot of disc space. Easy to build glibc, but much easier to hose your whole system(everything) if glibc isn't

Re: [Gimp-user] Terrible time to get 2.01 running

2004-06-07 Thread Steve M Bibayoff
Hello, Michael Schumacher [EMAIL PROTECTED] wrote: glib != glibc slaps palm to forhead. Sorry about adding noise, wasn't following thread to closely. Steve ___ Gimp-user mailing list [EMAIL PROTECTED]

Re: [Gimp-user] Terrible time to get 2.01 running

2004-06-07 Thread Robert Krueger
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

Re: [Gimp-user] Terrible time to get 2.01 running

2004-06-07 Thread Robert Krueger
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

Re: [Gimp-user] Terrible time to get 2.01 running

2004-06-07 Thread Steve M Bibayoff
Hello, Forwarring, I haven't used Suse in a very long time, and I rarely use pkg-config, so I may be leading you down a wrong road. Robert Krueger [EMAIL PROTECTED] wrote: 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

Re: [Gimp-user] Terrible time to get 2.01 running

2004-06-07 Thread Patrick Shanahan
* Robert Krueger [EMAIL PROTECTED] [06-07-04 14:51]: I am having a terrible time getting 2.01 to run in my Suse 9.0 system. You will find SuSE 9.0 rpms for gimp 2.01 @: http://www.usr-local-bin/org -- Patrick ShanahanRegistered Linux User #207535

Re: [Gimp-user] Terrible time to get 2.01 running

2004-06-07 Thread Sven Neumann
Hi, Robert Krueger [EMAIL PROTECTED] writes: 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. Please go to http://gimp.org/unix/ and use the RPMS linked from there. Sven

Re: [Gimp-user] Terrible time to get 2.01 running

2004-06-07 Thread Robert Krueger
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

Re: [Gimp-user] Terrible time to get 2.01 running

2004-06-07 Thread Carol Spears
On Mon, Jun 07, 2004 at 04:12:36PM -0400, Robert Krueger wrote: Carol Spears wrote: are you absolutely married to suse for a distribution? No offense, Carol, but this thread isn't solving my problem. And I already did build glib from source...several times. I'm not changing distributions

Re: [Gimp-user] Terrible time to get 2.01 running

2004-06-07 Thread Thong Nguyen
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