I have no idea where all those 1's came from!
This commit was SVN r23852.
This commit is contained in:
Jeff Squyres
parent
d7161a2b65
commit
984844b261
202
INSTALL
202
INSTALL
@ -1,102 +1,102 @@
|
||||
Copyright (c) 2004-2005 The Trustees of Indiana University and Indiana
|
||||
1 University Research and Technology
|
||||
1 Corporation. All rights reserved.
|
||||
1Copyright (c) 2004-2005 The University of Tennessee and The University
|
||||
1 of Tennessee Research Foundation. All rights
|
||||
1 reserved.
|
||||
1Copyright (c) 2004-2005 High Performance Computing Center Stuttgart,
|
||||
1 University of Stuttgart. All rights reserved.
|
||||
1Copyright (c) 2004-2005 The Regents of the University of California.
|
||||
1 All rights reserved.
|
||||
1Copyright (c) 2008-2010 Cisco Systems, Inc. All rights reserved.
|
||||
1$COPYRIGHT$
|
||||
1
|
||||
1Additional copyrights may follow
|
||||
1
|
||||
1$HEADER$
|
||||
1
|
||||
1
|
||||
1For More Information
|
||||
1====================
|
||||
1
|
||||
1This file is a *very* short overview of building and installing Open
|
||||
1MPI, and building MPI applications. Much more information is
|
||||
1available on the Open MPI web site (e.g., see the FAQ section):
|
||||
1
|
||||
1 http://www.open-mpi.org/
|
||||
1
|
||||
1
|
||||
1Developer Builds
|
||||
1================
|
||||
1
|
||||
1If you have checked out a DEVELOPER'S COPY of Open MPI (i.e., you
|
||||
1checked out from subversion), you should read the HACKING file before
|
||||
1attempting to build Open MPI. You must then run:
|
||||
1
|
||||
1shell$ ./autogen.pl
|
||||
1
|
||||
1You will need very recent versions of GNU Autoconf, Automake, and
|
||||
1Libtool. If autogen.pl fails, read the HACKING file. If anything
|
||||
1else fails, read the HACKING file. Finally, we suggest reading the
|
||||
1HACKING file.
|
||||
1
|
||||
1*** NOTE: Developer's copies of Open MPI typically include a large
|
||||
1performance penalty at run-time because of extra debugging overhead.
|
||||
1
|
||||
1
|
||||
1User Builds
|
||||
1===========
|
||||
1
|
||||
1Building Open MPI is typically a combination of running "configure"
|
||||
1and "make". Execute the following commands to install the Open MPI
|
||||
1system from within the directory at the top of the tree:
|
||||
1
|
||||
1shell$ ./configure --prefix=/where/to/install
|
||||
1[...lots of output...]
|
||||
1shell$ make all install
|
||||
1
|
||||
1If you need special access to install, then you can execute "make
|
||||
1all" as a user with write permissions in the build tree, and a
|
||||
1separate "make install" as a user with write permissions to the
|
||||
1install tree.
|
||||
1
|
||||
1Compiling support for various networks or other specific hardware may
|
||||
1require additional command ling flags when running configure. See the
|
||||
1README file for more details. Note that VPATH builds are fully
|
||||
1supported. For example:
|
||||
1
|
||||
1shell$ gtar zxf openmpi-X.Y.Z.tar.gz
|
||||
1shell$ cd openmpi-X.Y.Z
|
||||
1shell$ mkdir build
|
||||
1shell$ cd build
|
||||
1shell$ ../configure ...your options...
|
||||
1[...lots of output...]
|
||||
1shell$ make all install
|
||||
1
|
||||
1Parallel builds are also supported (although some versions of "make",
|
||||
1such as GNU make, will only use the first target listed on the command
|
||||
1line when executable parallel builds). For example (assume GNU make):
|
||||
1
|
||||
1shell$ make -j 4 all
|
||||
1[...lots of output...]
|
||||
1shell$ make install
|
||||
1
|
||||
1Parallel make is generally only helpful in the build phase; the
|
||||
1installation process is mostly serial and does not benefit much from
|
||||
1parallel make.
|
||||
1
|
||||
1
|
||||
1Compiling MPI Applications
|
||||
1==========================
|
||||
1
|
||||
1MPI applications should be compiled using the Open MPI "wrapper"
|
||||
1compilers:
|
||||
1
|
||||
1C programs: mpicc your-code.c
|
||||
1C++ programs: mpiCC your-code.cc or
|
||||
1 mpic++ your-code.cc (for case-insensitive filesystems)
|
||||
1F77 programs: mpif77 your-code.f
|
||||
1F90 programs: mpif90 your-code.f90
|
||||
1
|
||||
1These compilers simply add various command line flags (such as -lmpi)
|
||||
1and invoke a back-end compiler; they are not compilers in themselves.
|
||||
University Research and Technology
|
||||
Corporation. All rights reserved.
|
||||
Copyright (c) 2004-2005 The University of Tennessee and The University
|
||||
of Tennessee Research Foundation. All rights
|
||||
reserved.
|
||||
Copyright (c) 2004-2005 High Performance Computing Center Stuttgart,
|
||||
University of Stuttgart. All rights reserved.
|
||||
Copyright (c) 2004-2005 The Regents of the University of California.
|
||||
All rights reserved.
|
||||
Copyright (c) 2008-2010 Cisco Systems, Inc. All rights reserved.
|
||||
$COPYRIGHT$
|
||||
|
||||
Additional copyrights may follow
|
||||
|
||||
$HEADER$
|
||||
|
||||
|
||||
For More Information
|
||||
====================
|
||||
|
||||
This file is a *very* short overview of building and installing Open
|
||||
MPI, and building MPI applications. Much more information is
|
||||
available on the Open MPI web site (e.g., see the FAQ section):
|
||||
|
||||
http://www.open-mpi.org/
|
||||
|
||||
|
||||
Developer Builds
|
||||
================
|
||||
|
||||
If you have checked out a DEVELOPER'S COPY of Open MPI (i.e., you
|
||||
checked out from subversion), you should read the HACKING file before
|
||||
attempting to build Open MPI. You must then run:
|
||||
|
||||
shell$ ./autogen.pl
|
||||
|
||||
You will need very recent versions of GNU Autoconf, Automake, and
|
||||
Libtool. If autogen.pl fails, read the HACKING file. If anything
|
||||
else fails, read the HACKING file. Finally, we suggest reading the
|
||||
HACKING file.
|
||||
|
||||
*** NOTE: Developer's copies of Open MPI typically include a large
|
||||
performance penalty at run-time because of extra debugging overhead.
|
||||
|
||||
|
||||
User Builds
|
||||
===========
|
||||
|
||||
Building Open MPI is typically a combination of running "configure"
|
||||
and "make". Execute the following commands to install the Open MPI
|
||||
system from within the directory at the top of the tree:
|
||||
|
||||
shell$ ./configure --prefix=/where/to/install
|
||||
[...lots of output...]
|
||||
shell$ make all install
|
||||
|
||||
If you need special access to install, then you can execute "make
|
||||
all" as a user with write permissions in the build tree, and a
|
||||
separate "make install" as a user with write permissions to the
|
||||
install tree.
|
||||
|
||||
Compiling support for various networks or other specific hardware may
|
||||
require additional command ling flags when running configure. See the
|
||||
README file for more details. Note that VPATH builds are fully
|
||||
supported. For example:
|
||||
|
||||
shell$ gtar zxf openmpi-X.Y.Z.tar.gz
|
||||
shell$ cd openmpi-X.Y.Z
|
||||
shell$ mkdir build
|
||||
shell$ cd build
|
||||
shell$ ../configure ...your options...
|
||||
[...lots of output...]
|
||||
shell$ make all install
|
||||
|
||||
Parallel builds are also supported (although some versions of "make",
|
||||
such as GNU make, will only use the first target listed on the command
|
||||
line when executable parallel builds). For example (assume GNU make):
|
||||
|
||||
shell$ make -j 4 all
|
||||
[...lots of output...]
|
||||
shell$ make install
|
||||
|
||||
Parallel make is generally only helpful in the build phase; the
|
||||
installation process is mostly serial and does not benefit much from
|
||||
parallel make.
|
||||
|
||||
|
||||
Compiling MPI Applications
|
||||
==========================
|
||||
|
||||
MPI applications should be compiled using the Open MPI "wrapper"
|
||||
compilers:
|
||||
|
||||
C programs: mpicc your-code.c
|
||||
C++ programs: mpiCC your-code.cc or
|
||||
mpic++ your-code.cc (for case-insensitive filesystems)
|
||||
F77 programs: mpif77 your-code.f
|
||||
F90 programs: mpif90 your-code.f90
|
||||
|
||||
These compilers simply add various command line flags (such as -lmpi)
|
||||
and invoke a back-end compiler; they are not compilers in themselves.
|
||||
|
||||
Loading…
Reference in New Issue
Block a user