Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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 install some softwares, the dependencies (some .so files) are exactly in those folders, which I've already added to /etc/ld.so.conf. However, no matter how I installed that software, the only way to successfully install it is by using "--nodeps".
I do think that's really too funny......
Anybody who can tell me why it is so? How can I just avoid this conditions without using "--nodeps"? Because I'm used to using APT/SYNAPTIC, which will always consider those softwares which were installed by using "--nodeps" as broken!! Whenever I wanted to update/install some new softwares by APT/SYNAPTIC, I have to remove the broken softwares first, only after that, can I install the new softwares!!!
I often download ".rpm" files including "devel.rpm" and "src.rpm", which will also include all the source files I need. So, normally, I do not need to "./configure" my own software.
I checked "INSTALL" file of "opencv0.9.6", in which there is the following line:
"
--nodeps is needed in this version, because it can not find
libavcodec.so, even if it is in the path (a weird bug somewhere).
"
I just wonder, why there are always such kind of wierd bugs? I just wanna know what happened exactly inside the whole software? Anything wrong with "configure" or "MakeFile"?
I think i have heard of something close to that but it was an odd issue that I was able to get through by following the vendor's guide. Do a little research and see if there is some funky combination between your distro and software....
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.