Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's 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.
Number One, make a good backup, restore it to test it's integrity.
Now go ahead and try if you have libc.so.0 There will be copious problems.
Difficulties between libraries built for different versions will certainly give you a headache.
If you were super keen and happy to track down all the bits I still wouldn't mix versions.
---------------------------------------------------------------------------
If the information was valuable to you give me a pat on the back (click my rep)
Caveat: I have not done this myself, but according to two pages I found online (linked at the bottom of this reply), you simply include the specific .so or .a file in the gcc command line. For instance:
Quote:
Code:
gcc -Wall calc.c /usr/lib/libm.a -o calc
Keep in mind, I assume that works with any library you would normally link with using the -l or -L options to gcc. However, because libc is automatically linked, this may not work for it. You may need to do some research to disable ld's automatic inclusion of '-lc' when linking.
I am actually cross compiling Eglibc for the ARM architecture using the Linaro Tool chain.
I cross compiled Eglibc.When i tried to verify it, by linking an application against the eglibc's libc.so.6, it was taking the default libc.so.6, that was actaully present in the Cross-compiler and not my copy of libc.so.6.
As per the caveat of Dark Helmet, it was not working.
So how should i proceed.As per my understanding,in x86,the linker ie ld, reads /etc/ld.so.conf and also the directories specified in the LD_LIBRARY_PATH to take the libraries.
In that way, is there any path or file that needs to be modified?
And any hints on how to disable the automatic inclusion of -lc while loading and link my version of libc.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.