<hr>
<address>
- <a href="mail.html" target="body">The deal.II Group</a>
+ <a href="../mail.html" target="body">The deal.II Group</a>
$Date$
</address>
</body>
<hr>
<address>
- <a href="mail.html" target="body">The deal.II Group</a>
+ <a href="../mail.html" target="body">The deal.II Group</a>
$Date$
</address>
</body>
<hr>
<address>
- <a href="mail.html" target="body">The deal.II Group</a>
+ <a href="../mail.html" target="body">The deal.II Group</a>
$Date$
</address>
</body>
<title>Porting deal.II</title>
<link href="../screen.css" rel="StyleSheet" media="screen">
<meta name="author" content="the deal.II authors <authors@dealii.org>">
- <meta name="copyright" content="Copyright (C) 2000, 2001, 2002, 2005, 2010, 2012 by the deal.II authors">
+ <meta name="copyright" content="Copyright (C) 2000, 2001, 2002, 2005, 2010, 2012, 2013 by the deal.II authors">
<meta name="date" content="$Date$">
<meta name="svn_id" content="$Id$">
<meta name="keywords" content="deal.II porting">
Consequently, there is a good chance that <acronym>deal.II</acronym>
will run on a reasonably well behaved system besides the ones listed
- in the <a href="readme.html" target="body">ReadMe</a>. Nevertheless,
+ in the <a href="../readme.html" target="body">ReadMe</a>. Nevertheless,
there are cases where some adjustments are necessary.
</p>
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
- "http://www.w3.org/TR/html4/loose.dtd">
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+ "http://www.w3.org/TR/html4/loose.dtd">
-<html>
- <head>
+<html>
+ <head>
<title>The deal.II Readme on interfacing to ARPACK</title>
<link href="../screen.css" rel="StyleSheet">
- <meta name="author" content="the deal.II authors <authors @ dealii.org>">
- <meta name="copyright" content="Copyright (C) 2010 by the deal.II authors">
- <meta name="date" content="$Date: 2010-05-05 (Thu, 05 May 2010) $">
+ <meta name="author" content="the deal.II authors <authors @ dealii.org>">
+ <meta name="copyright" content="Copyright (C) 2010, 2013 by the deal.II authors">
+ <meta name="date" content="$Date$">
<meta name="svn_id" content="$Id: readme-arpack.html$">
- <meta name="keywords" content="deal.II">
- </head>
- <body>
+ <meta name="keywords" content="deal.II">
+ </head>
+ <body>
+
-
<h2>Installation of <acronym>ARPACK</acronym></h2>
<p>
- <a href="http://www.caam.rice.edu/software/ARPACK/">ARPACK</a>
+ <a href="http://www.caam.rice.edu/software/ARPACK/">ARPACK</a>
is a collection of Fortran77 subroutines designed to solve large
scale eigenvalue problems.
<a href="http://www.caam.rice.edu/software/ARPACK/" target="_top">ARPACK</a>
<li>edit <code>ARmake.inc</code></li>
<ul>
<li>change home to the correct directory</li>
- <li>choose which <acronym>BLAS</acronym> and
+ <li>choose which <acronym>BLAS</acronym> and
<acronym>LAPACK</acronym> you would like to use</li>
</ul>
<li>change the file second.f in the UTIL directory</li>
- <li>do <code>make lib</code> in the current directory
+ <li>do <code>make lib</code> in the current directory
to build the standard library <code>libarpack_$(PLAT).a</code>
</li>
</ul>
</p>
<p>
- Try to run one of the examples and compare the output.
- How the output should look like is stated in the README
+ Try to run one of the examples and compare the output.
+ How the output should look like is stated in the README
that can be found in the <code>EXAMPLES</code> directory.
- </p>
+ </p>
<p>
- If that output you produced looks like it should you can
- proceed to comile <acronym>deal.II</acronym> with
+ If that output you produced looks like it should you can
+ proceed to comile <acronym>deal.II</acronym> with
<acronym>ARPACK</acronym>.
</p>
<hr>
<address>
- <a href="mail.html">The deal.II Group</a>
+ <a href="../mail.html">The deal.II Group</a>
$Date$
</address>
</body>
<link href="../screen.css" rel="StyleSheet">
<meta name="author" content="the deal.II authors <authors @ dealii.org>">
<meta name="copyright" content="Copyright (C) 2010, 2011, 2012, 2013 by the deal.II authors">
- <meta name="date" content="$Date: 2010-05-05 (Thu, 05 May 2010) $">
+ <meta name="date" content="$Date$">
<meta name="svn_id" content="$Id: readme-mumps.html$">
<meta name="keywords" content="deal.II">
</head>
<hr>
<address>
- <a href="mail.html">The deal.II Group</a>
+ <a href="../mail.html">The deal.II Group</a>
$Date$
</address>
</body>
<hr>
<address>
- <a href="mail.html">The deal.II Group</a>
+ <a href="../mail.html">The deal.II Group</a>
$Date$
</address>
</body>
</p>
+ <a name="license-text"></a>
<h3>Full license text</h3>
<pre>
New: There is now some support to include and use routines from the
<a href="http://www.cse.clrc.ac.uk/Activity/HSL"
target="_top">Harwell Subroutine Library</a>.
- (See the <a href="../../readme.html#hsl" target="body">ReadMe</a>
- file for more information on installation of HSL
- subroutines.)
<br>
(WB 2001/01/30)
</p>
existence of a Fortran 77 compiler, and sets its path, some
compiler flags and the libraries to be linked in when mixing
C++ and F77 in some variables in the file
- <code>common/Make.global_options</code> (see also
- <a href="../../development/makefiles.html" target="body">this
- page</a>).
+ <code>common/Make.global_options</code>.
<br>
(WB 2000/12/30)
</p>
<code class="class">SparseDirectMA27</code> and
<code class="class">SparseDirectMA47</code>
for the sparse direct solvers MA27 and MA47.
- (See the <a href="../../readme.html#hsl" target="body">ReadMe</a>
- file for more information on installation of HSL
- subroutines.)
<br>
(WB 2001/01/30)
</p>
<br>
As a consequence, if your makefile makes any assumption on the
location of deal.II include files or the name of the deal.II library
- it will need to be changed. The <a
- href="../../development/makefiles.html">sample Makefiles</a> have been
+ it will need to be changed. The sample Makefiles have been
updated for this.
<br>
(WB 2010/10/25)
library that, among much other functionality, offers some
sparse direct solvers. We have added support for an
interface to these solvers to the library.
- (See the <a href="../readme.html#hsl" target="body">ReadMe</a>
- file for more information on installation of HSL
- subroutines.)
</dd>
<dt>