GTK+-2.2: errors during ./configure

Here's the errors:

checking for glib-2.0 >= 2.1.4 atk >= 1.0.1 pango >= 1.0.1... Package atk was not found in the pkg-config search path.
Perhaps you should add the directory containing `atk.pc'
to the PKG_CONFIG_PATH environment variable
No package 'atk' found

configure: error: Library requirements (glib-2.0 >= 2.1.4 atk >= 1.0.1 pango >= 1.0.1) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them.

[scruff@localhost gtk+-2.2.0]$ whereis glib-2.0
glib-2: /usr/lib/glib-2.0 /usr/include/glib-2.0 /usr/share/glib-2.0

[scruff@localhost gtk+-2.2.0]$ whereis pango
pango: /etc/pango /usr/lib/pango /usr/local/etc/pango /usr/local/lib/pango

I downloaded and installed atk and pango and I get the same errors.

Searching the net showed I'm not the only one that's had this prob, though I have yet to see a solution. Anyone here get past this install?

Did you have a look at the Gome Installation Guide? This is sort of overkill, I admit, but it got lots of hints and tips and it also covers the installation of pango, atk, and gtk+

Good luck.

Just looked. Nothing specific to my problem. I will keep searching though

<bump>

Did you try:
find / -name atk.pc -print

If you found it
then:
export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:/path

/usr/local/lib/pkgconfig/atk.pc.

I tried PKG_CONFIG_PATH=$PKG_CONFIG_PATH:/usr/local/lib/pkgconfig/atk.pc

Then I got the same errors when ./configure.

Was I correct that ':/path' was to be where I found atk?

I think you should use just
/usr/local/lib/pkgconfig
for the path

And, did you use 'export' like in my post?

It has to work. That's what it says in your error:
"Perhaps you should add the directory containing `atk.pc'
to the PKG_CONFIG_PATH environment variable"

When you have the same error again make sure that it asks for the same file. Sometimes I had to add other paths for some other files during ./configure process.

Also you might want to double check your variable:

echo $PKG_CONFIG_PATH

Wow. Thanks alot It went.

I didn't include 'export' like your post the 1st time. Would you mind explaining to me what it is I just did for future reference?

In a root terminal do "ldconfig". Then try your ./configure again.

I am not sure if I can really explain that.

I found it somewhere on 'man' pages (I don't remember where anymore). It explained what the '.pc' files mean.

But anyway, when some program/command can't find something it's because the 'search path' is not specified. In this case it was PKG_CONFIG_PATH. So you had to set the search path using this variable.

You can set the path permanently in your .bash_profile by adding a line 'export blah_blah_whatever_you_need'

Also, there is another variable LD_LIBRARY_PATH that you have to setup when your compiler complains that it can't find some library. (I had this problem after I installed 'gtkmm')

a pc (pkgconfig) file gives information about where to look to heards and libraries for dependent packages.

You are aware that you can just installl this all by RPM i hope.... A normal user would need a very good reason to want to be compiling all this from source, especially on a distro like redhat where the RPM database is so integrated into the way the system runs at the highest levels.

I am compiling everything from source to learn more. I was building up to recompiling my kernel, which I did successfully last night

Actually, the recompiling the kernel was 10x easier than getting that damn lib installed.