Bureaucrats, cc_docs_admin, cc_staff
2,224
edits
Installing software in your home directory: Difference between revisions
Jump to navigation
Jump to search
Installing software in your home directory (view source)
Revision as of 17:12, 24 August 2017
, 6 years agoMarked this version for translation
No edit summary |
(Marked this version for translation) |
||
| Line 25: | Line 25: | ||
If other errors arise, contact [mailto:support@computecanada.ca support]. For more information see [[Make]], [[Autotools]], and [[CMake]]. | If other errors arise, contact [mailto:support@computecanada.ca support]. For more information see [[Make]], [[Autotools]], and [[CMake]]. | ||
==Using Libraries== | ==Using Libraries== <!--T:16--> | ||
Normally the simplest way to make use of a library on a Compute Canada system is to first load the corresponding module | Normally the simplest way to make use of a library on a Compute Canada system is to first load the corresponding module | ||
{{Command|module load library_name/x.y.z}} | {{Command|module load library_name/x.y.z}} | ||
| Line 41: | Line 41: | ||
[[Python]], [[R]], and [[Perl]] are languages with large libraries of extension packages, and package managers that can easily install almost any desired extension in your home directory. See the page for each language to find out if the package you're looking for is already available on our systems. If it is not, you should also find detailed guidance there on using that language's package manager to install it for yourself. | [[Python]], [[R]], and [[Perl]] are languages with large libraries of extension packages, and package managers that can easily install almost any desired extension in your home directory. See the page for each language to find out if the package you're looking for is already available on our systems. If it is not, you should also find detailed guidance there on using that language's package manager to install it for yourself. | ||
== Installing binary packages == | == Installing binary packages == <!--T:15--> | ||
If you install pre-compiled binaries in your home directory (for example [https://conda.io/miniconda.html Miniconda]) they may fail using errors such as <code>/lib64/libc.so.6: version `GLIBC_2.18' not found</code>. Often such binaries can be patched using our <code>setrpaths.sh</code> script, using the syntax <code>setrpaths.sh --path path [--add_origin]</code> where path refers to the directory where you installed that software. This script will make sure that the binaries use the correct interpreter, and search for the libraries they are dynamically linked to in the correct folder. The option <code>--add_origin</code> will also add $ORIGIN to the RUNPATH. This is sometimes helpful if the library cannot find other libraries in the same folder as itself. | If you install pre-compiled binaries in your home directory (for example [https://conda.io/miniconda.html Miniconda]) they may fail using errors such as <code>/lib64/libc.so.6: version `GLIBC_2.18' not found</code>. Often such binaries can be patched using our <code>setrpaths.sh</code> script, using the syntax <code>setrpaths.sh --path path [--add_origin]</code> where path refers to the directory where you installed that software. This script will make sure that the binaries use the correct interpreter, and search for the libraries they are dynamically linked to in the correct folder. The option <code>--add_origin</code> will also add $ORIGIN to the RUNPATH. This is sometimes helpful if the library cannot find other libraries in the same folder as itself. | ||