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.
[root@localhost lib]# mklessfs /etc/lessfs.cfg /lessfs
mklessfs: error while loading shared libraries: libhamsterdb.so.5: cannot open shared object file: No such file or directory
i found this file in /usr/local/lib , and i use from
export LD_LIBRARY_PATH =$LD_LIBRARY_PATH:/usr/local/lib
error be ok, but when i write : #echo $?
result : 4
and next commands not work,
can you help me,Please?
Thanks
We don't know what your "/etc/lessfs.cfg" contains, if those settings are sane, if there's errors or warnings in /var/log/messages and if your /lessfs is or was already mounted.
i can ./configure HamsterDB but in make of it, show below error ,
Please DO NOT compile software as root user.
Remove /root/Desktop/rpms/hamsterdb-2.1.9 then unpack hamsterdb-2.1.9.tar.gz as unprivileged user.
Now 'cd' into the hamsterdb-2.1.9 directory and type:
Code:
./configure 2>&1 | tee /tmp/hamsterdb-2.1.9.txt
and then attach "/tmp/hamsterdb-2.1.9.txt" to your reply.
As for me, I don't update the files that drive ldconfig using bash-scripts such as these. I'm much more pedantic. (Read: "I do it by hand ... carefully ... and after backing-up the previous version of the file(s) to avoid accidentally removing my foot.")
The zeroth question is: "Well, if I simply re-run ldconfig, does the problem go away?" New libraries or library-versions won't be found if the cache is not up-to-date, because Linux searches the cache, not the filesystem. If this makes the problem go away, as it often does, then ... " ."
The first question, resolved either with find or perhaps locate, is: "does the library being sought actually exist, and if so, where?" Does more than one version exist? And so on.
The follow-on question is: "does ldconfig know to look there?" And if it doesn't, I'm immediately asking: "Well, why the not?!"
If the library's in the wrong place, then I want to discover why it (erroneously) wound-up where it now is, because "simply moving the thing" might-or might-not actually be sufficient. (Libraries sometimes contain location-dependencies that are built into them by the ./configure script that preceded the make that actually constructed them.) It isn't good-enough for me simply to conclude that something was done incorrectly, because I presume that, when the "mistake" was made, it was earnestly thought to be correct.
Also bear in mind that, when libraries have dependencies on other libraries, the messages that you see might actually be referring to those other libraries. (It happens ...)
[hamid@localhost hamsterdb-2.1.9]$ rpm -qf /usr/local/include/boost/filesystem/operations.hpp
file /usr/local/include/boost/filesystem/operations.hpp is not owned by any package
[hamid@localhost hamsterdb-2.1.9]$
[root@localhost hamsterdb-2.1.9]# find /lib /opt /usr -type f \( -name operations.hpp -o -name \*hamster\* -o -iname \*boost\* \) -printf "rpm -qf \"%p\"\n"|/bin/sh
boost-regex-1.41.0-18.el6.x86_64
boost-iostreams-1.41.0-18.el6.x86_64
boost-devel-1.41.0-18.el6.x86_64
boost-test-1.41.0-18.el6.x86_64
boost-iostreams-1.41.0-18.el6.x86_64
boost-graph-1.41.0-18.el6.x86_64
boost-test-1.41.0-18.el6.x86_64
boost-filesystem-1.41.0-18.el6.x86_64
boost-serialization-1.41.0-18.el6.x86_64
boost-signals-1.41.0-18.el6.x86_64
boost-system-1.41.0-18.el6.x86_64
boost-regex-1.41.0-18.el6.x86_64
boost-serialization-1.41.0-18.el6.x86_64
boost-thread-1.41.0-18.el6.x86_64
boost-date-time-1.41.0-18.el6.x86_64
boost-signals-1.41.0-18.el6.x86_64
kernel-devel-2.6.32-431.el6.x86_64
swig-1.3.40-6.el6.x86_64
vim-common-7.2.411-1.8.el6.x86_64
boost-devel-1.41.0-18.el6.x86_64
libstdc++-devel-4.4.7-4.el6.x86_64
file /usr/local/lib/libboost_log.a is not owned by any package
file /usr/local/lib/libboost_random.a is not owned by any package
file /usr/local/lib/libboost_context.a is not owned by any package
file /usr/local/lib/libboost_iostreams.so.1.57.0 is not owned by any package
file /usr/local/lib/libboost_unit_test_framework.so.1.57.0 is not owned by any package
file /usr/local/lib/libboost_locale.so.1.57.0 is not owned by any package
file /usr/local/lib/libboost_thread.so.1.57.0 is not owned by any package
file /usr/local/include/boost/icl/detail/boost_config.hpp is not owned by any package
file /usr/local/include/boost/atomic/detail/operations.hpp is not owned by any package
file /usr/local/include/boost/geometry/geometries/adapted/boost_array.hpp is not owned by any package
file /usr/local/include/boost/geometry/geometries/adapted/boost_fusion.hpp is not owned by any package
file /usr/local/include/boost/geometry/geometries/adapted/boost_tuple.hpp is not owned by any package
file /usr/local/include/boost/geometry/geometries/adapted/boost_polygon.hpp is not owned by any package
[root@localhost hamsterdb-2.1.9]#
Thanks but you forgot to post output of 'grep -i boost /home/hamid/hamsterdb-2.1.9/config.log'. It doesn't matter right now but for the future remember to be precise and complete. Else things are going to be very inefficient.
Quote:
Originally Posted by hamsaeed
you thinks problem from where?
Yes, for example the boost-devel RPM puts "operations.hpp" in /usr/include/boost/filesystem/ and you show also the same file name in /usr/local/include/boost/atomic/detail/. This happened because you mixed installing software from packages (via Yum) and manually from source (.tar.gz). Decide based on if you need a particular version which software you keep. Else you will have to configure building and using software manually by using non-standard header and library locations. This practice is prone to errors if you do not know how to do that properly and operability / debugging may be severely hampered to boot.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.