Mercurial > repos > bgruening > package_atlas_3_10

view tool_dependencies.xml @ 5:3bf7e2082c5c

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Uploaded
author bgruening
date Tue, 21 May 2013 20:10:14 -0400
parents 11bb8ca8c41c
children 0c59f3a0d124
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_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">cd ATLAS &amp;&amp;
                    mkdir build &amp;&amp;
                    cd build &amp;&amp;
                    mkdir $INSTALL_DIR/atlas/ &amp;&amp;
                    <!-- It's not supported by many systems.
                    cpufreq-selector -g performance &amp;&amp;
                    -->
                    ../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 &amp;&amp; make </action>
                <action type="shell_command">cd ./ATLAS/build &amp;&amp; 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 will be set (including libatlas.a).
        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>