Re: [Gimp-user] One stupid thing
On Thursday 09 February 2006 07:08 pm, Michael Schumacher wrote: John R. Culleton wrote: Heh. I set up Debian sarge, downloaded Gimp 2.3.8? and tried to compile. Now I am back to the missing XML::Parser problem again. Did you ignore my first mail in this thread? Michael Not at all. I was noting that on two different flavors of linux it is necessary to download and install material beyond that contained in the Gimp download in order to get it to compile. And that wasn't true in prior versions. Perhaps the missing module should be put in with the Gimp tarball if that is legal and practical. Thanks for your assistance. -- John Culleton Books with answers to marketing and publishing questions: http://wexfordpress.com/tex/shortlist.pdf Book coaches, consultants and packagers: http://wexfordpress.com/tex/packagers.pdf ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
[Gimp-user] Default settings for scaling images: high quality?
Dear List, sorry for possible duplications - I only subscribed today! When I resize images, I always use bicubic precision - unless I forget to change from linear (low quality). To avoid this, I'd prefer to have high quality scaling as default option. There must be a way, now? Thanks a lot. Regards Ralf. ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Default settings for scaling images: high quality?
I'd prefer to have high quality scaling as default option. There must be a way, now? FilePreferencesTool options -- Pagarbiai Vytautas Xandros 3.0.2 OCE Opera 8.51 ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
[Gimp-user] Problems compiling GIMP
I am attempting to build GIMP 2.3.7 on an Intel IMac. The configure goes fine, however when I run make I get an error. The following is the tail end of the output: - if gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../.. -I../.. -I../../app -I../../app -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include -DG_LOG_DOMAIN=\Gimp-Composite\ -pthreads -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -DGIMP_DISABLE_DEPRECATED -DG_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -DPANGO_DISABLE_DEPRECATED -DGDK_MULTIHEAD_SAFE -DGTK_MULTIHEAD_SAFE -mmmx -msse -g -O2 -Wall -MT libcompositesse_a-gimp-composite-sse.o -MD -MP -MF .deps/libcompositesse_a-gimp-composite-sse.Tpo -c -o libcompositesse_a-gimp-composite-sse.o `test -f 'gimp-composite-sse.c' || echo './'`gimp-composite-sse.c; \ then mv -f .deps/libcompositesse_a-gimp-composite-sse.Tpo .deps/libcompositesse_a-gimp-composite-sse.Po; else rm -f .deps/libcompositesse_a-gimp-composite-sse.Tpo; exit 1; fi if gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../.. -I../.. -I../../app -I../../app -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include -DG_LOG_DOMAIN=\Gimp-Composite\ -pthreads -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -DGIMP_DISABLE_DEPRECATED -DG_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -DPANGO_DISABLE_DEPRECATED -DGDK_MULTIHEAD_SAFE -DGTK_MULTIHEAD_SAFE -mmmx -msse -g -O2 -Wall -MT libcompositesse2_a-gimp-composite-sse2.o -MD -MP -MF .deps/libcompositesse2_a-gimp-composite-sse2.Tpo -c -o libcompositesse2_a-gimp-composite-sse2.o `test -f 'gimp-composite-sse2.c' || echo './'`gimp-composite-sse2.c; \ then mv -f .deps/libcompositesse2_a-gimp-composite-sse2.Tpo .deps/libcompositesse2_a-gimp-composite-sse2.Po; else rm -f .deps/libcompositesse2_a-gimp-composite-sse2.Tpo; exit 1; fi i686-apple-darwin8-gcc-4.0.1: unrecognized option '-pthreads' i686-apple-darwin8-gcc-4.0.1: unrecognized option '-pthreads' gimp-composite-mmx.c: In function 'gimp_composite_scale_rgba8_rgba8_rgba8_mmx': gimp-composite-mmx.c:1016: error: PIC register '%ebx' clobbered in 'asm' gimp-composite-mmx.c: At top level: gimp-composite-mmx.c:836: warning: 'mmx_op_overlay' defined but not used make[3]: *** [libcompositemmx_a-gimp-composite-mmx.o] Error 1 make[3]: *** Waiting for unfinished jobs gimp-composite-sse.c: In function 'gimp_composite_scale_rgba8_rgba8_rgba8_sse': gimp-composite-sse.c:786: error: PIC register '%ebx' clobbered in 'asm' make[3]: *** [libcompositesse_a-gimp-composite-sse.o] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 - I then can seem to run a make install, but there is no gimp executable. Only gimp-remote seems to get installed. Can someone perhaps lead me in the right direction with this? Thanks! Scott ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Problems compiling GIMP
Hi Scott, Am 10.02.2006 um 20:27 schrieb Scott: I am attempting to build GIMP 2.3.7 on an Intel IMac. The configure goes fine, however when I run make I get an error. The following is the tail end of the output: sorry, can't help with that, I'm still waiting for my new machine (MacBook). How did you try to compile this? I mean, are there fink or darwinports or something like that involved or how did you satisfy all the dependencies of GIMP? lexA --- Live is like a chocolate box, you never know what you wanna get... GPG Signatur auf http://wernicke-online.net/Impressum/ prüfen PGP.sig Description: Signierter Teil der Nachricht ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Problems compiling GIMP
So far I have compiled them all from source.. Since I am new to Mac's I am not sure how to package them yet for easy install.. Otherwise I would make what I have done thus far available on my site. Once I figure out this GIMP issue then I will probably address packaging them up. So far everything else has had no issues using the standard compile process. Fink and folks do not have Intel versions available yet, and I did not want to run in non-native mode. Scott Hi Scott, Am 10.02.2006 um 20:27 schrieb Scott: I am attempting to build GIMP 2.3.7 on an Intel IMac. The configure goes fine, however when I run make I get an error. The following is the tail end of the output: sorry, can't help with that, I'm still waiting for my new machine (MacBook). How did you try to compile this? I mean, are there fink or darwinports or something like that involved or how did you satisfy all the dependencies of GIMP? lexA --- Live is like a chocolate box, you never know what you wanna get... GPG Signatur auf http://wernicke-online.net/Impressum/ prüfen ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] One stupid thing
John R. Culleton wrote: Not at all. I was noting that on two different flavors of linux it is necessary to download and install material beyond that contained in the Gimp download in order to get it to compile. And that wasn't true in prior versions. Um... you're kidding, right? GTK+ Glib libpng libjpeg gcc make ... are also required and not included. Perhaps the missing module should be put in with the Gimp tarball if that is legal and practical. Sorry, but after your previous statement I have troubles to take you serious. Maybe you could help to solve my confusion and tell me why you thinks this could ever be practical? HTH, Michael -- The GIMP http://www.gimp.org | IRC: irc://irc.gimp.org/gimp Wiki http://wiki.gimp.org | .de: http://gimpforum.de Plug-ins http://registry.gimp.org | ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] One stupid thing
On Friday 10 February 2006 04:46 pm, Michael Schumacher wrote: John R. Culleton wrote: Not at all. I was noting that on two different flavors of linux it is necessary to download and install material beyond that contained in the Gimp download in order to get it to compile. And that wasn't true in prior versions. Um... you're kidding, right? GTK+ Glib libpng libjpeg gcc make ... are also required and not included. All these and Perl are either included in a standard full installation of e.g., Slackware or Debian Sarge, As I stated earler previous editions of Gimp have compiled without difficulty. I have Slackware Current up to date as of yesterday. I have Debian Sarge up to date as of yesterday. I can compile older versions of Gimp. My concern is not so much with 2.3.x but with 2.4. If that stable version requires software bits and pieces not found on most Linux systems and not downloadable from ww.gimp.org then there is trouble ahead. -- John Culleton Books with answers to marketing and publishing questions: http://wexfordpress.com/tex/shortlist.pdf Book coaches, consultants and packagers: http://wexfordpress.com/tex/packagers.pdf ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Problems compiling GIMP
On Fri, Feb 10, 2006 at 02:27:42PM -0500, Scott wrote: gimp-composite-sse.c: In function 'gimp_composite_scale_rgba8_rgba8_rgba8_sse': gimp-composite-sse.c:786: error: PIC register '%ebx' clobbered in 'asm' make[3]: *** [libcompositesse_a-gimp-composite-sse.o] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 - I then can seem to run a make install, but there is no gimp executable. Only gimp-remote seems to get installed. Can someone perhaps lead me in the right direction with this? recently there was the same problem with mmx. if you run ./configure --help it will tell you how to build without this sse stuff. these are some optimizations that were included by some guy from Sun and seem to be unmaintained lately. if you are using apple products, you probably are not interested in speed so probably building without that stuff will not seem to hurt performance. carol ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] One stupid thing
glib and gtk+ and other libs required by Gimp might be part of any current Linux distro but they might not be the right versions required by any given Gimp version. As for the XML::Parser perl module, perl installations that come with Linux distros will have some perl modules installed but not all. I think it's reasonable to require the system owner or the person who is building Gimp to make sure external libs and apps are configured per Gimp's requirements. In this case, that means the system owner is responsible for making sure perl is setup per Gimp's requirements unless Gimp is being built with perl support disabled (if that is an option). Peace... Tom John R. Culleton [EMAIL PROTECTED] To s.comgimp-user@lists.xcf.berkeley.edu Sent by: cc gimp-user-bounces @lists.XCF.Berkel Subject ey.EDURe: [Gimp-user] One stupid thing 02/10/2006 02:27 PM On Friday 10 February 2006 04:46 pm, Michael Schumacher wrote: John R. Culleton wrote: Not at all. I was noting that on two different flavors of linux it is necessary to download and install material beyond that contained in the Gimp download in order to get it to compile. And that wasn't true in prior versions. Um... you're kidding, right? GTK+ Glib libpng libjpeg gcc make ... are also required and not included. All these and Perl are either included in a standard full installation of e.g., Slackware or Debian Sarge, As I stated earler previous editions of Gimp have compiled without difficulty. I have Slackware Current up to date as of yesterday. I have Debian Sarge up to date as of yesterday. I can compile older versions of Gimp. My concern is not so much with 2.3.x but with 2.4. If that stable version requires software bits and pieces not found on most Linux systems and not downloadable from ww.gimp.org then there is trouble ahead. -- John Culleton Books with answers to marketing and publishing questions: http://wexfordpress.com/tex/shortlist.pdf Book coaches, consultants and packagers: http://wexfordpress.com/tex/packagers.pdf ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] One stupid thing
On Fri, Feb 10, 2006 at 05:27:23PM -0500, John R. Culleton wrote: On Friday 10 February 2006 04:46 pm, Michael Schumacher wrote: John R. Culleton wrote: Not at all. I was noting that on two different flavors of linux it is necessary to download and install material beyond that contained in the Gimp download in order to get it to compile. And that wasn't true in prior versions. Um... you're kidding, right? GTK+ Glib libpng libjpeg gcc make ... are also required and not included. All these and Perl are either included in a standard full installation of e.g., Slackware or Debian Sarge, As I stated earler previous editions of Gimp have compiled without difficulty. I have Slackware Current up to date as of yesterday. I have Debian Sarge up to date as of yesterday. I can compile older versions of Gimp. My concern is not so much with 2.3.x but with 2.4. If that stable version requires software bits and pieces not found on most Linux systems and not downloadable from ww.gimp.org then there is trouble ahead. we were discussing this on the irc. XML::Parser is needed by intltool and has been for some time now. my thoughts when you mentioned needing this (additional) software from two different distributions was in trying to figure out how this could have happened. i do not install a lot of the stuff that is needed for one of these all knowing and all responsive desktops. this means i am building things on what many of the users would consider a minimal set up. i wonder if this fact about the way i use my computer combined with the way distributions are separating their packages in a way that might not be apparent from the source web sites -- perhaps there is a dependency check that is not registering somewhere. debian purposely breaks libtool the other way. it insists on seeing software that has been purposely and perfectly placed so it won't build and refusing to build at that point instead of going where it knows (or can easily determine) where to go. they like it that way. they closed my bug report. i can talk you through how to build things on sarge so that you can see what i am talking about. everyone i spoke to about my problem was very nice, btw. carol ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Problems compiling GIMP
On Fri, Feb 10, 2006 at 11:49:09PM +0100, Axel Wernicke wrote: Am 10.02.2006 um 23:32 schrieb Carol Spears: if you are using apple products, you probably are not interested in speed so probably building without that stuff will not seem to hurt performance. couldn't you've been simply nice and friendly? Since he tries to build GIMP for the new Intel Macs he's proven to care about performance anyway :) could you assume for a moment that i was being nice and friendly? after a while, when people suggest that you are not being nice and not being friendly when you are, you start to wonder if the person suggesting this is being friendly and is being nice. do people run apple because it is really fast? i am sorry if i got this wrong. i thought they run apple because the products are so sealed up and lovely to look at and the fellow users are so united in thinking. the only apple products i have had opportunity to work with are really slow or in need of a huge network of other apples in which to be able to function on. if anyone were to suggest that i am using my computer because speed is not an issue, i would probably have to agree. carol ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] One stupid thing
John R. Culleton wrote: Not at all. I was noting that on two different flavors of linux it is necessary to download and install material beyond that contained in the Gimp download in order to get it to compile. And that wasn't true in prior versions. Perhaps the missing module should be put in with the Gimp tarball if that is legal and practical. That suggestion would imply that all dependencies be packaged which is nonsense! Owen ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] One stupid thing
John R. Culleton wrote: Not at all. I was noting that on two different flavors of linux it is necessary to download and install material beyond that contained in the Gimp download in order to get it to compile. And that wasn't true in prior versions. Perhaps the missing module should be put in with the Gimp tarball if that is legal and practical. i imagine that when you compiled prior versions of the Gimp you failed to notice that you already had libraries/headers et al required to compile. an easy mistake. as long as i can remember the Gimp has been dependent on external libraries for compilation. there are very few applications that aren't. it would be great to be able to ship all the sources required to compile but frankly that would produce a very large tarball; each time you download the sources you'd be downloading these extra libraries all over again. that would be boring. there are a number of other complications/inefficiences involved also. one that comes to mind are the difficulties produced by duplicate libraries. for instance, imagine having a libjpeg installation from your distribution (/usr/lib) *and* another from our hypothetical Gimp source tarball (/usr/local/lib). of course you could throw all the sources of dependencies (if legal) into this tarball, compile and install them to a non-system wide location, and then link against them. this would produce what is known as a statically linked binary. Apple users are used to this, but they are also used to having duplicate libs scattered all over the system; static linking is esp common in their ~/Applications directory - very messy. as a Linux user however, this would drive me bonkers.. Julian -- __ _ ___ ___| |___ __| |_ _ __ __ _ _ _| |__ ___ (_-/ -_) / -_) _| _| '_ \/ _` | '_| / /(_- /__/\___|_\___\__|\__| .__/\__,_|_| |_\_\/__/ |_http://selectparks.net/~julian ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Problems compiling GIMP
On Fri, Feb 10, 2006 at 02:27:42PM -0500, Scott wrote: gimp-composite-sse.c: In function 'gimp_composite_scale_rgba8_rgba8_rgba8_sse': gimp-composite-sse.c:786: error: PIC register '%ebx' clobbered in 'asm' make[3]: *** [libcompositesse_a-gimp-composite-sse.o] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 - I then can seem to run a make install, but there is no gimp executable. Only gimp-remote seems to get installed. Can someone perhaps lead me in the right direction with this? recently there was the same problem with mmx. if you run ./configure --help it will tell you how to build without this sse stuff. these are some optimizations that were included by some guy from Sun and seem to be unmaintained lately. I ran it with --disable-mmx, now ld does not support the -rpath switch on OS X. And there does not seem to be an option to disable it in the configure, at least that I found . if you are using apple products, you probably are not interested in speed so probably building without that stuff will not seem to hurt performance. I use to think that, I am an avid Linux and Solaris user. But, OS X is much further along in regards of ease of use and application support for my family members. This allows me to insure there will never be any microsoft products in my house. :-) But this Imac is the 2.0 DC w/1gb of RAM. Under normal usage it runs nicely, it does seem to stumble sooner under high load then my Sun Ultra 20 (opteron) does. But, generally speaking it is a good performer.. Thanks for all your help.. Scott ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Problems compiling GIMP
Am 11.02.2006 um 05:43 schrieb Scott: recently there was the same problem with mmx. if you run ./configure --help it will tell you how to build without this sse stuff. these are some optimizations that were included by some guy from Sun and seem to be unmaintained lately. I ran it with --disable-mmx, now ld does not support the -rpath switch on OS X. And there does not seem to be an option to disable it in the configure, at least that I found . Thats the one I got on PPC since 2.3.6! Folks at IRC told me that this would be an issue outside of GIMP, so I gave up for a while :( But this Imac is the 2.0 DC w/1gb of RAM. Under normal usage it runs nicely, it does seem to stumble sooner under high load then my Sun Ultra 20 (opteron) does. But, generally speaking it is a good performer.. sounds like outperfoming my iBook 800 will be an easy job for the MacBook Pro :) Thanks for all your help.. Scott Greetings, lexA ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user --- Live is like a chocolate box, you never know what you wanna get... GPG Signatur auf http://wernicke-online.net/Impressum/ prüfen PGP.sig Description: Signierter Teil der Nachricht ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Default settings for scaling images: high quality?
Am Freitag, 10. Februar 2006 20:13 schrieben Sie: FilePreferencesTool options thank you, this works ;) is there a way to use this setting system wide (all users)? any hints on how to associate gimp for a specific file type (suffix) likewise system wide (mimetypes for KDE 3.3), BTW? cheers Ralf ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
