ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
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.
Hi. I've got this situation where I want to compile and install something in a local user account (I don't have root privileges). However, the gnu libc version on the system is too old for the software I want to install. (The system has 2.5, I need at least 2.7.) I am wondering how feasible it is to install my own version of gnu libc locally, and use it. I have installed a lot of software locally like this, but never anything as low level as libc.
In general, it's not a good idea, but if you keep it in /home/user, and you have the space, you could build a whole OS in /home. I can see problems ahead, but it should be possible to build. Running might be a different issue.
You should be able to do that. It can probably be accomplished most readily by using the '--prefix=' option to the libc 'configure' step when building your upgraded libc. Make it point to somewhere in your private directory structure. When you build your application, you will need to coerce it to point at the upgraded libc. Without knowing how the application builds, about the best advice I could give would be to add something like 'LDFLAGS+=-L /your/private/libc/directory' to the make commandline. There may be better ways that end up with the additional commands codified in the build system.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.