On O2, users can compile and install software in their
/home directories or shared directories (e.g.
/n/dataX ) where you have write permission. In general, during the configure step,
--prefix can be set to a directory where you have write access to install the software to that directory. Software installs via binary files do not need to be compiled, only uncompressed.
1) Download (
curl) or sFTP upload software source files (usually a
tar.gz) to a write-accessible directory (like
/home/mfk8) from an interactive shell (not "login0X").
curl software from an FTP or HTTP URL:
2) Unpack file using
tar from an interactive shell (please do not compile on shell login servers, denoted "loginX")
If the file is a
tar.gz, unpack tarball:
If the file is just
This creates a directory for the software with its contents.
3) Change to the directory created during the unpack, view README or install guide. This may indicate what compilers/libraries are needed to install. Check out
module spider for available compilers and libraries.
4) Load the compiler and any libraries necessary, as found in README, and make sure to specify
--prefix or whatever the equivalent flag is if specified in the README:
5) Usually run
make install (check README/install notes)
6) Software executables are generally now in a "bin" folder. You can add (prepend) these to your
$PATH environment variable like so, to make them accessible simply by name:
If you download and install software into your
/home or other directory, you are generally expected to adhere to any software license agreement. If you have questions about this or need help deploying a license, please feel encouraged to contact HMS Research Computing.