Mercurial > repos > bgruening > upload_testing
view tool_dependencies.xml @ 62:f9c068c8a80a
Uploaded
author | bgruening |
---|---|
date | Fri, 20 Sep 2013 06:30:04 -0400 |
parents | b2e673e1db33 |
children | d507ebc3b071 |
line wrap: on
line source
<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"> 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 ./build && make </action> <action type="shell_command">cd ./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>