<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#99ffff" text="#000099">
Thank you very much, Pavan! I'm not really a command line user - I
assume this will cause MPICH to compile with g95 and also to use g95
when compiling other programs to run under MPI. I'm not sure of the
syntax of the "&&" command - is that causing it to run make
with the previous line as input?<br>
<br>
Thank You Again!!<br>
Patti<br>
<br>
Pavan Balaji wrote:
<blockquote cite="mid47F92643.7080906@mcs.anl.gov" type="cite"><br>
You can force MPICH2 to use g95 by setting environment variables at
configure time:
<br>
<br>
$ F77=/path/to/g95 F90=/path/to/g95 ./configure
--prefix=/some/place/mpich2-install
<br>
<br>
$ make && make install
<br>
<br>
-- Pavan
<br>
<br>
On 04/06/2008 02:08 PM, PattiMichelle wrote:
<br>
<blockquote type="cite">Hello Everyone :-)
<br>
I have installed g95 on my SuSE 10.2 x86_64 dual core system and want
to use MPICH2 to compile a certain parallel-enabled fortran code. I
looked at the MPICH2 configure script file(s) and noticed entries for
g95, so as long as I build the code from source (rather than installing
from an .rpm file), then it should detect g95, correct? I'm not sure
*how* it actually detects it because g95 can be installed pretty much
anywhere according to the g95 docs. I have set (in bashrc):
<br>
<br>
alias f77=g95
<br>
alias f90=g95
<br>
<br>
...and it seems to work...
<br>
<br>
patti@PattiDesktop:~> f77
<br>
g95: no input files
<br>
patti@PattiDesktop:~> f90
<br>
g95: no input files
<br>
patti@PattiDesktop:~>
<br>
<br>
...and have removed gfortran so the only fortran on my system *should*
be g95... I would appreciate a comment or three as to whether or not I
need to set anything else before running configure / make / make
install on the MPICH2 source.
<br>
<br>
THANK YOU!!
<br>
PattiMichelle Sheaffer
<br>
<br>
<br>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>