Installing software in your home directory: Difference between revisions

Jump to navigation Jump to search
Marked this version for translation
No edit summary
(Marked this version for translation)
Line 1: Line 1:
<languages />
<languages />
<translate>
<translate>
<!--T:1-->
Much academic software is freely available on the internet. You can email Compute Canada [mailto:support@computecanada.ca support] staff, provide them with a URL, and ask them to install any such package so that you and other users will be able access it via a [[Using modules|module load]] command. If the license terms and technical requirements are met they will make it available, typically in one or two business days.
Much academic software is freely available on the internet. You can email Compute Canada [mailto:support@computecanada.ca support] staff, provide them with a URL, and ask them to install any such package so that you and other users will be able access it via a [[Using modules|module load]] command. If the license terms and technical requirements are met they will make it available, typically in one or two business days.


<!--T:2-->
You are permitted to install software in your own home space or project space if you wish. You might choose to do this, for example,  
You are permitted to install software in your own home space or project space if you wish. You might choose to do this, for example,  
* if you plan to make your own modifications to the code, or
* if you plan to make your own modifications to the code, or
* if you wish to evaluate it on a shorter timescale than "one or two business days".
* if you wish to evaluate it on a shorter timescale than "one or two business days".


<!--T:3-->
'''Read the installation instructions that accompany the software.''' These instructions often fall into one of the classes described below.
'''Read the installation instructions that accompany the software.''' These instructions often fall into one of the classes described below.


== configure; make; make install ==
== configure; make; make install == <!--T:4-->
{{Commands|./configure
{{Commands|./configure
|make
|make
Line 15: Line 18:
is a very common instruction pattern. Variations include <code>cmake .</code> replacing <code>./configure</code>, and <code>sudo make install</code> replacing <code>make install</code>.
is a very common instruction pattern. Variations include <code>cmake .</code> replacing <code>./configure</code>, and <code>sudo make install</code> replacing <code>make install</code>.


<!--T:5-->
Sometimes this will work exactly as prescribed, but sometimes it will fail at <code>make install</code> because the package expects to be able to write to <code>/usr/local</code> or some other shared area in the file system. It will always fail if <code>sudo make install</code> is attempted, because <code>sudo</code> is a request for "root" or administrator privileges. The usual solution is to supply a <code>--prefix</code> flag at the <code>configure</code> step, to direct the installation to go to the directory of your choice, ''e.g.:''
Sometimes this will work exactly as prescribed, but sometimes it will fail at <code>make install</code> because the package expects to be able to write to <code>/usr/local</code> or some other shared area in the file system. It will always fail if <code>sudo make install</code> is attempted, because <code>sudo</code> is a request for "root" or administrator privileges. The usual solution is to supply a <code>--prefix</code> flag at the <code>configure</code> step, to direct the installation to go to the directory of your choice, ''e.g.:''
{{Command|./configure --prefix{{=}}$PROJECT/some-package && make && make install}}
{{Command|./configure --prefix{{=}}$PROJECT/some-package && make && make install}}


<!--T:6-->
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]].


== apt-get and yum ==
== apt-get and yum == <!--T:7-->
If the software includes instructions to run <code>apt-get</code> or <code>yum</code>, it is unlikely that you will be able to install it using those instructions. Look for instructions that say "to build from source", or contact [mailto:support@computecanada.ca support] for assistance.
If the software includes instructions to run <code>apt-get</code> or <code>yum</code>, it is unlikely that you will be able to install it using those instructions. Look for instructions that say "to build from source", or contact [mailto:support@computecanada.ca support] for assistance.


== Python, R, and Perl packages ==
== Python, R, and Perl packages == <!--T:8-->
[[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.
</translate>
</translate>
Bureaucrats, cc_docs_admin, cc_staff
2,306

edits

Navigation menu