Stupidest piece of software on the planet: GTK+

versaulis · 11-07-2008, 02:38 PM

If it's not complaining about my glib version not being up to date enough (even though I'm running the latest version), it constantly complains about Pango. I have the latest versions of everything installed. I've installed Cairo, Xft, X, and Pango. Pango claims that is has found all of the former backends. The libraries are installed to /usr/lib and the header files are installed to /usr/include. Everything is in it's right place.

Can ANYBODY tell me why GTK+ keeps chasing it's tail??? There are a million and one people talking about how GTK+ can't find anything, won't compile, and so on. I've been Googleing for hours, but none of them seem to fit my situation. Some people had old Pango installs lingering, and other such problems.

*Edit*
My solution to this problem was to install GTK-1 before GTK-2 and it's dependencies. There seems to be no problems if pango and so on are not in the system yet.
*Edit*

Code:

root:/sources3/gtk+-1.3.15# ./configure --prefix=/usr --sysconfdir=/etc 2>&1 | tee -a /logs/gtk+1-config.log
checking for a BSD compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... missing
checking for working autoconf... found
checking for working automake... missing
checking for working autoheader... missing
checking for working makeinfo... found
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for executable suffix...
checking for object suffix... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependant libraries... pass_all
checking command to parse /usr/bin/nm -B output... ok
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for ranlib... ranlib
checking for strip... strip
checking for objdir... .libs
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.lo... no
checking if gcc supports -fno-rtti -fno-exceptions... yes
checking whether the linker (/usr/bin/ld) supports shared libraries... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking if libtool supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
creating libtool
checking whether to enable maintainer-specific portions of Makefiles... no
checking for some Win32 platform... no
checking for native Win32... no
checking whether build environment is sane... yes
checking for strerror in -lcposix... no
checking for gcc option to accept ANSI C... none needed
checking for a BSD compatible install... /usr/bin/install -c
checking whether make sets ${MAKE}... (cached) yes
checking for pkg-config... /usr/bin/pkg-config
checking for glib-2.0 >= 1.3.15 atk >= 0.13 pango >= 0.26... yes
checking BASE_DEPENDENCIES_CFLAGS... -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/atk-1.0 -I/usr/include/pango-1.0
checking BASE_DEPENDENCIES_LIBS... -latk-1.0 -lpango-1.0 -lm -lgobject-2.0 -lgmodule-2.0 -lglib-2.0
checking for gawk... gawk
checking for perl5... no
checking for perl... perl
checking for indent... no
checking for lstat... yes
checking for mkstemp... yes
checking for bind_textdomain_codeset... yes
checking for sigsetjmp... yes
checking whether make is GNU Make... yes
checking for ranlib... (cached) ranlib
checking for gcc option to accept ANSI C... none needed
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking for off_t... yes
checking for size_t... yes
checking for working alloca.h... yes
checking for alloca... yes
checking for stdlib.h... (cached) yes
checking for unistd.h... (cached) yes
checking for getpagesize... yes
checking for working mmap... yes
checking argz.h usability... yes
checking argz.h presence... yes
checking for argz.h... yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking nl_types.h usability... yes
checking nl_types.h presence... yes
checking for nl_types.h... yes
checking malloc.h usability... yes
checking malloc.h presence... yes
checking for malloc.h... yes
checking for string.h... (cached) yes
checking for unistd.h... (cached) yes
checking sys/param.h usability... yes
checking sys/param.h presence... yes
checking for sys/param.h... yes
checking for getcwd... yes
checking for munmap... yes
checking for putenv... yes
checking for setenv... yes
checking for setlocale... yes
checking for strchr... yes
checking for strcasecmp... yes
checking for strdup... yes
checking for __argz_count... yes
checking for __argz_stringify... yes
checking for __argz_next... yes
checking for LC_MESSAGES... yes
checking libintl.h usability... yes
checking libintl.h presence... yes
checking for libintl.h... yes
checking for dgettext in libc... yes
checking for msgfmt... /usr/bin/msgfmt
checking for dcgettext... yes
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for catalogs to be installed... az ca cs cy da de el en_GB en@IPA es et eu fa fi fr ga gl he hr hu ia it ja ko lt ms nl nn no pl pt pt_BR ro ru sk sl sp sr sv tr uk vi wa zh_TW zh_CN
checking for extra flags to get ANSI library prototypes... none needed
checking for the BeOS... no
checking for extra flags for POSIX compliance... none needed
checking for pkg-config... (cached) /usr/bin/pkg-config
checking for GLIB - version >= 1.3.15... yes (version 2.19.0)
checking pwd.h usability... yes
checking pwd.h presence... yes
checking for pwd.h... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking for unistd.h... (cached) yes
checking winsock.h usability... no
checking winsock.h presence... no
checking for winsock.h... no
checking for ANSI C header files... (cached) yes
checking for an ANSI C-conforming const... (cached) yes
checking return type of signal handlers... void
checking for stdlib.h... (cached) yes
checking for unistd.h... (cached) yes
checking for getpagesize... (cached) yes
checking for working mmap... (cached) yes
checking for getresuid... yes
checking for uid_t in sys/types.h... yes
checking for fd_set... yes, found in sys/types.h
checking for wchar.h... yes
checking for wctype.h... yes
checking for iswalnum... yes
checking if iswalnum() and friends are properly defined... yes
checking whether to build gmodulized gdk-pixbuf... yes
checking whether dynamic modules work... yes
checking for TIFFReadScanline in -ltiff... yes
checking tiffio.h usability... yes
checking tiffio.h presence... yes
checking for tiffio.h... yes
checking for jpeg_destroy_decompress in -ljpeg... yes
checking for jpeglib.h... yes
checking for jpeg_simple_progression in -ljpeg... yes
checking for png_read_info in -lpng... yes
checking png.h usability... yes
checking png.h presence... yes
checking for png.h... yes
checking for png_structp in png.h... yes
checking pixbuf loaders to build...
checking for sys/wait.h that is POSIX.1 compatible... yes
checking return type of signal handlers... (cached) void
checking for x86 platform... yes
checking compiler support for MMX... yes
checking for XOpenDisplay in -lX11... yes
checking for XShmAttach in -lXext... yes
checking for XShapeCombineMask in -lXext... yes
checking for XConvertCase in -lX11... yes
checking for XUnregisterIMInstantiateCallback in -lX11... yes
checking for XkbQueryExtension in -lX11... yes
checking sys/ipc.h usability... yes
checking sys/ipc.h presence... yes
checking for sys/ipc.h... yes
checking sys/shm.h usability... yes
checking sys/shm.h presence... yes
checking for sys/shm.h... yes
checking X11/extensions/XShm.h... yes
checking Pango flags... -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/freetype2 -lpangox-1.0 -lpangoxft-1.0 -lpangoft2-1.0 -lXft -lpango-1.0 -lm -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -lXrender -lfontconfig -lfreetype -lz -lX11
checking for pango_context_new in -lpango... no
configure: error:
*** Can't link to Pango. Pango is required to build
*** GTK+. For more information see http://www.pango.org
root:/sources3/gtk+-1.3.15#

