Until I hear otherwise, I am proceding as if priya is not the sysadmin.
Advice still holds - ask the sysadmin to install the program - or an approved equivalent. If this is a school/university machine, considering the program in question this seems likely, then ask a course supervisor to ask the sysadmin. This is usually more effective.
If the admin, or whoever, says no, then give up. Go curse short-sighted admins everywhere and look for something else. Get a laptop. Create a VPN to your home computer and run the software there. Whatever.
The only reason I'm still watching this is that the problem is an interesting application of hacking skills.
Reviewing the software - the first program was GDIS
and the second was GULP
The system is stated to be Ubuintu (no release number given) so one would not be bothering with rpm anyway, not usually. You'd want to hack dpkg and a deb file.
We'd normally sudo apt-get install gdis
as GDIS is in the repos.
GULP is not free software
GULP is available free of charge to academics provided you accept the following conditions of use:
1. The program is not to be distributed to anyone else without the express permission of the author.
2. The program is not to be used for commercial research. For any commercial use of the program a license must be obtained from Accelrys Inc, including contract research.
3. The program is supplied on an "as is" basis with no implied guarantee or support.
... and registration is required to download - which checks that the user has access to an academic email address. A university computer looks very likely.
GULP devs support linux and mac (but not windows - in ter rest ting) so one could reasonably email for help - but read the faq first. The FAQ says that you have to edit the file
getmachine under the Linux or Darwin section, for PC Linux and Mac respectively, and set the options appropriately for your machine.
It's a fortran program, and linux has a choice of compilers.
So - did priya do this? If not, this may well explain the not-found library. Of course not having the lib installed or installed to a non-standard place, or not having permissions to access the lib would all produce that error too.
GULP does not exist as a deb file or an rpm.
One could use the dpkg tools to make a deb file, then install from that. You still want a valid build environment though, which we do not seem to have.
Downloading the GDIS deb file from the repo, and extracting it to see what's what would be another approach.