Next changeset 1:37ff27ea37ed (2015-02-14) |
Commit message:
initial upload |
added:
tool_dependencies.xml |
b |
diff -r 000000000000 -r 597c0e54eded tool_dependencies.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/tool_dependencies.xml Sun Aug 11 06:26:05 2013 -0400 |
b |
@@ -0,0 +1,43 @@ +<tool_dependency> + <package name="atlas" version="3.10.1"> + <install version="1.0"> + <actions> + <!-- first action is always downloading --> + <!--<action type="download_by_url" target_filename="ATLAS.tar.bz2">http://downloads.sourceforge.net/project/math-atlas/Stable/3.10.1/atlas3.10.1.tar.bz2</action>--> + <action type="download_file">http://downloads.sourceforge.net/project/math-atlas/Stable/3.10.1/atlas3.10.1.tar.bz2</action> + <action type="shell_command">tar xfvj atlas3.10.1.tar.bz2</action> + <action type="download_file">http://www.netlib.org/lapack/lapack-3.4.2.tgz</action> + + <action type="shell_command"> + # try to disable cpu throttling + if hash cpufreq-selector 2>/dev/null; then + cpufreq-selector -g performance + elif hash cpupower 2>/dev/null; then + cpupower frequency-set -g performance + else + echo 'Please deactivate CPU throttling by your own, or install cpufreq-selector' + exit + fi + </action> + <action type="shell_command"> + cd ATLAS && + mkdir build && + cd build && + mkdir $INSTALL_DIR/atlas/ && + ../configure -Fa alg -fPIC --prefix=$INSTALL_DIR/atlas/ --with-netlib-lapack-tarfile=../../lapack-3.4.2.tgz + </action> + <action type="shell_command">cd ./ATLAS/build && make </action> + <action type="shell_command">cd ./ATLAS/build && make install</action> + + <action type="set_environment"> + <environment_variable name="ATLAS_LIB_DIR" action="set_to">$INSTALL_DIR/atlas/lib</environment_variable> + <environment_variable name="ATLAS_INCLUDE_DIR" action="set_to">$INSTALL_DIR/atlas/include</environment_variable> + </action> + </actions> + </install> + <readme>ATLAS_LIB_DIR and ATLAS_INCLUDE_DIR (including libatlas.a) will be exported for later use. + During ATLAS library compilation, ATLAS performs code efficiency checks. These checks can only provide optimal results, if "frequency scaling" is disabled on the CPU, and no other load-intense processes are running. + Ideally, you should compile on an empty cluster node with CPU frequency scaling disabled (see "cpufreq-selector" or "cpufreq-set"). + </readme> + </package> +</tool_dependency> |