Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Most beginners (sorry if I'm wrong) made this mistake, they believe they should upgrade or upgrade X/KDE/glibc because an installer says so. I'd recommend getting a better package suited for your distribution
..doesn't fedora have this packate listed in their package manager already?
i got the package from fedora repository.
i would be great if u can clarify ,how i can get the right package.
i ahve been able to compile svgalib-19 on my system,but am not able to run the demo examples,because they ask for libc.so.6(GLIBC_2.4).
do u have any idea,how i can get around this problem.
Unless you really know what you are doing, fiddling with upgrading glibc will likely result in a borked system. It's happened to me before. Even trying to upgrade with a built in package manager doesn't ensure it will work, as there are a lot of other things related to glibc you need to do. As the other poster said, try to either get a better package, or compile from source and skip and glibc test.
i tried installing svgalib using rpm package,it won't install bcause of faild dependency(i.e. libc.so.6) and if i compile from source,i am not able to run the demos which cannot lnk to libc.so.6
this version of svgalib is a devel version and requires libc.so.6(GLIBC_2.4), which is present in glibc-2.3.90-11(devel)
and libc.so -2.3.4 is diff from libc.so.6(GLIBC_2.4)
i am running glibc-2.3.5 the latest stble version on my box.
Originally posted by foo_bar_foo there is something wrong with this post we need to clarify
are you trying to compile things that won't link
or are things complaining at runtime
i have a link
libc.so.6 -> libc-2.3.4.so
in /lib
do you have that pointing to your 2.3.5 ?
Just another tip: those files are usually added by the -devel packages. Do you have glibc-devel installed?
Do a locate to be sure that the file actually exists, then look closely (ls -l) at the files to be sure what symlinks point to what.
Then, just to be sure, as root do /sbin/ldconfig to make sure that the loader's library-cache is up to date.
Be sure that all of the directories (other than /lib, /usr/lib) that contain any libraries are listed in /etc/ld.so.conf. If you change it, run ldconfig again.
Fiddling with glibc definitely leads to borkness. My testbed system is rather awkwardly 'semi-borked' right now, probably in-part due to this.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.