Re: [Gimp-developer] dependancies (used to be xinput)
On Thu, 2002-06-06 at 20:17, Philip Brown wrote: > Fair enough. But that being the case, please fix the configure script so > that when "pangoft2" is not found, it prints out a more useful message Instead of writing these lines (and your other mails), why don't you submit a patch? I am pretty sure that people will welcome your contribution. Lutz -- +--+ | Lutz Müller +49 (7156) 34837 | | | | Hans-Sachs-Strasse 5 | | 71254 Ditzingen http://www.topfrose.de | | Germany [EMAIL PROTECTED] | +--+ ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] dependancies (used to be xinput)
On Thu, Jun 06, 2002 at 11:21:19AM +0200, Sven Neumann wrote: > Philip Brown <[EMAIL PROTECTED]> writes: > > > My problems hit because of 'pangoft2', which is required by gtk1.3.7, > > but is NOT INSTALLED by pango1.0.2, the latest version of pango. > > and there is the file INSTALL which you should have read: > > 3. We require PangoFT2, a Pango backend that uses FreeType2. Make > sure you have FreeType2 installed before you compile Pango. Fair enough. But that being the case, please fix the configure script so that when "pangoft2" is not found, it prints out a more useful message like, "we require pango, with the optional freetype2 library support compiled in. " > BTW. Sun's make is really akward and I don't see why you are putting > extra pain on you and other people by refusing to install GNU > make. really awkward? almost nothing in your entire build scheme uses any GNU make 'features'. The same with all the other libraries' makefiles. There is no overriding reason for you to use GNUmake specific features, and since standard makefiles work with both sun make, and GNU make, it makes sense to stick to the plainer standard. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] dependancies (used to be xinput)
Hi, Philip Brown <[EMAIL PROTECTED]> writes: > My problems hit because of 'pangoft2', which is required by gtk1.3.7, > but is NOT INSTALLED by pango1.0.2, the latest version of pango. and there is the file INSTALL which you should have read: 3. We require PangoFT2, a Pango backend that uses FreeType2. Make sure you have FreeType2 installed before you compile Pango. if you had freetype2 installed, PangoFT2 would probably have been built and installed. > Here's a fuller list of all the issues I have compiling the various > dependancies under solaris, for the curious: no, we don't want and can't care about your problems compiling glib. You should file a bug-report against glib instead. BTW. Sun's make is really akward and I don't see why you are putting extra pain on you and other people by refusing to install GNU make. It's a well known fact that a whole bunch of GNU software requires GNU make and that it definitely makes your life easier to install and use it. > pkg-config when called from other libraries' configure scripts, > keeps whining about 'sh: gnome-config: not found' > eg: > > checking for libpng12... sh: gnome-config: not found this is a stupid problem with pkg-config that tries some hardcoded fallbacks if it can't find the .pc file it should look for. I don't like this fact either but Havoc seems to think that it is a good idea. > gtk+-2.0.3 README claims that png, jpg, and tiff libraries are optional. they are required but you may choose to switch this requirement off and build without them. You will end up with an image manipulation program that doesn't support the most important image formats. > However, in gtk+-2.0.3/gdk-pixbuf GTK+ depends on png, jpg, and tiff just as GIMP depends on them. This is a good choice since application developers can then be sure that the functionality to load these image file formats is available. You should only switch these dependencies off (by using the --without-foo configure options) if you are building GTK+ for a special target like an embedded device where you know exactly what software will be using GTK+ later. > And finally, the killer, while trying to configure gimp 1.3.7: > > checking for GTK+ - version >= 2.0.0... yes (version 2.0.3) > checking for pangoft2 >= 1.0.0... sh: gnome-config: not found > sh: gnome-config: not found > Package pangoft2 was not found in the pkg-config search path. > Perhaps you should add the directory containing `pangoft2.pc' > to the PKG_CONFIG_PATH environment variable > No package 'pangoft2' found > > And before you say I should set my PKG_CONFIG_PATH... > 'pangoft2' **was** **not** **installed** by pango1.0.2, even when > I used gmake to compile and install, from scratch. > > $ find /usr/local -name 'pangoft*' -print > > returns nothing. I will end this mail with the statement I started it with: and there is the file INSTALL which you should have read: 3. We require PangoFT2, a Pango backend that uses FreeType2. Make sure you have FreeType2 installed before you compile Pango. if you had freetype2 installed, PangoFT2 would probably have been built and installed. Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] dependancies (used to be xinput)
Hi, Philip Brown <[EMAIL PROTECTED]> writes: > seems that the latest version of pkgconfig is not compatible with the > latest version of pango. this is complete nonsense. Please don't say this kind of stuff on public mailing-lists. > Which is a really good reason to not do this sort of nonsense. > Just use autoconfig like always, instead of this silly pkgconfig. > It's too redhat, for a software tool that's supposed to be cross-UNIX > compatible. you obviously didn't understand what pkg-config does since it does a completely different thing than autoconf and in no way intents to replace it. Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] dependancies (used to be xinput)
On Wed, Jun 05, 2002 at 04:05:18PM -0700, Philip Brown wrote: > And finally, the killer, while trying to configure gimp 1.3.7: > ... > Package pangoft2 was not found in the pkg-config search path. > ... > $ find /usr/local -name 'pangoft*' -print > > returns nothing. BTW: I went back and did a configure ; gmake; gmake install for pango 1.0.0 that did not install pangoft2* anywhere either, although i certainly see pango-1.0.0/pango/pangoft2.h sitting in the source directories. same with pango-1.0.2/pango/pangoft2.h ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] dependancies (used to be xinput)
On Wed, Jun 05, 2002 at 11:35:25PM +0200, Christian Rose wrote: > ons 2002-06-05 klockan 23.28 skrev Philip Brown: > > seems that the latest version of pkgconfig is not compatible with the > > latest version of pango. > > Which is a really good reason to not do this sort of nonsense. > > Just use autoconfig like always, instead of this silly pkgconfig. > > It's too redhat, for a software tool that's supposed to be cross-UNIX > > compatible. > > Good conspiracy theory or troll, but the problem is that fontconfig has > nothing to do with pkgconfig, so that puts your little offtopic rant at > shame. Actually, fontconfig has nothing to do with the issues *I* had compiling (as far as I know). That was the original poster's problem. My problems hit because of 'pangoft2', which is required by gtk1.3.7, but is NOT INSTALLED by pango1.0.2, the latest version of pango. Here's a fuller list of all the issues I have compiling the various dependancies under solaris, for the curious: == glib2.0 fails with non-GNU make: ... Making all in docs Making all in reference Making all in glib make: Fatal error: Don't know how to make target `all-local' Current working directory /home/phil/build/glib-2.0.3/docs/reference/glib GNU make is 'recommended', but not stated as required. The really stupid thing is, its a bogus dependancy. Doing gmake at that point, doesnt seem to actually compile anything extra. Similar problem with atk 1.0.2. however, GNU make is not mentioned at all, "recommended" or otherwise make: Fatal error: Don't know how to make target `all-local' Current working directory /home/phil/build/atk-1.0.2/docs pango suffers from similar GNU-make-itis pkg-config when called from other libraries' configure scripts, keeps whining about 'sh: gnome-config: not found' eg: checking for libpng12... sh: gnome-config: not found gtk+-2.0.3 README claims that png, jpg, and tiff libraries are optional. However, in gtk+-2.0.3/gdk-pixbuf /usr/ccs/bin/ld -G -h libpixbufloader-png.so -o .libs/libpixbufloader-png.so io-png.lo -R/home/phil/build/gtk+-2.0.3/gdk-pixbuf/.libs -R/directio/lib -R/directio/lib -L/directio/lib -lpng -lz ./.libs/libgdk_pixbuf-2.0.so /directio/lib/libgmodule-2.0.so -ldl /directio/lib/libgobject-2.0.so /directio/lib/libglib-2.0.so -lm -lc ld: fatal: library -lpng: not found ld: fatal: File processing errors. No output written to .libs/libpixbufloader-png.so Similarly for -ljpeg, once I get over the png error. Similarly for -ltiff, once I get over the jpeg error. In gtk/stock-icons, failed to load "./stock_add_16.png": Failed to load image './stock_add_16.png': Fatal error in PNG image file: Incompatible libpng version in application and library *** Error code 1 [This was with libpng1.2; downgraded to 1.0.2, and reconfigured... ] Hit another GNU-make-ism in docs/reference/gdk-pixbuf Making all in gdk-pixbuf make: Fatal error: Don't know how to make target `all-local' Current working directory /home/phil/build/gtk+-2.0.3/docs/reference/gdk-pixbuf *** Error code 1 And finally, the killer, while trying to configure gimp 1.3.7: checking for GTK+ - version >= 2.0.0... yes (version 2.0.3) checking for pangoft2 >= 1.0.0... sh: gnome-config: not found sh: gnome-config: not found Package pangoft2 was not found in the pkg-config search path. Perhaps you should add the directory containing `pangoft2.pc' to the PKG_CONFIG_PATH environment variable No package 'pangoft2' found And before you say I should set my PKG_CONFIG_PATH... 'pangoft2' **was** **not** **installed** by pango1.0.2, even when I used gmake to compile and install, from scratch. $ find /usr/local -name 'pangoft*' -print returns nothing. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] dependancies (used to be xinput)
ons 2002-06-05 klockan 23.28 skrev Philip Brown: > > This is as good a point to ask as any; in following the > > latest incarnation of the crazy dep-chain I ran into a > > dead-end finding the mysterious 'fontconfig' (fontconfig > > is needed by pango is needed by gtk2 is needed by gimp). > > Anyone know where I can find such a thing? I thought > > that it sounded like it was probably part of pkgconfig > > (pkgconfig is needed by... etc) but it doesn't seem to > > be. > > seems that the latest version of pkgconfig is not compatible with the > latest version of pango. > Which is a really good reason to not do this sort of nonsense. > Just use autoconfig like always, instead of this silly pkgconfig. > It's too redhat, for a software tool that's supposed to be cross-UNIX > compatible. Good conspiracy theory or troll, but the problem is that fontconfig has nothing to do with pkgconfig, so that puts your little offtopic rant at shame. fontconfig is designed by Keith Packard of XFree86 fame. There's a fontconfig tarball at http://keithp.com/~keithp/download/. Haven't tried it though. Christian ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] dependancies (used to be xinput)
On Wed, Jun 05, 2002 at 09:37:41PM +0100, Adam D. Moss wrote: > ... > This is as good a point to ask as any; in following the > latest incarnation of the crazy dep-chain I ran into a > dead-end finding the mysterious 'fontconfig' (fontconfig > is needed by pango is needed by gtk2 is needed by gimp). > Anyone know where I can find such a thing? I thought > that it sounded like it was probably part of pkgconfig > (pkgconfig is needed by... etc) but it doesn't seem to > be. seems that the latest version of pkgconfig is not compatible with the latest version of pango. Which is a really good reason to not do this sort of nonsense. Just use autoconfig like always, instead of this silly pkgconfig. It's too redhat, for a software tool that's supposed to be cross-UNIX compatible. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
