Configure options for the F95 NAG compiler:

Switch(es)		Reason			Result
---------		------			------         

-f95nag			f95 NAG compiler is	mpif77 invokes f95 nag 
			at the top of your	mpif90 invokes f90
			path			(if one was located)

-f95nag			f95 NAG compiler is	mpif77 invokes f95 nag
-fc=<path of f95 NAG>	not at the top of your	mpif90 invokes f90
			path			(if one was located)

-f95nag			f90 compiler to be	mpif77 invokes f95 nag
-f90=<path of f95 NAG>	f95 NAG			mpif90 invokes f95 nag
(use -fc as directed
 above)

Configure options for the F90 NAG compiler:

Switch(es)		Reason			Result
---------		------			------         

-f90nag			f90 NAG compiler is	mpif77 invokes f90 nag
			at the top of your	mpif90 not configured
			path

-f90nag			f90 NAG compiler is	mpif77 invokes f90 nag
-fc=<path of f95 NAG>	not at the top of	mpif90 not configured
			your path

-f90nag			f90 compiler to be	mpif77 invokes f90 nag
-f90=<path of f90 NAG>	f90 NAG compiler	mpif90 invokes f90 nag
(use -fc as directed
 above)

Question:
What happens if you want to have your mpif77 script invoke your f95 NAG 
compiler and your mpif90 script invoke your f90 compiler located in
'usr/bin'?  For example:

	configure -f95nag -fc=<path of f95 NAG> -f90=/usr/bin/f90

Currently, configure only determines command line argument handling for the
'fc' compiler.  When configuring with the -f95nag switch, the 'fc' compiler 
is determined to be the f95 NAG compiler.  MPICH does not maintain multiple
Fortran libraries.  If the chosen f90 compiler handles command line arguments
differently than the f95 NAG compiler, then the following error will occur:

	`m pi_init_':
	initf.o(.text+0xf): undefined reference to `mpir_iargc_'
	initf.o(.text+0xc0): undefined reference to `mpir_getarg_'

We are currently working on ways to improve MPICH to overcome issues resulting
from configuring with multiple Fortran compilers.