A couple of things to note here, depending on how your system is installed: If you have compiled some libraries from source and installed them in the standard configure locations (/usr/local), then you will need to modify your PKG_CONFIG_PATH variable. Red Hat puts everything in /usr, and the default pkg-config directory is in /usr/share/pkgconfig. Installing from source will normally create a /usr/local/lib/pkgconfig directory. Before running configure, do the following from a bash shell: export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:/usr/share/pkgconfig ./configure should then find all of the appropriately configured libraries. The other thing that Red Hat does is separate a development package from a running package. In particular the include files are going to be missing. You'll need to use yum / apt-get / rpm to install the development packages (normally <pkg-name>-devel) in order to actually build the software. That said, the official libcroco packages are too old (0.4.0 as opposed to the required >= 0.5.0). Attempting to remove the current version of libcroco and libcroco-devel creates a raft of dependency issues. I suppose one could do a ./configure --prefix=/usr for the latest version of libcroco (0.5.1) and install on top of the current version. Another way to approach this would be to build both a libcroco and libcroco-devel rpm with the 0.5.1 source code. Before modifying libcroco and libcroco-devel, you should check to see what changed between 0.4.0 and 0.5.1 so that you don't break other packages. This is not the clearest of paths . . . sorry I wasn't more helpful. /mde/ just my two cents . . . .
