in the default locations of your system, and similarly for LAPACK.</p>
<p>If your BLAS or LAPACK libraries are not in the standard search
- path of your linker, you heve to linker where to find them. The
- path is not given as an argument to
+ path of your linker, you have to tell the linker where to find them.
+ The path is not given as an argument to
<code>--with-blas</code>. Rather, you set the variable
<code>LDFLAGS</code> accordingly or make sure that the path is in
your <code>LD_LIBRARY_PATH</code> or similar. For details, please
<p> This example will search for a library
<code>libmyblas.a</code> or <code>libmyblas.so</code> in the
directory <code>/my/lib</code> and elswhere in the system library
- paths.</p> </dd>
+ paths.</p>
+
+ <p>Some versions of BLAS and LAPACK need additional libraries
+ to be linked with. Such an example is the
+ <a href="http://math-atlas.sourceforge.net/">automatically tuned
+ linear algebra software (ATLAS)</a>. The BLAS version of this
+ package also needs declarations from <code>libatlas.a</code>,
+ so it must be included. Using the standard library names of
+ atlas, the include for BLAS reads
+ <pre>
+ ./configure --with-blas='f77blas -latlas'
+ </pre>
+ assuming that <code>libf77blas.a</code> and <code>libatlas.a</code>
+ or the respective shared libraries <code>*.so</code> are in your
+ <code>LD_LIBRARY_PATH</code>. LAPACK generated by ATLAS is
+ included in a similar fashion.</p>
+ </dd>
<a name="netcdf"></a>
<dt>NetCDF</dt>