I apologize if this is in a previous thread - I spent hte last 2 hours searching and none of the posts I found have gotten me any farther (as I've tried most of them sans creating symlinks which I don't think I shoul dhave to do, because I've never done it in past distros of Redhat..)

Basic configuration:

IBM Laptop P4 2.0ghz
Fedora Core 3 install with latest updates

I have extracted Glib 2.6.1 in /usr/local/src/glib-2.6.1 and ran ./configure/make/make install. When I extract GTK+-2.6.1 in /usr/local/src/gtk+-2.6.1, and then run ./configure in a terminal as root, it complains of the following:

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

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

What is the deal? I'm assuming that when I run "make install" that it is copying the libraries into the proper folders - either like /usr /lib or /use/local/lib, or both. I don't ever remember having to do this with redhat 7 or 8 (which is the last time I used linux, kernel 2.4.18 or .20 or something like that). What has changed? Has my crack supply dwindled in quality or is there something basic I am missing? I don't remember having to create symlinks to accomplish any of this stuff.... nor do I know if that wille ven work.

any help is greatly appreciated! help me keep linux on my laptop! :-)

Ok, do these commands for me. ldconfig must be done as root; everything else as the useryou're trying to compile with:

[root@bluebird /]# ldconfig -v | grep glib
libglib-2.0.so.0 -> libglib-2.0.so.0.600.1
/usr/local/src/glib-2.6.1:
libglib-1.2.so.0 -> libglib-1.2.so.0.0.10
libglib-2.0.so.0 -> libglib-2.0.so.0.400.8
libdbus-glib-1.so.0 -> libdbus-glib-1.so.0.0.0
libgw-glib.so.0 -> libgw-glib.so.0.0.0
libgwrap-glib.so.1 -> libgwrap-glib.so.1.0.0

>>

[root@bluebird /]# find / -name "glib-2.0.pc" -o -name "glib2-config" 2>/dev/null
/usr/local/src/glib-2.6.1/glib-2.0.pc
/usr/local/lib/pkgconfig/glib-2.0.pc

>>

[root@bluebird /]# echo $pkg_config_path

[root@bluebird /]# echo $PKG_CONFIG_PATH

[root@bluebird /]# echo $PATH
/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/root/bin

>>

Thanks in advance!

Alright, give this a try for me now:
After doing that, try to run the configure script for GTK-2 again. If it works, we'll need to make the change permanent.

=========================================================

Explanation of previous commands (if anyone is curious):

Ok, the ldconfig command says that glib2 is installed, and the compiler can find it to link against.

The find command made sure the glib-2.0.pc file exists somewhere other than the source tree (i.e. it's been installed) However, I was hoping for a file named "glib2-config" as well; might just have the name wrong on that one. Essentially, both have the same information: where the headers were installed, and what command line options the compiler needs to include to use the code with other software.

Echo'ing $PKG_CONFIG_PATH is just checking to make sure the pkg-config command is checking all the necessary places to find *.pc files.

Echo'ing $PATH was similarly checking to make sure the glib2-config was in the user's path. Again, perhaps it named something else, or perhaps glib2 doesn't include it.

You need:

export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig

Also, your ldconfig command is outputing the line:
/usr/local/src/glib-2.6.1:

I can't see the context around that line because the grep did not catch it, but /usr/local/src is the directory containing the source build tree, not the location where the where glib is installed. Did you redirect this with a "--prefix=" when configuring glib? This would also explain why the glib-2.0.pc file was not where it was expected.

echo $PKG_CONFIG_PATH now states that the path is /usr/local/lib/pkgconfig, but when I run ./configure in gtk+-2.6.1, it's still coming up with the same error.

DUR
>>
checking for glib-2.0 >= 2.6.0 atk >= 1.0.1 pango >= 1.7.0... 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.6.0 atk >= 1.0.1 pango >= 1.7.0) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them.

>>

OK, you gave me some great help, but I was blind as a bat. I'm going to download the latest ATK and install that, then post back my results.

