SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I'm installing gtk+-2.8.12 from source, and it barks at me, for the following reason:
checking whether make sets $(MAKE)... (cached) yes
checking for pkg-config... /usr/local/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for BASE_DEPENDENCIES... configure: error: Package requirements (glib-2.0 >= 2.8.5 atk >= 1.0.1 pango >= 1.9.0 cairo >= 0.9.2) were not met.
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Configure claims that I don't have glib, atk, pango or cairo, but I downloaded those, built and installed them! I tried changing my PKG_CONFIG_PATH variable to /usr/lib/pkgconfig/ and /usr/local/lib/pkgconfig/ but with no luck. Same error. I've tried to install gtk+ a number of times, and always gotten frustrated cause I keep running into this. I feel like it's a simple problem, I just can't get my head around it. Anyone out there have any advice?
If you built the dependencies (glib2, atk, cairo, pango is the correct order) using the ./configure without any options, then they are all installed under /usr/local/lib. So before running ./configure for gtk, run:
As you see there are 2 different directories whith the libfreetype library that the compiler uses. I suggest you to move the old freetype libraries (from /usr/lib to another dir), run "ldconfig" and re-run the ./configure script for pango.
Well now after two days of trying to fullfil Basic depenedances it succeeded with
checking for BASE_DEPENDENCIES... yes
and went further finally stoping at:
checking Pango flags... -I/usr/local/include/pango-1.0 -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/cairo -L/usr/local/lib -lpangocairo-1.0 -lpango-1.0 -lcairo -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0
*** Can't link to Pango. Pango is required to build
*** GTK+. For more information see pango.org
Isn`t Pango basic dependence? I guess it was found installed before so what`s the problem?
I tried to reinstall Pango over and over with no result... Any suggestions? need help...
Ehh but I`m a Mandriva user... I know this is the wrong section but I think there is some universal and shure way... (wander if U can help) and I don`t think there are any proper SlackBuilds 4 my distro;p
I got the same error... You were right. Its the FreeType library conflicting issue. I removed all the /usr/lib/libfreetype* from the directory (since there were IDENTICAL files in the /usr/local/lib/).
...or, you guys could actually just ask some people familiar with compiling these things.
pkg-config having a search path or not, there's a great number of things that misbehave if you have different prefixes for them. If everything it wanted were in /usr or if everything it wanted were in /usr/local, you'd have been fine. I've seen this enough from people on IRC reporting problems compiling things to not find it surprising.
I'm not saying I'm 100% sure this was what the issue was, but generally when you've got something you know was installed correctly, and PKG_CONFIG_PATH includes it, and it still fails, check that you don't have duplicate and differing versions of a lib installed (I've actually discussed this potential desynch between the path set in PKG_CONFIG_PATH and the search order the linker is likely to use with Pat before, so it's a "known" way to fail) and if you don't, be prepared to rebuild whichever packages are in the oddball prefix to use the same prefix as everything else.
Last edited by evilDagmar; 12-31-2007 at 05:39 AM.
Reason: Added explanation of why/when pkg-config using apps break