Quote:

Original post by PrincessDaisy The outputs talk about PKG_CONFIG_PATH, and changing tit so pkg_config can find the libraries... How do I do that? And will that solve my problems? I knew Linux wouldnt be as easy to set up as other OS's, but to be honest, if this problem isn't my doing, then its crazy. Am i going to have to go though steps like these when I install anything... I'd like to program on Linux, not have to fix it every 5 seconds. Anyway, any help would be appreciated :) Thanks Daisy

I can tell you just what's up with the PKG_CONFIG_PATH, and give you a little info about what's going on and why.

1) pkgconfig defaults to only looking at the information in /usr/lib/pkgconfig, and not in /usr/local/lib/pkgconfig.

2) doing a ./configure && make && make install for your standard auto-tooled software package (like anjuta, atk or any of the like) will install to /usr/local -- if you want them installed in /usr you can just add "--prefix=/usr" as a command line option to configure.

3) Alternately, you can run the configure script in the by setting the environment variable in the path, like
PKG_CONFIG_PATH=/usr/local/lib/pkgconfig ./configure && make && make install

4) If you are installing the prerequisite packages for anjuta via RPM (and bear with me -- I could be wrong, I don't use an RPM-based distribution) you may need to install the developer versions of those packages -- If you didn't install them initially when you set up Mandrake, they should be on the CD -- if you don't have that handy, look for them on freshrpms or from the Mandrake website.

Hope some of this is useful -- I started mucking around with Linux years ago just to have a full development toolchain -- and it took me a while to get used to everything, but the experience has been very rewarding. Good luck getting everything set up.

KB