colucix · 11-08-2008, 06:57 AM

Is there some more information in config.log?

bathory · 11-08-2008, 09:17 AM

Quote:

root:/sources3/gtk+-1.3.15# ./configure --prefix=/usr --sysconfdir=/etc 2>&1 | tee -a /logs/gtk+1-config.log

From your prompt above, I see that you're trying to compile gtk+-1.3.15, that is quite old software (released on 2002). I guess that's why it cannot compile against the latest glib and pango. Why don't you use the latest gtk+ version (gtk+-2.14.4).

Quakeboy02 · 11-08-2008, 11:07 AM

What distro are you using that doesn't have up-to-date versions of stuff like gtk available in a repo?

Su-Shee · 11-09-2008, 02:34 PM

Seems like a Pango version mismatch to me - or maybe your pango.pc is missing or in the wrong place (should be in /usr/lib/pkgconfig/ if your Pango stuff is in /usr/lib) or broken.

Check the pkgconfig path and call pkg-config by hand to see what's actually happening.

And make sure that gtk 1.3.x is really what you would like to compile with a recent Pango. I'm not even sure if this works.

i92guboj · 11-09-2008, 05:44 PM

I also think that your problem is simply finding the correct versions for everything.

The simple fact that your pango seems to be configured with glib2 is enough to make me think that it's impossible for it to be compatible with gtk+1. I would try installing any version of pango previous to 1.0.

But as the others say: why do you really need gtk+1 nowadays?

versaulis · 11-12-2008, 09:44 AM

Because they're installing it with Linux From Scratch. I suppose my trust is misplaced in this case. I just assumed that there are programs out there that still require the GTK+1 since it's in the LFS builds.

lumak · 11-12-2008, 11:46 AM

gtk as well as other gnome libraries are as touchy as the tool chain. You just can't randomly start upgrading pieces or use the latest version of ALL of them. I would suggest not updating anything unless your distribution updates them.

i92guboj · 11-13-2008, 02:40 AM

I would just forget about gtk1 unless you have a specific need. I don't know how LFS does these days, but I can't think of any gtk program that I'd run on an actual machine unless you are an xmmd addict.

About updating gtk, it shouldn't pose any problem as long as you keep the stuff that depends on it up to date as well. If you recompile gtk and there's an ABI breakage you need to recompile anything that depends on gtk+ as well. But the gtk stuff rarely breaks. It's stable enough. However, that's another story and a very different one. The problem in this thread is that gtk 1.x can't find pango, and most likely, that's because it needs a concrete version of pango, and not the latest one that you might have installed.

ErV · 11-13-2008, 03:58 AM

Quote:

Originally Posted by versaulis

If it's not complaining about my glib version not being up to date enough (even though I'm running the latest version), it constantly complains about Pango.

YOu are too impatient. gtk-1 is old, and instead of complaining, think of the ways to solve problems. Gtk is picky on the build order of the libraries, and I think that function being checked in pango might not exist in newer versions.

versaulis · 11-13-2008, 10:59 AM

Quote:

Originally Posted by ErV

