27
Q1:
Enter the AMSO1100 build path:
This is the full path to the AMSO1100 source code. Ammaso’s MPICH
implementation needs access to some files distributed in the AMSO1100
directory to correctly compile. This defaults to ../AMSO1100.
Q2:
Base directory to install mpich [/usr/opt/ammasso]:
This is the directory Ammasso’s MPICH implementation will be installed into.
Q3:
Enter path to c compiler [/usr/bin/gcc]:
This is the path to the C compiler that will be used to build MPICH C
programs.
Q4:
Enter path to c++ compiler [/usr/bin/g++]:
This is the path to the C++ compiler that will be used when building C++
MPICH programs.
Q5:
Enter path to fortran 77 compiler (enter ‘none’ to skip)
[/usr/bin/g77]:
This is the path to the FORTRAN 77 compiler that will be used when building
FORTRAN 77 MPICH programs.
Q6:
Build shared libraries (y or n)? [no]
Enabling this option builds shared libraries (.
so
files) for use by applications.
If this is left to the default of ’n’, only the static libraries (.
a
files) are built.
Q7:
Enter path to remote shell [/usr/bin/rsh]
Argonne, MPICH, from which Ammasso MPICH derives, assumes the use of
the BSD
rsh(1)
command, hence Ammasso’s choice to leave that as the
default. However, best security practices recommend a stronger system; such
as Secure Shell and Ammasso recommends sites consider its use.
This is the full pathname to the command that you want to use to launch
applications on cluster nodes. The default Ammasso MPICH will use the
rsh(1)
command. This is typically installed as
/usr/bin/rsh
.
The
Secure Shell
, or
ssh(1)
command is traditionally installed as
/usr/bin/ssh
. A properly configured Secure Shell system will provide
the needed mechanism. No matter what remote shell is chosen, Ammasso’s
MPICH requires that programs executed via the remote shell operate without
the need for the user to enter a password.
Q8:
Build mpich using a FORTRAN 90 compiler (y or n)? [no]