Differences
This shows you the differences between two versions of the page.
|
sep:software:installing_seplib [2008/07/23 22:33] altheyab created |
sep:software:installing_seplib [2015/05/27 02:06] (current) |
||
|---|---|---|---|
| Line 11: | Line 11: | ||
| Follow the following steps to install SEPlib from source | Follow the following steps to install SEPlib from source | ||
| - | * Download the [[http://sep.stanford.edu/pub/sep-distr/seplib-6.5.1.tar.gz| software ]] | + | * Download the [[sep:software:SEPlib#Downloading| software ]] |
| * gunzip seplib-6.5.1.tar.gz -c |tar xf - | * gunzip seplib-6.5.1.tar.gz -c |tar xf - | ||
| * cd seplib-6.5.1 | * cd seplib-6.5.1 | ||
| Line 24: | Line 24: | ||
| * [--with-mpi] Compile with MPI support | * [--with-mpi] Compile with MPI support | ||
| * [--with-su=/su/directory] Compile SU support | * [--with-su=/su/directory] Compile SU support | ||
| - | * [--with-mansupport] some systems don't include the packages neqn, tbl, etc. If your system does, use this option If you run into problems (for example you need to add an additional library path when compiling programs) you can often solve your problem by setting environmental variables that the configure script will then use. For example: | + | * [--with-mansupport] some systems don't include the packages neqn, tbl, etc. |
| + | If your system does, use this option If you run into problems (for example you need to add an additional library path when compiling programs) you can often solve your problem by setting environmental variables that the configure script will then use. For example: | ||
| * [FC] The Fortran compiler | * [FC] The Fortran compiler | ||
| * [LDFLAGS] Directories and libraries to link when compiling C programs | * [LDFLAGS] Directories and libraries to link when compiling C programs | ||
| Line 39: | Line 40: | ||
| * [MPI_LD] Mpi linking flags | * [MPI_LD] Mpi linking flags | ||
| * [PPM_FLAGS] PPM compiling flags | * [PPM_FLAGS] PPM compiling flags | ||
| - | * [PPM_LD] PPM linking flags SEPlib now uses a GNU-style configure mechanism for installation, this includes the packages: | + | * [PPM_LD] PPM linking flags |
| + | SEPlib now uses a GNU-style configure mechanism for installation, this includes the packages: | ||
| * autoconf | * autoconf | ||
| * automake | * automake | ||
| - | * libtool ===== Further sugestions ===== | + | * libtool |
| + | ===== Further sugestions ===== | ||
| * Try removimg seplib_base/lib/corelibs/sep/sepgetpar_scan.c and vplot/filters/loclib/getpar_scan.c if compiling fails for one of these files. This seems particularly problematic on Solaris. You will need to make sure you have flex or lex in your path before configuring SEPlib for this to work. | * Try removimg seplib_base/lib/corelibs/sep/sepgetpar_scan.c and vplot/filters/loclib/getpar_scan.c if compiling fails for one of these files. This seems particularly problematic on Solaris. You will need to make sure you have flex or lex in your path before configuring SEPlib for this to work. | ||
| * If using the Sun Fortran compiler also use the Sun C compiler (setenv CC /path/to/C) | * If using the Sun Fortran compiler also use the Sun C compiler (setenv CC /path/to/C) | ||
| Line 51: | Line 54: | ||
| * Email bob at sep.stanford.edu if you have any problems | * Email bob at sep.stanford.edu if you have any problems | ||
| - | \\ | + | * For Ubuntu 8.04; install with synaptic package manager: gfortran, g++, libtool, flex, x11 development kits. |
| + | |||
| + | |||
| + | \\ \\ | ||
| + | {{page>share:footer&nofooter&noeditbtn}} | ||