YOu are too impatient. gtk-1 is old, and instead of complaining, think of the ways to solve problems. Gtk is picky on the build order of the libraries, and I think that function being checked in pango might not exist in newer versions.

You are too ignorant. Not only have I been trying to "think of the ways to solve problems", I've been running a lot of tests as well. Building the GTK is a new experience for me and, as should be obvious to anyone with experience with building linux systems, I have to figure out these details. I cannot just magically know it all. Instead of looking around for people to insult and tear down, add your knowledge to the collective and go away. Nobody needs your personal opinions. The only one complaining is you.

lumak · 11-13-2008, 11:42 AM

Quote:

Originally Posted by versaulis

The only one complaining is you.

LOL. Right. This whole thread started out with a complaint.

ErV · 11-13-2008, 01:05 PM

Quote:

Originally Posted by versaulis

You are too ignorant.

I don't care.

Quote:

Originally Posted by versaulis

Building the GTK is a new experience

It is the same same thing as 95% of all other unix software built using "GNU build tools", aka "autotools" (autoconf + automake + autoheader + m4 + aclocal. Which means ./configure script & stuff). If you built at least one program, it will be same thing.

Quote:

Originally Posted by versaulis

for me and, as should be obvious to anyone with experience with building linux systems, I have to figure out these details.

There is not much to figure out.

Quote:

Originally Posted by versaulis

I cannot just magically know it all.

You can non-magically learn it all during the process of solving this problem. As everyone "experienced" did in in their time.

Quote:

Originally Posted by versaulis

Instead of looking around for people to insult and tear down, add your knowledge to the collective and go away.

./configure is a human-readable bash script, that can be opened with text editor.
It has a test to check if pango is here or not.
The test most likely has C source, which is inlined into configure but it is probably shown into config.log (or was it configure.log?) or there is ldd check or something similar, that also should be visible in logfile, probably with the exact command and maybe even cause of failure. Besides, someone probably already got error message exactly like yours (in same situation, by the way), posted it somewhere on the interenet along with the way to solve the problem. So, why don't you check how exactly ./configure checks for pango presense? Or why don't you search similar error message with google?
Besides, as already suggested, your pango version might not have function that is used in check, and probably needed for gtk 1. In this case the only solution will be finding "correct" version of pango that is probably indicated in software documentation.

Quote:

Originally Posted by versaulis

Nobody needs your personal opinions.

Negative & I don't care.
Besides, you officially asked for opinions by opening thread in public forum.

Quote:

Originally Posted by versaulis

The only one complaining is you.

Negative. See your first post. Or title of this thread.

versaulis · 11-13-2008, 01:54 PM

First of all, you changed my quotes to serve your purposes. I said:

Quote:

Building the GTK is a new experience for me

Installing the GTK may be similar to other packages, but it is the first one that ever gave me this problem.

To say that there is not much to figure out, when the task at hand is building linux software like the GTK, is a statement made from a point of reference. If this is easy for you, great, but it's not easy to everyone - especially beginners. If your answer to that is to beat up on anyone who is trying to learn this, then you're not going to help anyone. You're just a psychopath that's here to tear people down (and I'm not just name calling, look it up).

Quote:

You can non-magically learn it all during the process of solving this problem. As everyone "experienced" did in in their time.

I'm in that process right now, obviously. I do lots of searching on google, whatever documentation I can find, and so on. I try to look at the configure scripts as well, but they are very hard to read for a person who has not tried to figure them out before.

Quote:

Besides, you officially asked for opinions by opening thread in public forum.

That is illogical. The fact that a person has the ability to carry out an action in public does not mean that everyone around the person is asking him to do so. That should be obvious, especially when generalized.

Maybe what you meant to say was that, by opening a thread in public forum, it is inevitable that an opinion will be given. This only true when psychopaths that don't care about their ignorance are on said forum. You're the first one I've met here.

The point is that you showed up with the goal in mind of tearing a person down, instead of just helping out on a website that is designed around helping people understand Linux - most of whom are probably beginners. If you can't function in an environment where people are trying to help each other in this manner, go somewhere else. There are plenty of public forums out there full of people just like you, who can't deal with beginners. That's the place for you. People won't be doing things that you regard as complaining and not trying hard enough. They're more knowledgeable and know where all the resources they need are at and how to use them. Linux is not my area of expertise, but I'm not going to just give up because people like you are trying to tear me down.

ErV · 11-13-2008, 02:22 PM

Quote:

Originally Posted by versaulis

This only true when psychopaths that don't care about their ignorance are on said forum. You're the first one I've met here.

Well, you obviously never met a real trolls or psychopaths on the internet, if you are naming me as one.

Quote:

Originally Posted by versaulis

The point is that you showed up with the goal in mind of tearing a person down,

Unless you are telepathic you don't know what is on the person's mind and what is people's "goal". I still think that calling a library "stupidest piece of..." is strange way to ask for help. Have you read "how to ask questions smart way"?

I've given you several tips about how you can deal with your problem (locate "pango existense test", search for exactly same error message, read docs or downgrade pango), and I'm not interested in the rest. Bye.