The -v option to ldconfig will print the directory the library was found in as a "header" so to speak. I imagine ldconfig output the line "/usr/local/src/glib-2.6.1:" because that directory was added to ld.so.conf. I have a feeling sfunk1x tried adding that to solve his problem initially.

Everything looks ok to me. It's just that glib2 was installed to a tree other than where pkg-config was installed. Otherwise, the default path pkg-config searches would have picked up the glib-2.0.pc file.

So yeah, you'll need to download and install ATK and all the other goodies the configure script lists that you don't have. Also, remember to run ldconfig after you install a library (at least, before you compile something that wants to link against it).

OK...

>>
checking for glib-2.0 >= 2.6.0 atk >= 1.0.1 pango >= 1.7.0... 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.6.0 atk >= 1.0.1 pango >= 1.7.0) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them.
[root@bluebird gtk+-2.6.1]# rpm -qa atk
atk-1.8.0-2_1.rhfc3.at



>>

The wierd thing is.. this is a standard, alomost full install of Fedora Core 3. When I perform an rpm-qa atk these are the results:

[root@bluebird gtk+-2.6.1]# rpm -qa atk
atk-1.8.0-2_1.rhfc3.at

>>

Yet, I am still getting the error message above. When I built Glib 2.6.1, I did not add the prefix line, as I didn't understand that I needed it. I tried the man page but I still wasn't clear after reading it. Should I rebuild glib and add the prefix flag so it adds the .pc file?

Also, why, after using an RPM to install the latest ATK (which FC3 already had I believe), would it not find the pc file for atk? I'd think that woul dbe a nobrainer considering there was practically no use rinteraction during the install. What am I missing here?

thanks for the noob help!

Here's the deal. In the "wisdom" of package maintainers, support software is split into two pieces: the "normal" package and a "devel" package.

The assumption is, if you're using a package manager, you're not actually going to compile anything by hand; you'll just use the package manager to install whatever you need. In doing so, you're trusting someone else to do the compiling for you. Well, there are files used in compilation that are not needed after the compilation is finished. Those files get stripped out of the "normal" packages in an effort to save space. Again, you're using a package manager, and won't need to compile anything yourself.

Those orphaned files get shoved into the "devel" package. So, if you plan to do any compiling of software that uses a library (such at ATK), then you need to install the development package. They should be on your install CDs or downloadable from the same place you got the normal package from. Typically, they just have "-devel" sandwiched in the file name. Once installed, then you can compile against it.

I'm not a big fan of this strategy, but that's the way it is. So go hunt down the devel package and install it, and you should be ok.

OK. Awesome. I'm going to take care of the ATk dev install in a moment.

So, how do I go about making that path permenant, so future packages won't complain about glib?

Open up /etc/profile (you'll need to be root to edit it). Scroll down to the bottom of the file, and add the export command exactly like mentioned before. Save the file and exit.

The next time you log in, you can double-check it's there by doing the echo $PKG_CONFIG_PATH thing.

Keep in mind, that if you open a new terminal in your current session, it's not the same thing as logging in. That's just a side effect of how X works. You'll have to completely log out, and if you're not sure what I mean by that, then a reboot will take care of it.

Thanks to everyone who replied! Everything has been installed, and now I can isntall the packages that I wanted to install.

Thanks for the assistance. Now to move onto other projects.. :-)

This is a different message. You fixed glib, not it needs the same fix for atk. pango comes next. I think pango is the last of the madness, but I am not sure. I was building gimp-2.2.2 and needed more yet. If you are putting everything in /usr/local, all of the ".pc" files should end up there and be found. If you change the "--prefix=" to somewhere else, like "--prefix=/my/new/path", add "/my/new/path/lib/pkgconfig" to PKG_CONFIG_PATH.

Fedora Core 3 does not have the glib version that gtk+2.6.1 needs. If you look at /usr/lib/pkgconfig
and open the glib-2.0.pc file it states that the glib version is "Version: 2.4.7". gtk+2.6.1 needs glib-2.6.0
or greater. You'll need to upgrade the glib, atk, and pango libraries first before ./configure for the gtk+-2.61
stop complaining about those.

Oops! I only got to see the full thread of your post after send my post. Seems you got it lick already.