Bureaucrats, cc_docs_admin, cc_staff
2,773
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 15:20, 26 July 2018
, 5 years agoCompiling on compute nodes
(Marked this version for translation) |
(Compiling on compute nodes) |
||
| Line 93: | Line 93: | ||
* all binaries under <code>/cvmfs/soft.computecanada.ca</code> use what is called a RUNPATH, which means that the directories for the runtime libraries that these binaries depend on are put inside the binary. That means it is generally '''not''' necessary to use <code>$LD_LIBRARY_PATH</code>. In fact, <code>$LD_LIBRARY_PATH</code> overrides this runpath and you should '''not''' set that environment variable to locations such as <code>/usr/lib64</code> or <code>$EBROOTNIXPKGS/lib</code>. Many binaries will no longer work if you attempt this. | * all binaries under <code>/cvmfs/soft.computecanada.ca</code> use what is called a RUNPATH, which means that the directories for the runtime libraries that these binaries depend on are put inside the binary. That means it is generally '''not''' necessary to use <code>$LD_LIBRARY_PATH</code>. In fact, <code>$LD_LIBRARY_PATH</code> overrides this runpath and you should '''not''' set that environment variable to locations such as <code>/usr/lib64</code> or <code>$EBROOTNIXPKGS/lib</code>. Many binaries will no longer work if you attempt this. | ||
* if all else fails you can use <code>module --force purge</code> to remove the CVMFS environment. You are then left with a bare-bones CentOS-7 installation without modules. This may help for special situations such as compiling GCC yourself or using custom toolchains such as the [http://www.astro.wisc.edu/~townsend/static.php?ref=mesasdk MESA SDK]. Purging modules would then '''only''' be necessary when you compile such software; the modules can be reloaded when running it. | * if all else fails you can use <code>module --force purge</code> to remove the CVMFS environment. You are then left with a bare-bones CentOS-7 installation without modules. This may help for special situations such as compiling GCC yourself or using custom toolchains such as the [http://www.astro.wisc.edu/~townsend/static.php?ref=mesasdk MESA SDK]. Purging modules would then '''only''' be necessary when you compile such software; the modules can be reloaded when running it. | ||
== Compiling on compute nodes == | |||
In most situations you can compile on the login nodes. However, if the code needs to be built on a node | |||
* with a GPU, or | |||
* with a Skylake CPU, | |||
then you should start an [[Running jobs#Interactive jobs|interactive job]] on a host with the hardware you need, and compile from there. | |||
</translate> | </translate> | ||