[cig-commits] r18293 - in short/3D/PyLith/trunk: . doc/install
brad at geodynamics.org
brad at geodynamics.org
Tue Apr 26 11:38:18 PDT 2011
Author: brad
Date: 2011-04-26 11:38:18 -0700 (Tue, 26 Apr 2011)
New Revision: 18293
Removed:
short/3D/PyLith/trunk/doc/install/Cluster_Rocks-4.3-AMD64.txt
short/3D/PyLith/trunk/doc/install/Cluster_Rocks-4.3-AMD64_bash.sh
short/3D/PyLith/trunk/doc/install/Linux_Fedora8-AMD64_Aagaard.txt
short/3D/PyLith/trunk/doc/install/Linux_Fedora8-AMD64_Aagaard_bash.sh
short/3D/PyLith/trunk/doc/install/Linux_ubuntu-AMD64_Aagaard.sh
short/3D/PyLith/trunk/doc/install/Linux_ubuntu-AMD64_Aagaard.txt
short/3D/PyLith/trunk/doc/install/MacBookPro_Aagaard.txt
short/3D/PyLith/trunk/doc/install/MacBookPro_Aagaard_bash.sh
Modified:
short/3D/PyLith/trunk/DEPENDENCIES
short/3D/PyLith/trunk/INSTALL
short/3D/PyLith/trunk/README
short/3D/PyLith/trunk/doc/install/Makefile.am
short/3D/PyLith/trunk/doc/install/README
Log:
Updated installation instructions to use PyLith Installer.
Modified: short/3D/PyLith/trunk/DEPENDENCIES
===================================================================
--- short/3D/PyLith/trunk/DEPENDENCIES 2011-04-26 18:00:54 UTC (rev 18292)
+++ short/3D/PyLith/trunk/DEPENDENCIES 2011-04-26 18:38:18 UTC (rev 18293)
@@ -1,3 +1,5 @@
+See INSTALL for suggested methods for installing PyLith.
+
REQUIRED DEPENDENCIES
MPI
@@ -13,6 +15,7 @@
OPTIONAL DEPENDENCIES
cppunit
+HDF5
CUBIT
netcdf
PETSc (development version) w/TetGen and ParMetis
Modified: short/3D/PyLith/trunk/INSTALL
===================================================================
--- short/3D/PyLith/trunk/INSTALL 2011-04-26 18:00:54 UTC (rev 18292)
+++ short/3D/PyLith/trunk/INSTALL 2011-04-26 18:38:18 UTC (rev 18293)
@@ -1,266 +1,9 @@
Installation instructions are available in the PyLith manual
available on the CIG website
-(http://www.geodynamics.org/cig/software/packages/short/pylith/).
+(http://www.geodynamics.org/cig/software/pylith).
-Detailed instructions for installing PyLith on several platforms are
-available in the doc/install directory.
-
-System Requirements
-===================
-
-PyLith should work on any UN*X system. It requires the following
-language tools:
-
-* A C compiler.
-
-* A C++ compiler.
-
-* Python 2.3 or later; see <http://www.python.org/>.
-
-If you are using a modern UN*X system, there is a good chance that all
-of the above tools are already installed.
-
-In addition, PyLith v1.4 requires the following software packages:
-
-1. MPI
-2. PETSc
-3. Pythia (CIG)
-4. Nemesis (CIG)
-5. Proj
-6. Cppunit (optional; needed to run tests)
-7. Netcdf (optional; needed to import meshes from CUBIT)
-8. Numpy
-9. FIAT
-10. Spatialdata (CIG)
-
-Generic GNU Installation Instructions
-*************************************
-
-Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004 Free
-Software Foundation, Inc.
-
-This file is free documentation; the Free Software Foundation gives
-unlimited permission to copy, distribute and modify it.
-
-Basic Installation
-==================
-
-These are generic installation instructions.
-
- The `configure' shell script attempts to guess correct values for
-various system-dependent variables used during compilation. It uses
-those values to create a `Makefile' in each directory of the package.
-It may also create one or more `.h' files containing system-dependent
-definitions. Finally, it creates a shell script `config.status' that
-you can run in the future to recreate the current configuration, and a
-file `config.log' containing compiler output (useful mainly for
-debugging `configure').
-
- It can also use an optional file (typically called `config.cache'
-and enabled with `--cache-file=config.cache' or simply `-C') that saves
-the results of its tests to speed up reconfiguring. (Caching is
-disabled by default to prevent problems with accidental use of stale
-cache files.)
-
- If you need to do unusual things to compile the package, please try
-to figure out how `configure' could check whether to do them, and mail
-diffs or instructions to the address given in the `README' so they can
-be considered for the next release. If you are using the cache, and at
-some point `config.cache' contains results you don't want to keep, you
-may remove or edit it.
-
- The file `configure.ac' (or `configure.in') is used to create
-`configure' by a program called `autoconf'. You only need
-`configure.ac' if you want to change it or regenerate `configure' using
-a newer version of `autoconf'.
-
-The simplest way to compile this package is:
-
- 1. `cd' to the directory containing the package's source code and type
- `./configure' to configure the package for your system. If you're
- using `csh' on an old version of System V, you might need to type
- `sh ./configure' instead to prevent `csh' from trying to execute
- `configure' itself.
-
- Running `configure' takes awhile. While running, it prints some
- messages telling which features it is checking for.
-
- 2. Type `make' to compile the package.
-
- 3. Optionally, type `make check' to run any self-tests that come with
- the package.
-
- 4. Type `make install' to install the programs and any data files and
- documentation.
-
- 5. You can remove the program binaries and object files from the
- source code directory by typing `make clean'. To also remove the
- files that `configure' created (so you can compile the package for
- a different kind of computer), type `make distclean'. There is
- also a `make maintainer-clean' target, but that is intended mainly
- for the package's developers. If you use it, you may have to get
- all sorts of other programs in order to regenerate files that came
- with the distribution.
-
-Compilers and Options
-=====================
-
-Some systems require unusual options for compilation or linking that the
-`configure' script does not know about. Run `./configure --help' for
-details on some of the pertinent environment variables.
-
- You can give `configure' initial values for configuration parameters
-by setting variables in the command line or in the environment. Here
-is an example:
-
- ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
-
- *Note Defining Variables::, for more details.
-
-Compiling For Multiple Architectures
-====================================
-
-You can compile the package for more than one kind of computer at the
-same time, by placing the object files for each architecture in their
-own directory. To do this, you must use a version of `make' that
-supports the `VPATH' variable, such as GNU `make'. `cd' to the
-directory where you want the object files and executables to go and run
-the `configure' script. `configure' automatically checks for the
-source code in the directory that `configure' is in and in `..'.
-
- If you have to use a `make' that does not support the `VPATH'
-variable, you have to compile the package for one architecture at a
-time in the source code directory. After you have installed the
-package for one architecture, use `make distclean' before reconfiguring
-for another architecture.
-
-Installation Names
-==================
-
-By default, `make install' will install the package's files in
-`/usr/local/bin', `/usr/local/man', etc. You can specify an
-installation prefix other than `/usr/local' by giving `configure' the
-option `--prefix=PREFIX'.
-
- You can specify separate installation prefixes for
-architecture-specific files and architecture-independent files. If you
-give `configure' the option `--exec-prefix=PREFIX', the package will
-use PREFIX as the prefix for installing programs and libraries.
-Documentation and other data files will still use the regular prefix.
-
- In addition, if you use an unusual directory layout you can give
-options like `--bindir=DIR' to specify different values for particular
-kinds of files. Run `configure --help' for a list of the directories
-you can set and what kinds of files go in them.
-
- If the package supports it, you can cause programs to be installed
-with an extra prefix or suffix on their names by giving `configure' the
-option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
-
-Optional Features
-=================
-
-Some packages pay attention to `--enable-FEATURE' options to
-`configure', where FEATURE indicates an optional part of the package.
-They may also pay attention to `--with-PACKAGE' options, where PACKAGE
-is something like `gnu-as' or `x' (for the X Window System). The
-`README' should mention any `--enable-' and `--with-' options that the
-package recognizes.
-
- For packages that use the X Window System, `configure' can usually
-find the X include and library files automatically, but if it doesn't,
-you can use the `configure' options `--x-includes=DIR' and
-`--x-libraries=DIR' to specify their locations.
-
-Specifying the System Type
-==========================
-
-There may be some features `configure' cannot figure out automatically,
-but needs to determine by the type of machine the package will run on.
-Usually, assuming the package is built to be run on the _same_
-architectures, `configure' can figure that out, but if it prints a
-message saying it cannot guess the machine type, give it the
-`--build=TYPE' option. TYPE can either be a short name for the system
-type, such as `sun4', or a canonical name which has the form:
-
- CPU-COMPANY-SYSTEM
-
-where SYSTEM can have one of these forms:
-
- OS KERNEL-OS
-
- See the file `config.sub' for the possible values of each field. If
-`config.sub' isn't included in this package, then this package doesn't
-need to know the machine type.
-
- If you are _building_ compiler tools for cross-compiling, you should
-use the `--target=TYPE' option to select the type of system they will
-produce code for.
-
- If you want to _use_ a cross compiler, that generates code for a
-platform different from the build platform, you should specify the
-"host" platform (i.e., that on which the generated programs will
-eventually be run) with `--host=TYPE'.
-
-Sharing Defaults
-================
-
-If you want to set default values for `configure' scripts to share, you
-can create a site shell script called `config.site' that gives default
-values for variables like `CC', `cache_file', and `prefix'.
-`configure' looks for `PREFIX/share/config.site' if it exists, then
-`PREFIX/etc/config.site' if it exists. Or, you can set the
-`CONFIG_SITE' environment variable to the location of the site script.
-A warning: not all `configure' scripts look for a site script.
-
-Defining Variables
-==================
-
-Variables not defined in a site shell script can be set in the
-environment passed to `configure'. However, some packages may run
-configure again during the build, and the customized values of these
-variables may be lost. In order to avoid this problem, you should set
-them in the `configure' command line, using `VAR=value'. For example:
-
- ./configure CC=/usr/local2/bin/gcc
-
-will cause the specified gcc to be used as the C compiler (unless it is
-overridden in the site shell script).
-
-`configure' Invocation
-======================
-
-`configure' recognizes the following options to control how it operates.
-
-`--help'
-`-h'
- Print a summary of the options to `configure', and exit.
-
-`--version'
-`-V'
- Print the version of Autoconf used to generate the `configure'
- script, and exit.
-
-`--cache-file=FILE'
- Enable the cache: use and save the results of the tests in FILE,
- traditionally `config.cache'. FILE defaults to `/dev/null' to
- disable caching.
-
-`--config-cache'
-`-C'
- Alias for `--cache-file=config.cache'.
-
-`--quiet'
-`--silent'
-`-q'
- Do not print messages saying which checks are being made. To
- suppress all normal output, redirect it to `/dev/null' (any error
- messages will still be shown).
-
-`--srcdir=DIR'
- Look for the package's source code in directory DIR. Usually
- `configure' can determine that directory automatically.
-
-`configure' also accepts some other, not widely useful, options. Run
-`configure --help' for more details.
-
+We *STRONGLY* recommend that you first become familiar with PyLith
+using the binary packages before attempting to install PyLith from
+source. If you want to install from source, we recommend using the
+PyLith Installer, which is available on the PyLith webpage listed
+above.
Modified: short/3D/PyLith/trunk/README
===================================================================
--- short/3D/PyLith/trunk/README 2011-04-26 18:00:54 UTC (rev 18292)
+++ short/3D/PyLith/trunk/README 2011-04-26 18:38:18 UTC (rev 18293)
@@ -20,7 +20,7 @@
You can download the source code and binaries from
- http://geodynamics.org/cig/software/packages/short/pylith
+ http://geodynamics.org/cig/software/pylith
Installation instructions are in the bundled README and INSTALL
files, as well as in the User Manual on the web page.
Deleted: short/3D/PyLith/trunk/doc/install/Cluster_Rocks-4.3-AMD64.txt
===================================================================
--- short/3D/PyLith/trunk/doc/install/Cluster_Rocks-4.3-AMD64.txt 2011-04-26 18:00:54 UTC (rev 18292)
+++ short/3D/PyLith/trunk/doc/install/Cluster_Rocks-4.3-AMD64.txt 2011-04-26 18:38:18 UTC (rev 18293)
@@ -1,372 +0,0 @@
-======================================================================
-INSTRUCTIONS FOR INSTALLING PYLITH ON A LINUX CLUSTER RUNNING ROCKS-4.3
-======================================================================
-
-I place applications that are rarely updated in $HOME/tools. For CIG
-source code, I separate the source code, build directories, and
-installed code. The source code sits in $HOME/src/cig, I build the
-packages under $HOME/scratch/build/cig, and install the packages to
-$HOME/tools/cig.
-
-I use the bash shell and place all software package environment
-variables in a .bash.tools file that is read by the .bashrc file.
-
-On an x86_64 system it is important to keep files associated with a
-32-bit architecture separate from those associated with a 64-bit
-architecture. Some architecture independent files are put in
-$PREFIX/lib with 64-bit architecture files in $PREFIX/lib64. In most
-cases when a library with versions for both architectures is
-available, the linker will use the one compatible with the requested
-architecture (the default is usually the 64-bit architecture).
-
-To make things easier, I create environment variables TOOLS_DIR,
-CIG_DIR, TOOLS_FORMAT, and PYTHON_VERSION. The TOOLS_FORMAT variable
-makes it easier to maintain multiple copies of packages built with
-different options (e.g., different compilers and different levels of
-optimization). Note that the python version should match the version
-of Python you will be using. If you don't know the version of python,
-run "python --version".
-
- export TOOLS_DIR=${HOME}/tools
- export TOOLS_FORMAT=gcc-3.4_64
- export PYTHON_VERSION=2.4
-
- export CIG_DIR=${HOME}/tools/cig/${TOOLS_FORMAT}
- export CIG_INCDIR=${CIG_DIR}/include
- export CIG_LIBDIR=${CIG_DIR}/lib
- export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${CIG_LIBDIR}
- export PYTHONPATH=${PYTHONPATH}:${CIG_DIR}/lib64/python${PYTHON_VERSION}/site-packages:${CIG_DIR}/lib/python${PYTHON_VERSION}/site-packages
- PATH=${CIG_DIR}/bin:$PATH
-
-1. Install additional CentOS packages (must be root).
-
- Make sure the Rocks installation procedure installs the following
- packages (these are not usually installed by default).
-
- These can be installed by running
-
- rpm -Uvh /home/install/rocks-dist/lan/x86_64/RedHat/RPMS/PACKAGE_FILE.rpm
-
- gdb
- libtool
-
-2. Install the PVFS2 Roll (Optional, must be root).
-
- PyLith does not currently use parallel I/O, but it will likely do so
- in the future. As a result, we include instructions for installing
- PyLith with PVFS2 and MPICH2 with PVFS2.
-
- PVFS2 provides a virtual parallel file system using the local disk
- on each node. Stability is not great, but it does provide
- significantly better performance than serial I/O. Another feature
- is that it spreads the data over the local disks on the I/O
- (compute) nodes.
-
- a. Set Rocks to install the PVFS2 roll.
-
- b. Set environment variables.
-
- export PVFS2_DIR=/opt/pvfs2
- export PVFS2_INCDIR=$PVFS2_DIR/include
- export PVFS2_LIBDIR=$PVFS2_DIR/lib
-
-3. Adjust your environment to use Python 2.4 instead of Python 2.3.
-
- Python 2.3 contains bugs that prevent its full functionality on a
- x86_64 system. Rocks installs Python 2.4 in /opt/rocks.
-
- PATH=/opt/rocks/bin:${PATH}
- export PYTHON_DIR=/opt/rocks/lib/python$PYTHON_VERSION
- export PYTHON_LIBDIR=/opt/rocks/lib/python$PYTHON_VERSION
- export PYTHON_INCDIR=/opt/rocks/include/python$PYTHON_VERSION
-
-4. Install numpy (http://numpy.scipy.org/).
-
- PyLith requires numpy >= 1.0 (the version that comes with Rocks 4.3
- is 0.9).
-
- a. Untar the source code.
-
- b. Install the software.
-
- python setup.py install --prefix=${TOOLS_DIR}/numpy-1.0.3-2/${TOOLS_FORMAT}
-
- c. Set environment variables.
-
- NUMPY_DIR=${TOOLS_DIR}/numpy-1.0.3/${TOOLS_FORMAT}
- export PYTHONPATH=${PYTHONPATH}:${NUMPY_DIR}/lib/python${PYTHON_VERSION}/site-packages
-
-
-5. Install mercurial (http://www.selenic.com/mercurial/wiki/)
-
- a. Untar the source code.
-
- b. Install the package.
-
- python setup.py install --prefix=$TOOLS_DIR/mercurial-0.9.4/${TOOLS_FORMAT}
-
- c. Set environment variables.
-
- MERCURIAL_DIR=${TOOLS_DIR}/mercurial-0.9.3/${TOOLS_FORMAT}
- PATH=${PATH}:${MERCURIAL_DIR}/bin
- export PYTHONPATH=${PYTHONPATH}:${MERCURIAL_DIR}/lib/python${PYTHON_VERSION}/site-packages
-
-6. Install the AMD Core Math Library (ACML).
-
- http://developer.amd.com/tools/acml/Pages/default.aspx
-
- Notes: (i) You need to register to download.
- (ii) Make sure you download the version appropriate for your
- compiler (version 3.5.0 for Rocks 4.3).
-
- a. Expand the tarball and run the installation script.
- I install to ${TOOLS_DIR}/acml-3.5.0.
-
- b. Set environment variables.
-
- ACML_DIR=${TOOLS_DIR}/acml-3.5.0/gnu64
- export ACML_LIBDIR=${ACML_DIR}/lib
- export ACML_INCDIR=${ACML_DIR}/include
- export LD_LIBRARY_PATH=${ACML_LIBDIR}:${LD_LIBRARY_PATH}
-
-7. Install MPICH2 (http://www.mcs.anl.gov/research/projects/mpich2/)
-
- IMPORTANT NOTE: When installing MPICH2 to work with PVFS2, the two
- versions must be compatible. If you get errors when building the
- romio portion of MPICH2 associated with PVFS2, you likely don't have
- compatible versions of PVFS2 and MPICH2. I found mpich2-1.0.4p1 to
- be compatible with the Rocks 4.3 PVFS2 roll.
-
- a. Untar the source and then run configure, build, and install.
-
- export CC=gcc
- export CXX=g++
- export F77=g77
- export FC=g77
- export CFLAGS="-fPIC -I${PVFS2_INCDIR}"
- export CXXFLAGS=-fpic
- export F77FLAGS=-fpic
- export LDFLAGS="-L${PVFS2_LIBDIR}"
- export LIBS="-lpvfs2 -lssl -lpthread -lrt"
-
- ./configure --with-arch=LINUX --disable-f90 --enable-sharedlibs=gcc --enable-cxx --prefix=${TOOLS_DIR}/mpich2-1.0.4p1/${TOOLS_FORMAT} --enable-g=none --enable-romio --with-file-system=pvfs2+ufs+nfs
- make
- make install
-
- b. Set environment variables.
-
- export RSHCOMMAND=ssh
- export MPI_DIR=${TOOLS_DIR}/mpich2-1.0.4p1/${TOOLS_FORMAT}
- PATH=$MPI_DIR/bin:$PATH
- export MANPATH=$MPI_DIR/man:$MANPATH
- export MPI_INCDIR=$MPI_DIR/include
- export MPI_LIBDIR=$MPI_DIR/lib
- export LD_LIBRARY_PATH=${MPI_LIBDIR}:${LD_LIBRARY_PATH}
- export MPI_VERSION=2
-
-8. Install ParMetis (http://glaros.dtc.umn.edu/gkhome/metis/parmetis/overview)
-
- a. Untar the source and edit the Makefile.
- b. Set the CC, COPTIONS, INCDIR, LD, and LIBDIR variables.
-
- CC = gcc
- COPTIONS = -fPIC
- INCDIR = -I${MPI_INCDIR}
- LD = gcc
- LIBDIR = -L${MPI_LIBDIR} -lmpich -lpthread -lrt
-
- c. Create shared libraries by hand.
-
- cd ${TOOLS_DIR}/parmetis-3.1/${TOOLS_FORMAT}/lib
- mkdir tmp
- cd tmp
- ar -x ../libmetis.a
- gcc -o ../libmetis.so -shared *.o
- rm *.o
- ar -x ../libparmetis.a
- gcc -o ../libparmetis.so -shared *.o
- rm *.o
- cd ..
- rmdir tmp
-
- d. Copy parmetis.h to the install location.
-
- cp parmetis.h ${TOOLS_DIR}/parmetis-3.1/${TOOLS_FORMAT}/include/
-
- e. Set environment variables.
-
- PARMETIS_DIR=$TOOLS_DIR/parmetis-3.1/${TOOLS_FORMAT}
- export PARMETIS_INCDIR=$PARMETIS_DIR/include
- export PARMETIS_LIBDIR=$PARMETIS_DIR/lib
- export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${PARMETIS_LIBDIR}
-
-9. Install cppunit (http://cppunit.sourceforge.net/cppunit-wiki)
-
- a. Untar the source and run configure, build, and install.
-
- ./configure --prefix=${TOOLS_DIR}/cppunit-1.10.2/${TOOLS_FORMAT}
- make
- make install
-
- b. Set environment variables.
-
- CPPUNIT_DIR=${TOOLS_DIR}/cppunit-1.10.2/${TOOLS_FORMAT}
- PATH=${PATH}:${CPPUNIT_DIR}/bin
- export CPPUNIT_LIBDIR=${CPPUNIT_DIR}/lib
- export CPPUNIT_INCDIR=${CPPUNIT_DIR}/include
- export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${CPPUNIT_LIBDIR}
-
-10. Install FIAT (http://www.fenics.org/wiki/FIAT)
-
- a. Install FIAT.
-
- python setup.py install --prefix=$TOOLS_DIR/fiat-0.3.1/${TOOLS_FORMAT}
-
- b. Set environment variables.
-
- FIAT_DIR=${TOOLS_DIR}/fiat-0.3.3/${TOOLS_FORMAT}
- export PYTHONPATH=${PYTHONPATH}:${FIAT_DIR}/lib/python${PYTHON_VERSION}/site-packages
-
-11. Install the development version of PETSc
- (http://www-unix.mcs.anl.gov/petsc/petsc-as/)
-
- a. Clone the source repository.
-
- hg clone http://petsc.cs.iit.edu/petsc/petsc-dev
- cd petsc-dev/config
- hg clone http://petsc.cs.iit.edu/petsc/BuildSystem BuildSystem
-
- b. Set PETSC_ARCH and PETSC_DIR environment variables.
-
- export PETSC_DIR=${TOOLS_DIR}/petsc-dev
- export PETSC_ARCH=linux_${TOOLS_FORMAT}_opt
-
- c. Configure PETSc, build, and test.
-
- ARCH_FLAGS="--PETSC_ARCH=linux_${TOOLS_FORMAT}_opt --with-debugging=no"
- LANG_FLAGS="--with-clanguage=c++"
- BUILD_FLAGS="--with-mpi-compilers=0 --with-gnu-compilers=1 --with-shared=1 --with-dynamic=1 --with-64-bit-points=1 --with-large-file-io=1 --CC=gcc --CXX=g++ --FC=g77 --F77=g77"
- MPI_FLAGS="--with-mpi-dir=${TOOLS_DIR}/mpich2-1.0.4p1/gcc-3.4_64 --with-mpi-shared=0"
- LIBS="-L${PVFS2_LIBDIR} -lpvfs2 -lssl -lpthread -lrt"
- OPTIONS="--with-lgrind=0 --download-tetgen"
- PART_FLAGS="--with-chaco=1 --download-chaco=1 --with-parmetis=1 --with-parmetis-dir=${TOOLS_DIR}/parmetis-3.1/gcc-3.4_64"
- SIEVE_FLAGS="--with-sieve=1 --with-boost=1 --download-boost=1"
- config/configure.py ${ARCH_FLAGS} ${LANG_FLAGS} ${BUILD_FLAGS} --with-blas-lapack-lib="-L${ACML_LIBDIR} -lacml -lacml_mv" ${MPI_FLAGS} --LIBS="-L${PVFS2_LIBDIR} -lpvfs2 -lssl" ${OPTIONS} ${PART_FLAGS} ${SIEVE_FLAGS}
- make
- make test
-
-12. Install SWIG (http://www.swig.org/)
-
- a. Untar and install.
-
- tar -zxvf swig.1.3.39.tgz
- configure --prefix=${TOOLS_DIR}/swig-1.3.39/${TOOLS_FORMAT}
- make
- make install
-
- b. Update environment variables.
-
- SWIG_DIR=${TOOLS_DIR}/swig-1.3.39/${TOOLS_FORMAT}
- PATH=${PATH}:${SWIG_DIR}/bin
-
-13. Install pythia.
-
- a. Download the source code from the SVN repository.
-
- svn co http://geodynamics.org/svn/cig/cs/pythia/trunk pythia
-
- b. Install the software.
-
- python setup.py install --prefix=${CIG_DIR}
-
- c. Set environment variables.
-
- export PYTHIA_INCDIR=${CIG_INCDIR}/pythia-0.8
-
-14. Install nemesis.
-
- a. Download the source code from the SVN repository.
-
- svn co http://geodynamics.org/svn/cig/cs/nemesis/trunk nemesis
-
- b. Create the configure script.
-
- autoreconf -if
-
- c. Run configure, build, and install.
-
- ./configure --prefix=${CIG_DIR} CPPFLAGS="-I${CIG_INCDIR} -I${MPI_INCDIR}" LDFLAGS="-L${CIG_LIBDIR} -L${MPI_LIBDIR} -L${PVFS2_LIBDIR}" LIBS="-lpvfs2 -lssl -lpthread -lrt" CC=gcc CXX=g++ FC=g77 F77=g77
- make
- make install
-
-15. Install PROJ.4 (http://trac.osgeo.org/proj/)
-
- a. Download the source code AND the datum shifts (proj-datumgrid-1.3.zip).
-
- b. Untar the source code and unzip the datum shifts in the nad directory.
-
- c. Run configure and build.
-
- ./configure --prefix=${TOOLS_DIR}/proj-4.5.0/${TOOLS_FORMAT} CC=gcc CXX=g++ FC=g77 F77=f77
- make
- make install
-
- d. Set environment variables.
-
- PROJ4_DIR=${TOOLS_DIR}/proj-4.5.0/${TOOLS_FORMAT}
- PATH=${PATH}:${PROJ4_DIR}/bin
- export PROJ4_INCDIR=${PROJ4_DIR}/include
- export PROJ4_LIBDIR=${PROJ4_DIR}/lib
- export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${PROJ4_LIBDIR}
- export MANPATH=${MANPATH}:${PROJ4_DIR}/man
-
-16. Install netcdf (http://www.unidata.ucar.edu/software/netcdf/).
-
- a. Untar the source code.
-
- b. Run configure and build.
-
- ./configure --prefix=${TOOLS_DIR}/netcdf-3.6.2/${TOOLS_FORMAT} --disable-f90 --enable-shared CC=gcc CXX=g++ F77=g77 CFLAGS=-fPIC FFLAGS=-fPIC
- make
- make install
-
- c. Set environment variables.
-
- NETCDF_DIR=${TOOLS_DIR}/netcdf-3.6.2/${TOOLS_FORMAT}
- export NETCDF_INCDIR=${NETCDF_DIR}/include
- export NETCDF_LIBDIR=${NETCDF_DIR}/lib
-
-
-17. Install spatialdata.
-
- a. Download the source code from the SVN repository.
-
- svn co http://geodynamics.org/svn/cig/cs/spatialdata-0.1/trunk spatialdata
-
- b. Create the configure script.
-
- autoreconf -if
-
- c. Run configure, build, install, and the unit tests.
-
- ./configure --enable-pythia --enable-testing --prefix=${CIG_DIR} CPPFLAGS="-I${PROJ4_INCDIR} -I${CPPUNIT_INCDIR} -I${CIG_INCDIR}" LDFLAGS="-L${PROJ4_LIBDIR} -L${CPPUNIT_LIBDIR} -L${CIG_LIBDIR} " LIBS="" CC=gcc CXX=g++ FC=g77 F77=f77
- make
- make install
- make check
-
-18. Install PyLith.
-
- a. Download the source code from the SVN repository.
-
- svn co http://geodynamics.org/svn/cig/short/3D/PyLith/trunk pylith
-
- b. Create the configure script.
-
- autoreconf -if
-
- c. Run configure, build, install, and the unit tests.
-
- ./configure --enable-testing --enable-tetgen --enable-cubit --prefix=${CIG_DIR} CPPFLAGS="-I${PROJ4_INCDIR} -I${CPPUNIT_INCDIR} -I${CIG_INCDIR} -I${PYTHIA_INCDIR} -I${NETCDF_INCDIR}" LDFLAGS="-L${PROJ4_LIBDIR} -L${CPPUNIT_LIBDIR} -L${CIG_LIBDIR} -L${NETCDF_LIBDIR}" LIBS="" CC=gcc CXX=g++ FC=g77 F77=f77
- make
- make install
- make check
Deleted: short/3D/PyLith/trunk/doc/install/Cluster_Rocks-4.3-AMD64_bash.sh
===================================================================
--- short/3D/PyLith/trunk/doc/install/Cluster_Rocks-4.3-AMD64_bash.sh 2011-04-26 18:00:54 UTC (rev 18292)
+++ short/3D/PyLith/trunk/doc/install/Cluster_Rocks-4.3-AMD64_bash.sh 2011-04-26 18:38:18 UTC (rev 18293)
@@ -1,92 +0,0 @@
-# Environment variables for Bash Shells associated with Brad Aagaard's
-# install of PyLith on a Linux cluster running Rocks 4.3.
-
-# General
-export TOOLS_DIR=${HOME}/tools
-export TOOLS_FORMAT=gcc-3.4_64
-export PYTHON_VERSION=2.4
-
-# Location for installation of CIG software
-export CIG_DIR=${HOME}/tools/cig/${TOOLS_FORMAT}
-export CIG_INCDIR=${CIG_DIR}/include
-export CIG_LIBDIR=${CIG_DIR}/lib
-export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${CIG_LIBDIR}
-export PYTHONPATH=${PYTHONPATH}:${CIG_DIR}/lib64/python${PYTHON_VERSION}/site-packages:${CIG_DIR}/lib/python${PYTHON_VERSION}/site-packages
-PATH=${CIG_DIR}/bin:$PATH
-
-# PVFS2
-export PVFS2_DIR=/opt/pvfs2
-export PVFS2_INCDIR=$PVFS2_DIR/include
-export PVFS2_LIBDIR=$PVFS2_DIR/lib
-
-# Python 2.4
-PATH=/opt/rocks/bin:${PATH}
-export PYTHON_DIR=/opt/rocks/lib/python$PYTHON_VERSION
-export PYTHON_LIBDIR=/opt/rocks/lib/python$PYTHON_VERSION
-export PYTHON_INCDIR=/opt/rocks/include/python$PYTHON_VERSION
-
-# Numpy
-NUMPY_DIR=${TOOLS_DIR}/numpy-1.0.3/${TOOLS_FORMAT}
-export PYTHONPATH=${PYTHONPATH}:${NUMPY_DIR}/lib/python${PYTHON_VERSION}/site-packages
-
-# Mercurial
-MERCURIAL_DIR=${TOOLS_DIR}/mercurial-0.9.3/${TOOLS_FORMAT}
-PATH=${PATH}:${MERCURIAL_DIR}/bin
-export PYTHONPATH=${PYTHONPATH}:${MERCURIAL_DIR}/lib/python${PYTHON_VERSION}/site-packages
-
-# ACML
-ACML_DIR=${TOOLS_DIR}/acml-3.5.0/gnu64
-export ACML_LIBDIR=${ACML_DIR}/lib
-export ACML_INCDIR=${ACML_DIR}/include
-export LD_LIBRARY_PATH=${ACML_LIBDIR}:${LD_LIBRARY_PATH}
-
-# MPICH2
-export RSHCOMMAND=ssh
-export MPI_DIR=${TOOLS_DIR}/mpich2-1.0.4p1/${TOOLS_FORMAT}
-PATH=$MPI_DIR/bin:$PATH
-export MANPATH=$MPI_DIR/man:$MANPATH
-export MPI_INCDIR=$MPI_DIR/include
-export MPI_LIBDIR=$MPI_DIR/lib
-export LD_LIBRARY_PATH=${MPI_LIBDIR}:${LD_LIBRARY_PATH}
-export MPI_VERSION=2
-
-# Parmetis
-PARMETIS_DIR=$TOOLS_DIR/parmetis-3.1/${TOOLS_FORMAT}
-export PARMETIS_INCDIR=$PARMETIS_DIR/include
-export PARMETIS_LIBDIR=$PARMETIS_DIR/lib
-export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${PARMETIS_LIBDIR}
-
-# Cppunit
-CPPUNIT_DIR=${TOOLS_DIR}/cppunit-1.10.2/${TOOLS_FORMAT}
-PATH=${PATH}:${CPPUNIT_DIR}/bin
-export CPPUNIT_LIBDIR=${CPPUNIT_DIR}/lib
-export CPPUNIT_INCDIR=${CPPUNIT_DIR}/include
-export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${CPPUNIT_LIBDIR}
-
-# FIAT
-FIAT_DIR=${TOOLS_DIR}/fiat-0.3.3/${TOOLS_FORMAT}
-export PYTHONPATH=${PYTHONPATH}:${FIAT_DIR}/lib/python${PYTHON_VERSION}/site-packages
-
-# PETSc
-export PETSC_DIR=${TOOLS_DIR}/petsc-dev
-export PETSC_ARCH=linux_${TOOLS_FORMAT}_opt
-
-# SWIG
-SWIG_DIR=${TOOLS_DIR}/swig-1.3.39/${TOOLS_FORMAT}
-PATH=${PATH}:${SWIG_DIR}/bin
-
-# Pythia
-export PYTHIA_INCDIR=${CIG_INCDIR}/pythia-0.8
-
-# Proj.4
-PROJ4_DIR=${TOOLS_DIR}/proj-4.5.0/${TOOLS_FORMAT}
-PATH=${PATH}:${PROJ4_DIR}/bin
-export PROJ4_INCDIR=${PROJ4_DIR}/include
-export PROJ4_LIBDIR=${PROJ4_DIR}/lib
-export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${PROJ4_LIBDIR}
-export MANPATH=${MANPATH}:${PROJ4_DIR}/man
-
-# NETCDF
-NETCDF_DIR=${TOOLS_DIR}/netcdf-3.6.2/${TOOLS_FORMAT}
-export NETCDF_INCDIR=${NETCDF_DIR}/include
-export NETCDF_LIBDIR=${NETCDF_DIR}/lib
Deleted: short/3D/PyLith/trunk/doc/install/Linux_Fedora8-AMD64_Aagaard.txt
===================================================================
--- short/3D/PyLith/trunk/doc/install/Linux_Fedora8-AMD64_Aagaard.txt 2011-04-26 18:00:54 UTC (rev 18292)
+++ short/3D/PyLith/trunk/doc/install/Linux_Fedora8-AMD64_Aagaard.txt 2011-04-26 18:38:18 UTC (rev 18293)
@@ -1,271 +0,0 @@
-======================================================================
-INSTRUCTIONS FOR INSTALLING PYLITH ON LINUX x86_64 RUNNING FEDORA 8
-======================================================================
-
-I place applications that are rarely updated in /tools/common. This
-directory is in a separate /tools partition from system and user
-files; this is why I don't use /usr/local. For CIG source code, I
-separate the source code, build directories, and installed code. The
-source code sits in $HOME/src/cig, I build the packages under
-$HOME/scratch/build/cig, and install the packages to $HOME/tools/cig.
-
-I use the bash shell and place all software package environment
-variables in a .bash.tools file that is read by the .bashrc file.
-
-On an x86_64 system it is important to keep files associated with a
-32-bit architecture separate from those associated with a 64-bit
-architecture. Some architecture independent files are put in
-$PREFIX/lib with 64-bit architecture files in $PREFIX/lib64. In most
-cases when a library with versions for both architectures is
-available, the linker will use the one compatible with the requested
-architecture (the default is usually the 64-bit architecture).
-
-To make things easier, I create environment variables TOOLS_DIR,
-CIG_DIR, TOOLS_FORMAT, and PYTHON_VERSION. The TOOLS_FORMAT variable
-makes it easier to maintain multiple copies of packages built with
-different options (e.g., different compilers and different levels of
-optimization). Note that the python version should match the version
-of Python you will be using. If you don't know the version of python,
-run "python --version".
-
- export TOOLS_DIR=/tools/common
- export TOOLS_FORMAT=gcc-4.1.2_64
- export PYTHON_VERSION=2.5
-
- export CIG_DIR=${HOME}/tools/cig/${TOOLS_FORMAT}
- export CIG_INCDIR=${CIG_DIR}/include
- export CIG_LIBDIR=${CIG_DIR}/lib
- export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${CIG_LIBDIR}
- export PYTHONPATH=${PYTHONPATH}:${CIG_DIR}/lib64/python${PYTHON_VERSION}/site-packages:${CIG_DIR}/lib/python${PYTHON_VERSION}/site-packages
- PATH=${CIG_DIR}/bin:$PATH
-
- export NETCDF_INCDIR=/usr/include/netcdf-3
- export NETCDF_LIBDIR=/usr/lib64/netcdf-3
- export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${NETCDF_LIBDIR}
-
-
-1. When installing Fedora, include the development tools (gcc,
-gfortran, etc). in the installation.
-
-2. Install additional packages using yum (you need to be root).
-
- yum install NAMES_OF_PACKAGES
-
- Recommended packages:
-
- cppunit
- cppunit-devel
- proj
- proj-devel
- proj-nad
- numpy
- swig
- netcdf
- netcdf-devel
- mercurial
-
-3. Install the AMD Core Math Library (ACML).
-
- http://developer.amd.com/tools/acml/Pages/default.aspx
-
- Notes: (i) You need to register to download.
- (ii) Make sure you download the version appropriate for your
- compiler (e.g., acml-4-0-1-gfortran-64bit.tgz for gcc 4.1).
-
- a. Expand the tarball and run the installation script.
- I install to ${TOOLS_DIR}/acml-4.0.1
-
- b. Set environment variables.
-
- ACML_DIR=${TOOLS_DIR}/acml-4.0.1/gfortran64
- export ACML_INCDIR=${ACML_DIR}/include
- export ACML_LIBDIR=${ACML_DIR}/lib
- export ACML_LIBS="-lacml_mv -lacml -lgfortran -lm"
- export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${ACML_LIBDIR}
-
-4. Install MPICH2 (http://www.mcs.anl.gov/research/projects/mpich2/)
-
- a. Untar the source and then run configure, build, and install.
-
- export CC=gcc
- export CXX=g++
- export F77=gfortran
- export CFLAGS=-fPIC
- export CXXFLAGS=-fpic
- export F77FLAGS=-fpic
-
- ./configure --with-arch=LINUX --disable-f90 --enable-sharedlibs=gcc --enable-cxx --prefix=${TOOLS_DIR}/mpich2-1.0.6p1/${TOOLS_FORMAT} --enable-g=none --enable-romio --with-device=ch3:nemesis --enable-fast
- make
- make install
-
- b. Set environment variables.
-
- export RSHCOMMAND=ssh
- export MPI_DIR=$TOOLS_DIR/mpich2-1.0.6p1/${TOOLS_FORMAT}
- PATH=$MPI_DIR/bin:$PATH
- export MANPATH=$MPI_DIR/man:$MANPATH
- export MPI_INCDIR=$MPI_DIR/include
- export MPI_LIBDIR=$MPI_DIR/lib
- export LD_LIBRARY_PATH=${MPI_LIBDIR}:${LD_LIBRARY_PATH}
-
-5. Install ParMetis (http://glaros.dtc.umn.edu/gkhome/metis/parmetis/overview)
-
- a. Untar the source and edit the Makefile.
- b. Set the CC, COPTIONS, INCDIR, LD, and LIBDIR variables.
-
- CC = gcc
- COPTIONS = -fPIC
- INCDIR = -I${MPI_INCDIR}
- LD = gcc
- LIBDIR = -L${MPI_LIBDIR} -lmpich -lpthread -lrt
-
- c. Create shared libraries by hand.
-
- cd ${TOOLS_DIR}/parmetis-3.1/${TOOLS_FORMAT}/lib
- mkdir tmp
- cd tmp
- ar -x ../libmetis.a
- gcc -o ../libmetis.so -shared *.o
- rm *.o
- ar -x ../libparmetis.a
- gcc -o ../libparmetis.so -shared *.o
- rm *.o
- cd ..
- rmdir tmp
-
- d. Copy parmetis.h to the install location.
-
- cp parmetis.h ${TOOLS_DIR}/parmetis-3.1/${TOOLS_FORMAT}/include/
-
- e. Set environment variables.
-
- PARMETIS_DIR=$TOOLS_DIR/parmetis-3.1/${TOOLS_FORMAT}
- export PARMETIS_INCDIR=$PARMETIS_DIR/include
- export PARMETIS_LIBDIR=$PARMETIS_DIR/lib
- export PARMETIS_LIBS="-lparmetis -lmetis"
- export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${PARMETIS_LIBDIR}
-
-6. Install FIAT (http://www.fenics.org/wiki/FIAT)
-
- a. Install FIAT.
-
- python setup.py install --prefix=$TOOLS_DIR/fiat-0.3.1/${TOOLS_FORMAT}
-
- b. Set environment variables.
-
- FIAT_DIR=${TOOLS_DIR}/fiat-0.3.1/${TOOLS_FORMAT}
- export PYTHONPATH=${PYTHONPATH}:${FIAT_DIR}/lib/python${PYTHON_VERSION}/site-packages
-
-7. Install the development version of PETSc
- (http://www-unix.mcs.anl.gov/petsc/petsc-as/)
-
- a. Clone the source repository.
-
- hg clone http://petsc.cs.iit.edu/petsc/petsc-dev
- cd petsc-dev/config
- hg clone http://petsc.cs.iit.edu/petsc/BuildSystem BuildSystem
-
- b. Set PETSC_ARCH and PETSC_DIR environment variables.
-
- export PETSC_DIR=${TOOLS_DIR}/petsc-dev
- export PETSC_ARCH=linux_${TOOLS_FORMAT}_debug
-
- c. Configure PETSc, build, and test.
-
- ARCH_FLAGS="--PETSC_ARCH=linux_${TOOLS_FORMAT}_debug --with-debugging=1"
- LANG_FLAGS="--with-clanguage=c++"
- BUILD_FLAGS="--with-mpi-compilers=0 --with-gnu-compilers=1 --with-shared=1 --with-dynamic=1 --with-64-bit-points=1 --with-large-file-io=1 --CC=gcc --CXX=g++ --FC=gfortran --F77=gfortran"
- MPI_FLAGS="--with-mpi-dir=/tools/common/mpich2-1.0.6p1/${TOOLS_FORMAT} --with-mpi-shared=0"
- OPTIONS="--with-lgrind=0 --download-tetgen"
- PART_FLAGS="--with-chaco=1 --download-chaco=1 --with-parmetis=1 --with-parmetis-dir=/tools/common/parmetis-3.1/${TOOLS_FORMAT}"
- SIEVE_FLAGS="--with-sieve=1 --with-boost=1 --download-boost=1"
- config/configure.py ${ARCH_FLAGS} ${LANG_FLAGS} ${BUILD_FLAGS} --with-blas-lapack-lib="-L${TOOLS_DIR}/acml-4.0.1/${ACML_SUBDIR}/lib -lacml -lacml_mv" ${MPI_FLAGS} ${OPTIONS} ${PART_FLAGS} ${SIEVE_FLAGS} ${EXTRA_FLAGS}
- make
- make test
-
-8. Install pythia.
-
- a. Download the source code from the SVN repository.
-
- svn co http://geodynamics.org/svn/cig/cs/pythia/trunk pythia
-
- b. Install the software.
-
- python setup.py install --prefix=${CIG_DIR}
-
- c. Set environment variables.
-
- export PYTHIA_INCDIR=${CIG_INCDIR}/pythia-0.8
-
-9. Install nemesis.
-
- a. Download the source code from the SVN repository.
-
- svn co http://geodynamics.org/svn/cig/cs/nemesis/trunk nemesis
-
- b. Create the configure script.
-
- autoreconf -if
-
- c. Run configure, build, and install.
-
- ./configure --prefix=${CIG_DIR} CPPFLAGS="-I${CIG_INCDIR} -I${MPI_INCDIR}" LDFLAGS="-L${CIG_LIBDIR} -L${MPI_LIBDIR}" LIBS="-lpthread -lrt" CC=gcc CXX=g++ FC=gfortran F77=gfortran
-
- make
- make install
-
-10. Install spatialdata.
-
- a. Download the source code from the SVN repository.
-
- svn co http://geodynamics.org/svn/cig/cs/spatialdata-0.1/trunk spatialdata
-
- b. Create the configure script.
-
- autoreconf -if
-
- c. Run configure, build, install, and the unit tests.
-
- ./configure --enable-testing --enable-pythia --prefix=${CIG_DIR} CPPFLAGS="-I${CIG_INCDIR}" LDFLAGS="-L${CIG_LIBDIR} " LIBS="" CC=gcc CXX=g++ FC=gfortran F77=gfortran
- make
- make install
- make check
-
-11. Install PyLith.
-
- a. Download the source code from the SVN repository.
-
- svn co http://geodynamics.org/svn/cig/short/3D/PyLith/trunk pylith
-
- b. Create the configure script.
-
- autoreconf -if
-
- c. Run configure, build, install, and the unit tests.
-
- ./configure --enable-testing --enable-cubit --enable-tetgen --prefix=${CIG_DIR} CPPFLAGS="-I${CIG_INCDIR} -I${NETCDF_INCDIR}" LDFLAGS="-L${CIG_LIBDIR} -L${NETCDF_LIBDIR}" LIBS="" CC=gcc CXX=g++ FC=gfortran F77=gfortran CFLAGS="-g -O" CXXFLAGS="-g -O"
- make
- make install
- make check
-
-======================================================================
-OPTIONAL: Install Mayavi2 for visualization.
-======================================================================
-
-1. Install the following packages:
-
- scipy
- python-matplotlib
- python-imaging
- python-setuptools
- python-setuptools-devel
- vtk
- vtk-devel
- vtk-python
-
-2. Install Mayavi2 using eggs.
-
- unset PYTHONPATH
- export PYTHONPATH=${TOOLS_DIR}/mayavi2/${TOOLS_FORMAT}/lib/python${PYTHON_VERSION}/site-packages
- mkdir -p $PYTHONPATH
- easy_install -d $PYTHONPATH -f http://code.enthought.com/enstaller/eggs/source enthought.mayavi
Deleted: short/3D/PyLith/trunk/doc/install/Linux_Fedora8-AMD64_Aagaard_bash.sh
===================================================================
--- short/3D/PyLith/trunk/doc/install/Linux_Fedora8-AMD64_Aagaard_bash.sh 2011-04-26 18:00:54 UTC (rev 18292)
+++ short/3D/PyLith/trunk/doc/install/Linux_Fedora8-AMD64_Aagaard_bash.sh 2011-04-26 18:38:18 UTC (rev 18293)
@@ -1,54 +0,0 @@
-# Environment variables for Bash Shells associated with Brad Aagaard's
-# install of PyLith on a AMD64 computer running Fedora 8.
-
-# General
-export TOOLS_DIR=/tools/common
-export TOOLS_FORMAT=gcc-4.1.2_64
-export PYTHON_VERSION=2.5
-
-# Location for installation of CIG software
-export CIG_DIR=${HOME}/tools/cig/${TOOLS_FORMAT}
-export CIG_INCDIR=${CIG_DIR}/include
-export CIG_LIBDIR=${CIG_DIR}/lib
-export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${CIG_LIBDIR}
-export PYTHONPATH=${PYTHONPATH}:${CIG_DIR}/lib64/python${PYTHON_VERSION}/site-packages:${CIG_DIR}/lib/python${PYTHON_VERSION}/site-packages
-PATH=${CIG_DIR}/bin:$PATH
-
-# ACML
-ACML_DIR=${TOOLS_DIR}/acml-4.0.1/gfortran64
-export ACML_INCDIR=${ACML_DIR}/include
-export ACML_LIBDIR=${ACML_DIR}/lib
-export ACML_LIBS="-lacml_mv -lacml -lgfortran -lm"
-export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${ACML_LIBDIR}
-
-# MPICH2
-export RSHCOMMAND=ssh
-export MPI_DIR=$TOOLS_DIR/mpich2-1.0.6p1/${TOOLS_FORMAT}
-PATH=$MPI_DIR/bin:$PATH
-export MANPATH=$MPI_DIR/man:$MANPATH
-export MPI_INCDIR=$MPI_DIR/include
-export MPI_LIBDIR=$MPI_DIR/lib
-export LD_LIBRARY_PATH=${MPI_LIBDIR}:${LD_LIBRARY_PATH}
-
-# PARMETIS
-PARMETIS_DIR=$TOOLS_DIR/parmetis-3.1/${TOOLS_FORMAT}
-export PARMETIS_INCDIR=$PARMETIS_DIR/include
-export PARMETIS_LIBDIR=$PARMETIS_DIR/lib
-export PARMETIS_LIBS="-lparmetis -lmetis"
-export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${PARMETIS_LIBDIR}
-
-# FIAT
-FIAT_DIR=${TOOLS_DIR}/fiat-0.3.1/${TOOLS_FORMAT}
-export PYTHONPATH=${PYTHONPATH}:${FIAT_DIR}/lib/python${PYTHON_VERSION}/site-packages
-
-# PETSc
-export PETSC_DIR=${TOOLS_DIR}/petsc-dev
-export PETSC_ARCH=linux_${TOOLS_FORMAT}_debug
-
-# Pythia
-export PYTHIA_INCDIR=${CIG_INCDIR}/pythia-0.8
-
-# NETCDF (installed as package)
-export NETCDF_INCDIR=/usr/include/netcdf-3
-export NETCDF_LIBDIR=/usr/lib64/netcdf-3
-export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${NETCDF_LIBDIR}
Deleted: short/3D/PyLith/trunk/doc/install/Linux_ubuntu-AMD64_Aagaard.sh
===================================================================
--- short/3D/PyLith/trunk/doc/install/Linux_ubuntu-AMD64_Aagaard.sh 2011-04-26 18:00:54 UTC (rev 18292)
+++ short/3D/PyLith/trunk/doc/install/Linux_ubuntu-AMD64_Aagaard.sh 2011-04-26 18:38:18 UTC (rev 18293)
@@ -1,39 +0,0 @@
-#!/bin/bash
-
-#
-if [ "$TOOLS_FORMAT" == "" ]; then
- export TOOLS_FORMAT=gcc-4.4.1_64
-fi
-
-# Store pre-tools info so we can reread this file after changing settings
-if (($READTOOLS)); then
- PATH=${path_notools}
- export LD_LIBRARY_PATH=${ld_library_path_notools}
- export MANPATH=${manpath_notools}
- export PYTHONPATH=${pythonpath_notools}
-else
- export path_notools=${PATH}
- export ld_library_path_notools=${LD_LIBRARY_PATH}
- export manpath_notools=${MANPATH}
- export pythonpath=${PYTHONPATH}
- export READTOOLS=1
-fi
-
-PYTHON_VERSION=2.6
-
-export TOOLS_DIR=$HOME/tools/${TOOLS_FORMAT}
-if [ "$LD_LIBRARY_PATH" == "" ]; then
- export LD_LIBRARY_PATH=${TOOLS_DIR}/lib
-else
- export LD_LIBRARY_PATH=${TOOLS_DIR}/lib:${LD_LIBRARY_PATH}
-fi
-if [ "${PYTHON_PATH}" == "" ]; then
- export PYTHONPATH=${TOOLS_DIR}/lib/python${PYTHON_VERSION}/site-packages
-else
- export PYTHONPATH=${TOOLS_DIR}/lib/python${PYTHON_VERSION}/site-packages:${PYTHONPATH}
-fi
-PATH=${TOOLS_DIR}/bin:${PATH}
-
-# PETSC
-export PETSC_DIR=$HOME/src/petsc-dev
-export PETSC_ARCH=${TOOLS_FORMAT}
Deleted: short/3D/PyLith/trunk/doc/install/Linux_ubuntu-AMD64_Aagaard.txt
===================================================================
--- short/3D/PyLith/trunk/doc/install/Linux_ubuntu-AMD64_Aagaard.txt 2011-04-26 18:00:54 UTC (rev 18292)
+++ short/3D/PyLith/trunk/doc/install/Linux_ubuntu-AMD64_Aagaard.txt 2011-04-26 18:38:18 UTC (rev 18293)
@@ -1,205 +0,0 @@
-======================================================================
-INSTRUCTIONS FOR INSTALLING PYLITH ON LINUX x86_64 RUNNING UBUNTU 9.10
-======================================================================
-
-These installation instructions use as many Ubuntu packages as
-possible. This reduces the number of packages that must be built from
-source. We do not use the Ubuntu openmpi-1.3.2-3 because it appears to
-contain bugs that cause PyLith to hang when running in
-parallel. Instead, we build openmpi-1.4.2 from source.
-
-We install development versions of the CIG software. Installing using
-source tarballs is easy, simply replace downloading from the source
-repository and running autoreconf with downloading and unpacking the
-tarball.
-
-To make things easier, I create environment variables TOOLS_DIR,
-TOOLS_FORMAT, and PYTHON_VERSION. The TOOLS_FORMAT variable
-makes it easier to maintain multiple copies of packages built with
-different options (e.g., different compilers and different levels of
-optimization). Note that the python version should match the version
-of Python you will be using. If you don't know the version of python,
-run "python --version".
-
-See the Linux_ubuntu-AMD64_Aagaard.sh file for the settings used to
-setup the environment variables using the bash shell. The
-$TOOLS_FORMAT environment variable is used to differentiate between
-packages built with different compilers and/or different optimization
-settings. In this case, TOOLS_FORMAT is gcc-4.4.1_64. We use a medium
-level of optimization and do not strip out error checking code. You
-should setup your environment BEFORE building the packages.
-
-Source files
-
- Source files are placed under $HOME/src/PACKAGE.
-
-Build directories
-
- Packages supporting building in separate directories are built in
- $HOME/scratch/build/$TOOLS_FORMAT.
-
-Install directorires
-
- Packages are installed in $HOME/tools/$TOOLS_FORMAT.
-
-
-1. When installing Ubuntu, include the development tools (gcc,
-gfortran, etc). in the installation.
-
-2. Install additional packages.
-
- libcppunit
- libcppunit-dev
- proj
- proj-data
- libproj-dev
- swig-1.3.36
- python-numpy
- netcdf-bin
- libnetcdf-dev
- libnetcdf4
- mercurial
- subversion
- autoconf
- automake
-
-3. Install OpenMPI
-
- Download and unpack the tarball.
- cd $src/openmpi-1.4.2
- wget http://www.open-mpi.org/software/ompi/v1.4/downloads/openmpi-1.4.2.tar.gz
- tar -zxvf openmpi-1.4.2.tar.gz
-
- Run configure in the build directory.
- cd $HOME/scratch/build/$TOOLS_FORMAT/openmpi-1.4.2
- ${TOOLS_DIR}/openmpi-1.4.2/src/openmpi-1.4.2/configure --config-cache --prefix=${TOOLS_DIR} CC=gcc CXX=g++ FC=gfortran F77=gfortran CFLAGS="-O2 -fPIC" CXXFLAGS="-O2 -fPIC" FFLAGS="-O2 -fPIC"
-
- Run "make" and "make install".
- make
- make install
-
- Test
- mpicc -show
-
- You should see the gcc compiler being used with the appropriate
- flags to include the OpenMPI headers and libraries.
-
-
-4. FIAT (version 0.3.5 is the most recent version known to work)
-
- Depends on Python.
-
- Download and unpack the tarball.
- cd $HOME/src/fiat-0.3.5
- wget http://www.fenics.org/pub/software/fiat/FIAT-0.3.5.tar.gz
-
- Install using python.
- cd FIAT-0.3.5
- python setup.py install --prefix=$TOOLS_DIR
-
- Test
- python
- import FIAT
-
-
-5. pythia
-
- Depends on Python.
-
- Check out pythia from the publicly accessible CIG SVN repository.
- cd $HOME/src
- svn co http://geodynamics.org/svn/cig/cs/pythia/trunk pythia
-
- Install using python.
- cd pythia
- python setup.py install --prefix=$TOOLS_DIR
-
- Test
- python
- import pyre
-
-
-6. spatialdata
-
- Depends on pythia.
-
- Check out spatialdata from the publicly accessible CIG SVN repository.
- cd $HOME/src
- svn co http://geodynamics.org/svn/cig/cs/spatialdata-0.1/trunk spatialdata-dev
- cd spatialdata-dev
- autoreconf -if
-
- Run configure in the build dir.
- cd $HOME/scratch/build/$TOOLS_FORMAT/spatialdata-dev
- ${HOME}/src/spatialdata/configure --config-cache --enable-swig --enable-testing --enable-pythia --prefix=${TOOLS_DIR} CPPFLAGS="-I${TOOLS_DIR}/include " LDFLAGS="-L${TOOLS_DIR}/lib " CC=icc CXX=icpc CFLAGS="-O2 -fPIC" CXXFLAGS="-O2 -fPIC"
-
- Run "make" and "make install".
- make
- make install
-
- Test
- make check
-
-
-7. PETSc
-
- Checkout the development version of PETSc.
- cd $HOME/src
- hg clone http://petsc.cs.iit.edu/petsc/petsc-dev
- cd petsc-dev/config
- hg clone http://petsc.cs.iit.edu/petsc/BuildSystem BuildSystem
-
- Run configure in the *source* directory.
- cd $HOME/src/petsc-dev
- config/configure.py --PETSC_ARCH=linux_${TOOLS_FORMAT} --with-debugging=0 --with-clanguage=c++ --with-mpi-compilers=1 --with-shared=1 --with-dynamic=1 --with-64-bit-points=1 --with-large-file-io=1 --with-blas-lapack-lib="-L/usr/lib/atlas -llapack_atlas -llapack -latlas -lblas" --with-lgrind=0 --with-chaco=1 --download-chaco=1 --with-parmetis=1 --download-parmetis=1 --with-sieve=1 --with-boost=1 --download-boost=1 --with-ml=1 --download-ml=1
-
- Run "make" and "make test"
- make
- make test
-
-
-8. nemesis
-
- Depends on Python, MPI, pythia.
-
- Check out nemesis from the publicly accessible CIG SVN repository.
- cd $HOME/src
- svn co http://geodynamics.org/svn/cig/cs/nemesis/trunk nemesis-dev
- cd nemesis-dev
- autoreconf -if
-
- Run configure in the build dir.
- cd $HOME/scratch/build/$TOOLS_FORMAT/nemesis-dev
- $HOME/src/nemesis-dev/configure --prefix=${TOOLS_DIR}
-
- Run "make" and "make install".
- make
- make install
-
- Test
- nemesis
- import mpi
-
- Running nemesis should startup Python. Nemesis is an MPI wrapper
- around Python.
-
-
-9. PyLith
-
- Check out PyLith from the publicly accessible CIG SVN repository.
- cd $HOME/src
- svn co http://geodynamics.org/svn/cig/short/3D/PyLith/trunk pylith-dev
- cd pylith-dev
- autoreconf -if
-
- Run configure in the build dir.
- cd $HOME/scratch/build/$TOOLS_FORMAT/pylith-dev
- ${HOME}/src/pylith-dev/configure --config-cache --enable-swig --enable-testing --enable-cubit --prefix=${TOOLS_DIR} CPPFLAGS="-I${TOOLS_DIR}/include " LDFLAGS="-L${TOOLS_DIR}/lib " CC=mpicc CXX=mpiCC CFLAGS="-O2 -fPIC" CXXFLAGS="-O2 -fPIC"
-
- Run "make" and "make install".
- make
- make install
-
- Test
- make check
-
Deleted: short/3D/PyLith/trunk/doc/install/MacBookPro_Aagaard.txt
===================================================================
--- short/3D/PyLith/trunk/doc/install/MacBookPro_Aagaard.txt 2011-04-26 18:00:54 UTC (rev 18292)
+++ short/3D/PyLith/trunk/doc/install/MacBookPro_Aagaard.txt 2011-04-26 18:38:18 UTC (rev 18293)
@@ -1,271 +0,0 @@
-======================================================================
-INSTRUCTIONS FOR INSTALLING PYLITH ON AN INTEL MAC RUNNING OSX 10.5
-======================================================================
-
-NOTE: These installation instructions use the MacPorts package manager
-to install some commonly used packages. MacPorts appears to be a
-better alternative to Fink because packages are updated more
-frequently and there is better coherence among packages. However,
-MacPorts builds all packages from source so installing packages can
-take a long time.
-
-MacPorts places everything in /opt/local. For CIG source code, I
-separate the source code, build directories, and installed code. The
-source code sits in $HOME/src/cig, I build the packages under
-$HOME/scratch/build/cig, and install the packages to $HOME/tools/cig.
-
-I use the bash shell and place all software package environment
-variables in a .bash.tools file that is read by the .bashrc file.
-
-To make things easier, I create environment variables TOOLS_DIR,
-CIG_DIR, TOOLS_FORMAT, and PYTHON_VERSION. The TOOLS_FORMAT variable
-makes it easier to maintain multiple copies of packages built with
-different options (e.g., different compilers and different levels of
-optimization). Note that the python version should match the version
-of Python you will be using. If you don't know the version of python,
-run "python --version".
-
- export TOOLS_DIR=/tools
- export TOOLS_FORMAT=gcc-4.0
- export PYTHON_VERSION=2.5
-
- export CIG_DIR=$HOME/tools/cig/${TOOLS_FORMAT}
- export CIG_INCDIR=${CIG_DIR}/include
- export CIG_LIBDIR=${CIG_DIR}/lib
- PATH=$PATH:${CIG_DIR}/bin
- export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${CIG_LIBDIR}
- export PYTHONPATH=${PYTHONPATH}:${CIG_LIBDIR}/python${PYTHON_VERSION}/site-packages
-
-1. X and Xcode
-
- X and Xcode are on the Apple OSX install disc 1. X is under
- "additional options."
-
-2. Install MacPorts (http://www.macports.org/)
-
-3. Install Porticus (GUI interface to MacPorts)
- (http://porticus.alittledrop.com)
-
-4. Install MacPorts packages
-
- Install the following using Porticus:
-
- autoconf
- automake
- libtool
- subversion
- mercurial
- cppunit
- python25
- py25-numpy
- swig
-
- Install netcdf via the command line so that you can change the default variants:
-
- /opt/local/bin/port install netcdf -dap -netcdf4
-
-5. Install MPICH2 (http://www.mcs.anl.gov/research/projects/mpich2/)
-
- a. Untar the source and then run configure, build, and install.
-
- ./configure --with-arch=Darwin --disable-f90 --enable-css --prefix=${TOOLS_DIR}/mpich2-1.1.1/${TOOLS_FORMAT} --enable-g=none --enable-fast --disable-weak-symbols --enable-shared-libx=osx-gcc
- make
- make install
-
- b. Verify the shared libraries (lib*.dyllib) are created.
-
- c. If any of the dylib files are missing, create them by hand from the
- static libraries.
-
- Note: It is important to specify the full path for the .dylib files.
-
- To create libmpich.dylib:
-
- cd ${TOOLS_DIR}/mpich2-1.1.1/${TOOLS_FORMAT}/lib
- mkdir tmp
- cd tmp
- ar -x ../libmpich.a
- gcc -dynamiclib -single_module -undefined dynamic_lookup -o ${TOOLS_DIR}/mpich2-1.1.1/${TOOLS_FORMAT}/lib/libmpich.dylib *.o
- rm *.o
- cd ..
- rmdir tmp
-
- d. Set environment variables.
-
- export MPI_DIR=$TOOLS_DIR/mpich2-1.1.1/${TOOLS_FORMAT}
- PATH=$PATH:$MPI_DIR/bin
- export MANPATH=$MPI_DIR/man:$MANPATH
- export MPI_INCDIR=$MPI_DIR/include
- export MPI_LIBDIR=$MPI_DIR/lib
- export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${MPI_LIBDIR}
-
-6. Install ParMetis (http://glaros.dtc.umn.edu/gkhome/metis/parmetis/overview)
-
- a. Untar the source and edit the Makefile.in.
- b. Set the CC, COPTIONS, INCDIR, LD, and LIBDIR variables.
-
- CC = gcc
- COPTIONS = -DNDEBUG -fPIC
- INCDIR = -I${MPI_INCDIR}
- LIBDIR = -L${MPI_LIBDIR} -lmpich -lpmpich
-
- c. Edit the ParMETISLib/stdheaders.h file
-
- Comment out the line #include <malloc.h> since this is not a
- standard header file and not present in OS X 10.5.
-
- d. Create shared libraries by hand.
-
- Note: It is important to specify the full path for the .dylib files.
-
- cd ${TOOLS_DIR}/parmetis-3.1/${TOOLS_FORMAT}/lib
- mkdir tmp
- cd tmp
- ar -x ../libmetis.a
- gcc -o ${TOOLS_DIR}/parmetis-3.1/${TOOLS_FORMAT}/lib/libmetis.dylib -dynamiclib -single_module -undefined dynamic_lookup *.o
- rm *
- ar -x ../libparmetis.a
- gcc -o ${TOOLS_DIR}/parmetis-3.1/${TOOLS_FORMAT}/lib/libparmetis.dylib -dynamiclib -single_module -undefined dynamic_lookup *.o
- rm *
- cd ..
- rmdir tmp
-
- e. Copy parmetis.h to the install location.
-
- cp parmetis.h ${TOOLS_DIR}/parmetis-3.1/${TOOLS_FORMAT}/include/
-
- f. Set environment variables.
-
- PARMETIS_DIR=$TOOLS_DIR/parmetis-3.1/${TOOLS_FORMAT}
- export PARMETIS_INCDIR=$PARMETIS_DIR/include
- export PARMETIS_LIBDIR=$PARMETIS_DIR/lib
- export PARMETIS_LIBS="-lparmetis -lmetis"
- export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${PARMETIS_LIBDIR}
-
-7. Install FIAT (http://www.fenics.org/wiki/FIAT)
-
- a. Install FIAT.
-
- python setup.py install --prefix=$TOOLS_DIR/fiat-0.3.1/${TOOLS_FORMAT}
-
- b. Set environment variables.
-
- FIAT_DIR=${TOOLS_DIR}/fiat-0.3.4/${TOOLS_FORMAT}
- export PYTHONPATH=${PYTHONPATH}:${FIAT_DIR}/lib/python${PYTHON_VERSION}/site-packages
-
-8. Install the development version of PETSc
- (http://www-unix.mcs.anl.gov/petsc/petsc-as/)
-
- a. Clone the source repository.
-
- hg clone http://petsc.cs.iit.edu/petsc/petsc-dev
- cd petsc-dev/config
- hg clone http://petsc.cs.iit.edu/petsc/BuildSystem BuildSystem
-
-
- b. Set PETSC_ARCH and PETSC_DIR environment variables.
-
- export PETSC_DIR=${TOOLS_DIR}/petsc-dev
- export PETSC_ARCH=osx_${TOOLS_FORMAT}_debug
-
- c. Configure PETSc, build, and test.
-
- ARCH_FLAGS="--PETSC_ARCH=osx_${TOOLS_FORMAT}_debug --with-debugging=1"
- LANG_FLAGS="--with-clanguage=c++"
- BUILD_FLAGS="--with-mpi-compilers=0 --with-gnu-compilers=1 --with-shared=1 --with-dynamic=1 --with-64-bit-points=1 --with-large-file-io=1 --CC=gcc --CXX=g++"
- MPI_FLAGS="--with-mpi-dir=/sw/tools/mpich2-1.1.1/gcc-4.0 --with-mpi-shared=0"
- OPTIONS="--with-lgrind=0 --download-tetgen"
- PART_FLAGS="--with-chaco=1 --download-chaco=1 --with-parmetis=1 --with-parmetis-dir=/sw/tools/parmetis-3.1/gcc-4.0"
- SIEVE_FLAGS="--with-sieve=1 --with-boost=1 --download-boost=1"
- config/configure.py ${ARCH_FLAGS} ${LANG_FLAGS} ${BUILD_FLAGS} ${MPI_FLAGS} ${OPTIONS} ${PART_FLAGS} ${SIEVE_FLAGS} ${EXTRA_FLAGS}
- make
- make test
-
-9. Install pythia.
-
- a. Download the source code from the SVN repository.
-
- svn co http://geodynamics.org/svn/cig/cs/pythia/trunk pythia
-
- b. Install the software.
-
- python setup.py install --prefix=${CIG_DIR}
-
- c. Set environment variables.
-
- export PYTHIA_INCDIR=${CIG_INCDIR}/pythia-0.8
-
-10. Install nemesis.
-
- a. Download the source code from the SVN repository.
-
- svn co http://geodynamics.org/svn/cig/cs/nemesis/trunk nemesis
-
- b. Create the configure script.
-
- autoreconf -if
-
- c. Run configure, build, and install.
-
- ./configure --prefix=${CIG_DIR} CPPFLAGS="-I${CIG_INCDIR} -I${MPI_INCDIR}" LDFLAGS="-L${CIG_LIBDIR} -L${MPI_LIBDIR}" LIBS="-lpmpich -lmpich" CC=gcc CXX=g++
- make
- make install
-
- If you get an error about the architecture, edit libtool and
- delete "-arch ppc" or "-arch intel", which ever one is not for
- your machine.
-
-11. Install PROJ.4 (http://trac.osgeo.org/proj/)
-
- a. Download the source code AND the datum shifts (proj-datumgrid-1.4.zip).
-
- b. Untar the source code and unzip the datum shifts in the nad directory.
-
- c. Run configure and build.
-
- ./configure --prefix=${TOOLS_DIR}/proj-4.6.1/${TOOLS_FORMAT}
- make
- make install
-
- d. Set environment variables.
-
- PROJ4_DIR=${TOOLS_DIR}/proj-4.6.1/${TOOLS_FORMAT}
- export PROJ4_LIBDIR=${PROJ4_DIR}/lib
- export PROJ4_INCDIR=${PROJ4_DIR}/include
- PATH=${PATH}:${PROJ4_DIR}/bin
- export MANPATH=${MANPATH}:${PROJ4_DIR}/man
-
-12. Install spatialdata.
-
- a. Download the source code from the SVN repository.
-
- svn co http://geodynamics.org/svn/cig/cs/spatialdata-0.1/trunk spatialdata
-
- b. Create the configure script.
-
- autoreconf -if
-
- c. Run configure, build, install, and the unit tests.
-
- ./configure --enable-testing --enable-pythia --prefix=${CIG_DIR} CPPFLAGS="-I${PROJ4_INCDIR} -I${CPPUNIT_INCDIR} -I${CIG_INCDIR}" LDFLAGS="-L${PROJ4_LIBDIR} -L${CPPUNIT_LIBDIR} -L${CIG_LIBDIR} " LIBS="" CC=gcc CXX=g++
- make
- make install
- make check
-
-13. Install PyLith.
-
- a. Download the source code from the SVN repository.
-
- svn co http://geodynamics.org/svn/cig/short/3D/PyLith/trunk pylith
-
- b. Create the configure script.
-
- autoreconf -if
-
- c. Run configure, build, install, and the unit tests.
-
- ./configure --enable-testing --enable-tetgen --enable-cubit --prefix=${CIG_DIR} CPPFLAGS="-I${PROJ4_INCDIR} -I${CPPUNIT_INCDIR} -I${CIG_INCDIR} -I/sw/include" LDFLAGS="-L${PROJ4_LIBDIR} -L${CPPUNIT_LIBDIR} -L${CIG_LIBDIR} -L/sw/lib" LIBS="" CC=gcc CXX=g++ CFLAGS="-g -O" CXXFLAGS="-g -O"
- make
- make install
- make check
-
Deleted: short/3D/PyLith/trunk/doc/install/MacBookPro_Aagaard_bash.sh
===================================================================
--- short/3D/PyLith/trunk/doc/install/MacBookPro_Aagaard_bash.sh 2011-04-26 18:00:54 UTC (rev 18292)
+++ short/3D/PyLith/trunk/doc/install/MacBookPro_Aagaard_bash.sh 2011-04-26 18:38:18 UTC (rev 18293)
@@ -1,48 +0,0 @@
-# Environment variables for Bash Shells associated with Brad Aagaard's
-# install of PyLith on a MacBookPro running OS X 10.5
-
-# General
-export TOOLS_DIR=/tools
-export TOOLS_FORMAT=gcc-4.0
-export PYTHON_VERSION=2.5
-
-# Location for installation of CIG software
-export CIG_DIR=$HOME/tools/cig/${TOOLS_FORMAT}
-export CIG_INCDIR=${CIG_DIR}/include
-export CIG_LIBDIR=${CIG_DIR}/lib
-PATH=$PATH:${CIG_DIR}/bin
-export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${CIG_LIBDIR}
-export PYTHONPATH=${PYTHONPATH}:${CIG_LIBDIR}/python${PYTHON_VERSION}/site-packages
-
-# MPICH2
-export MPI_DIR=$TOOLS_DIR/mpich2-1.1.1/${TOOLS_FORMAT}
-PATH=$PATH:$MPI_DIR/bin
-export MANPATH=$MPI_DIR/man:$MANPATH
-export MPI_INCDIR=$MPI_DIR/include
-export MPI_LIBDIR=$MPI_DIR/lib
-export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${MPI_LIBDIR}
-
-# ParMetis
-PARMETIS_DIR=$TOOLS_DIR/parmetis-3.1/${TOOLS_FORMAT}
-export PARMETIS_INCDIR=$PARMETIS_DIR/include
-export PARMETIS_LIBDIR=$PARMETIS_DIR/lib
-export PARMETIS_LIBS="-lparmetis -lmetis"
-export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${PARMETIS_LIBDIR}
-
-# FIAT
-FIAT_DIR=${TOOLS_DIR}/fiat-0.3.4/${TOOLS_FORMAT}
-export PYTHONPATH=${PYTHONPATH}:${FIAT_DIR}/lib/python${PYTHON_VERSION}/site-packages
-
-# PETSc
-export PETSC_DIR=${TOOLS_DIR}/petsc-dev
-export PETSC_ARCH=osx_${TOOLS_FORMAT}_debug
-
-# Pythia
-export PYTHIA_INCDIR=${CIG_INCDIR}/pythia-0.8
-
-# Proj.4
-PROJ4_DIR=${TOOLS_DIR}/proj-4.6.1/${TOOLS_FORMAT}
-export PROJ4_LIBDIR=${PROJ4_DIR}/lib
-export PROJ4_INCDIR=${PROJ4_DIR}/include
-PATH=${PATH}:${PROJ4_DIR}/bin
-export MANPATH=${MANPATH}:${PROJ4_DIR}/man
Modified: short/3D/PyLith/trunk/doc/install/Makefile.am
===================================================================
--- short/3D/PyLith/trunk/doc/install/Makefile.am 2011-04-26 18:00:54 UTC (rev 18292)
+++ short/3D/PyLith/trunk/doc/install/Makefile.am 2011-04-26 18:38:18 UTC (rev 18293)
@@ -27,15 +27,7 @@
Cluster_CIT-pangu/PyLith.README \
Cluster_CIT-pangu/sample.bashrc \
Cluster_CIT-pangu/sample.bash.tools \
- Cluster_CIT-pangu/sample.pylithapp.cfg \
- Cluster_Rocks-4.3-AMD64.txt \
- Cluster_Rocks-4.3-AMD64_bash.sh \
- Linux_ubuntu-AMD64_Aagaard.txt \
- Linux_ubuntu-AMD64_Aagaard.sh \
- Linux_Fedora8-AMD64_Aagaard.txt \
- Linux_Fedora8-AMD64_Aagaard_bash.sh \
- MacBookPro_Aagaard.txt \
- MacBookPro_Aagaard_bash.sh
+ Cluster_CIT-pangu/sample.pylithapp.cfg
# End of file
Modified: short/3D/PyLith/trunk/doc/install/README
===================================================================
--- short/3D/PyLith/trunk/doc/install/README 2011-04-26 18:00:54 UTC (rev 18292)
+++ short/3D/PyLith/trunk/doc/install/README 2011-04-26 18:38:18 UTC (rev 18293)
@@ -1,66 +1,8 @@
-======================================================================
-OVERVIEW
-======================================================================
+If you are new to PyLith, we recommend using the PyLith binary
+distributions to get up and running quickly. Once you are familiar
+with PyLith and want a custom installation, then we recommend that you
+use the PyLith Installer to build PyLith and its dependencies. The
+PyLith Installer is available on the PyLith website
+http://www.geodynamics.org/cig/software/pylith/. Instructions for how
+to use the installer are bundled in its distribution.
-This directory contains detailed instructions for building PyLith from
-source on several different platforms. You can compile all of the
-software packages from source, but, in most cases, it is much easier
-to make use of package managers to install low-level
-dependencies. Additionally, some hardware vendors supply optimized
-math libraries (BLAS/LAPACK) that will provide better performance than
-generic implementations.
-
-The degree of difficulty of the installation is closely related to how
-many binary packages are available for your platform. Most Linux
-distributions provide package managers that make installing a
-consistent suite of packages very easy. On Darwin systems, the package
-managers do a poor job of maintaining compatibility across
-packages. For example, some Fink packages use Apple gcc while others
-use Fink gcc (these two versions of gcc are not necessarily
-compatible). On Darwin systems, we recommend using MacPorts as your
-package manager. It builds everything from source and generally does a
-better job of maintaining consistency than Fink.
-
-The particular versions of several packages used in the installation
-instructions vary depending on how when the package was installed and
-how often it is updated. Unless otherwise noted, you should be able to
-install the current stable releases and not run into compatibility
-problems.
-
-======================================================================
-INSTRUCTIONS FOR VARIOUS PLATFORMS
-======================================================================
-
-We recommend setting up your source, build, and install directories as
-in the Linux_ubuntu-AMD64_Aagaard.txt, Cluster_CIT-garuda, and
-Cluster_CIT-pangu examples. These are setup for relatively stable
-installations, whereas most of the other examples are setup for
-development work and testing with multiple versions of packages. As a
-result they are unnecessarily complex for most users. The other
-examples do provide details for other systems that you may find
-helpful.
-
-FILE PLATFORM
-
-Linux_ubuntu-AMD64_Aagaard.txt x86_64 desktop (gcc compilers)
-Cluster_CIT-garuda.txt Intel cluster (Intel compilers)
-Cluster_CIT-pangu.txt Intel cluster (Intel compilers)
-MacBookPro_Aagaard.txt Intel Mac (Apple gcc 4.2), MacPorts
-Linux_Fedora8-AMD64_Aagaard.txt x86_64 machine running Fedora 8 (gcc 4.1.2)
-Cluster_Rocks-4.3-AMD64.txt x86_64 cluster running Rocks 4.3 (gcc 3.4)
-
-======================================================================
-BUILDING IN A SEPARATE DIRECTORY FROM THE SOURCE TREE
-======================================================================
-
-Software packages that conform to the GNU build system and use a
-configure script can usually be built in a different directory from
-the source tree. A notable exception to this is MPICH2, which in most
-cases must be built in the source tree. Building in a directory
-separate from the source tree makes it easy to create builds for
-different compilers, optimization levels, etc. To build in a separate
-directory, simply run the configure script from the directory you wish
-to use as the top-level build directory. Run "make", etc. in the build
-directory. In cases where you need to generate the configure script
-via autoreconf, run "autoreconf -if" in the top-level source
-directory.
More information about the CIG-COMMITS
mailing list