forked from gfrd/egfrd
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathINSTALL
More file actions
75 lines (43 loc) · 1.71 KB
/
Copy pathINSTALL
File metadata and controls
75 lines (43 loc) · 1.71 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
:author: Koichi Takahashi
Prerequisites
-------------------------
1. autotools
(autoconf (>=2.50), automake (>=1.11) libtool (>=2.2.6))
2. GNU Scientific Library (GSL) 1.11 or later.
3. Boost C++ Library 1.37 or later.
4. Python 2.4 or later.
5. Scipy 0.5 or later, Numpy 1.0 or later.
If you use Fedora or any other RedHat lines of linux, check
if the following RPM packages are installed:
gsl, gsl-devel, numpy, scipy, boost, and boost-devel.
On Ubuntu Linux and some other Debian families, install the following:
gsl-bin libgsl0-dev libboost-dev libboost-date-time-dev libboost-python-dev libboost-regex-dev libboost-test-dev python-scipy.
In addition to above, optionally,
6. python-matplotlib if you want to use the plotting scripts in the samples.
7. Pychecker if you want to run 'make pycheck'.
A note on GSL version
++++++++++++++++++++++++++++++
GSL version 1.10 and earlier has at least two bugs that can cause abnormal
program exits when a Bessel function is evaluated with specific argument
values. These bugs can hit stability of this software.
For this reason, use of GSL version 1.11 or later is recommended.
Building this package
-------------------------
1. ./configure
2. make
If you cannot find the configure script, or the build process
fails to complete even if you have set up the environment correctly,
try
./autogen.sh
to remake the entire build mechanism.
Testing
-------------------
% make check
checks if some of the core components of the software run correctly.
In addition, you may run
% make pycheck
if you want to be super-strict about Python syntax.
Running
-------------------------
Go to subdirectories under doc/samples, and read README files
included about how to run the samples.