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.
I'd like to compile GIT on our company's SLES10 machine. Unfortunately, the system is missing a few dependencies and it has been locked down such that no more packages can be installed on a system-wide basis. The missing packages, so far as I can tell, are:
curl-devel
openssl-devel
Is there some way to easily compile these packages in my home directory by making use of the SRPMs? The problem that I'm running into is that curl depends on openssl. I can compile the openssl SRPM, but I have no means to install it, so that doesn't help me around the dependency problem. Any ideas?
Talk to your sysadmin and ask him to install the needed packages. No longer than it would take him, he should have no objections.
This is much more easily said than done. I work in the Nuclear industry, and we live with some fairly stringent QA procedures. Once the computing platform is certified and approved for production calculations, it's effectively set in stone.
As much as the Admins would love to help, they've been given orders not to mess with anything unless it's absolutely necessary.
Usually the NRC (assuming US) certifies the machine and distro (including above packages), but if your internal QA has an issue, then you are pretty much stuck.
Compile everything in your home, then compile curl statically, so you don't need external libs to run it.
Compile everything in your home, then install everything in a fake home directory that all the users can read, use then a wrapper script that sets LD_LIBRARY_PATH+=/home/sharedhomedir/usr/lib and launches curl
Compile everything in your home, then distribute all the needed stuff in a tarball and let the rest of users deal with it.
I don't know what his QA requirements are, so I can't tell for sure. But as long as the home directories are not mounted "noexec", it should run. Another entirely different question is whether the admis will be happy about the users being that smart or not.
In 1 and 3, the binaries will live in your home, so no modification to the system is needed if that's what you ask. It all comes down to one fact: do they allow you to run binaries from your home? If you can run your own bash scripts on your home then you should have no problems running any other kind of executable file.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.