DebianThis forum is for the discussion of Debian Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
When I try to install gtk, there is always one problem: first the error: "X development libraries not found" appears. I've found the solution, that I have to use: --x-includes=/... and --x-libraries=/...
then another error appears: *** libX11 not found. Check 'config.log' for more details.
Is this because I chose the wrong path? I tried more then one; and although libx11 is correctly installed, it isn't found... I also tried to find solutions in the inet, but none solved the problem
I don't know about your specific problem, but if your -do- have the library, there is a workaround (sometimes) by using a symlink.
To do this, you need to open the "./configure" file of the package / program you want to compile. Search for the section that does the check that is failing.
For example, I wanted to compile something that was looking for, lets say, libabc.a. I -knew- I had libabc.a, but the package's configure wasn't finding it.
So, I went into the configure script and searched for the section trying to compile a program on libabc.a (to check if it is present in the system). I discovered that the configure script was simply looking in the wrong place (/usr/local/lib instead of /usr/lib, if I remember right).
So the solutions was to put a symlink to /usr/lib/libabc.a into /usr/local/lib, so when the script called cc to compile the test program, and cc went looking for the library in /usr/local/lib, it will find the symlink there to /usr/lib...
So, in effect, you can "trick" the compiler to use a library in a directory that it does not refer to, by putting a symlink to that library in a directory the compiler does refer to.
Eg.
In /usr/local/lib do
ln -s libabc.a /usr/lib/libabc.a
So, if the script is looking in /usr/local/lib for libabc.a (where it does not exist, causing the compile to fail) there will be a symlink which will cause it to -actually- look in /usr/lib, and find the library there.
When I try to install gtk, there is always one problem: first the error: "X development libraries not found" appears. I've found the solution, that I have to use: --x-includes=/... and --x-libraries=/...
then another error appears: *** libX11 not found. Check 'config.log' for more details.
Is this because I chose the wrong path? I tried more then one; and although libx11 is correctly installed, it isn't found... I also tried to find solutions in the inet, but none solved the problem
Thanks in advance
Make sure that you have installed the x-dev package. For the file not found it looks like you need libx11-dev.
You may want to install the apt-file package for future problems like this it works similar to apt-get get in that you must apt-file update as root then can use the search command as normal user.
I've already tried with symlinks, didn't work.... any other ideas?
Mostly what happytux says above - make sure you have everything correctly installed and configured. Other than that, it has sometimes worked for me as well to actually get an -older- version of a library from its distribution site. Sometimes the older version would work, while the current / newest one wouldn't find its dependencies, for example.
If you are feeling adventurous, and the packager (the person putting the application togeteher) included his configure.in and maybe Makefile.am autoconf source files, you might try editing those to find the library correctly - but that is not for the faint of heart.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.