Hi,<br>please check the config log in detail with options passed as export FC=gfortran. It has not created mpif90 nor mpif77. Where things are going wrong?<br><br><div class="gmail_quote">On Wed, Sep 14, 2011 at 10:46 PM, Gus Correa <span dir="ltr"><<a href="mailto:gus@ldeo.columbia.edu">gus@ldeo.columbia.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">akshar bhosale wrote:<br>
> No, it is not bug because the same code is running in other machine.<br>
<br></div>
Hi Akshar<br>
<br>
The devilish thing with MPI programs is that success in one machine,<br>
or with a certain number of processes, or in a specific network,<br>
doesn't mean that the program is bug free.<br>
It may still fail in a different environment.<br>
[Actually, even sequential programs are like that.<br>
In one computer, with a certain compiler, etc,<br>
say, a segmentation fault may not appear, may not break<br>
at run time, but in another machine/OS/compiler it may.]<br>
"It works" is a necessary but not sufficient condition for<br>
"being bug-free"<br>
<br>
The error message you've got is pretty clear.<br>
There is a deadlock.<br>
See Pavan's suggestion in his email.<div class="im"><br>
<br>
I hope this helps,<br>
Gus Correa<br>
<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
Can something be done so that even if mpif77 does not get created,<br>
no issues; but mpif90 (mpich-1.2.7p1, gfortran) should get created<br>
and fortran helloworld should run without any issues.<br>
<br>
Thank you<br>
Akshar.<br>
<br></div><div><div></div><div class="h5">
On Tue, Sep 13, 2011 at 10:39 PM, Gus Correa <<a href="mailto:gus@ldeo.columbia.edu" target="_blank">gus@ldeo.columbia.edu</a> <mailto:<a href="mailto:gus@ldeo.columbia.edu" target="_blank">gus@ldeo.columbia.edu</a>><u></u>> wrote:<br>
Hi Akshar<br>
<br>
It sounds as a bug in the program,<br>
which causes a deadlock, not a problem with MPICH2.<br>
Your error message:<br>
<br>
> MPID_Send(57): DEADLOCK: attempting to send a message to the local<br>
> process without a prior matching receive<br>
If you post the code, the list may help you.<br>
<br>
<br>
Gus Correa<br>
<br>
<br>
akshar bhosale wrote:<br>
<br>
sorry for not answering why not mpich2.<br>
We have tried to compile our code using mpich2, it compiles but<br>
while running the executable generated, it runs and in between<br>
it comes out giving some mpi send error. The code compiled with<br>
mpif90 (mpich-1.2.7p1) using gfortran on other machine runs fine.<br>
Error is as follows:<br>
<br>
#######<br>
3 aft MPI_SEND 2 7 2 0<br>
3 call MPI_SEND 2 8 2 0<br>
3 aft MPI_SEND 2 8 2 0<br>
3 call MPI_SEND 2 9 2 0<br>
3 aft MPI_SEND 2 9 2 0<br>
3 call MPI_SEND 2 10 2 0<br>
3 aft MPI_SEND 2 10 2 0<br>
3 call MPI_SEND 3 1 3 0<br>
[cli_3]: aborting job:<br>
Fatal error in MPI_Send: Other MPI error, error stack:<br>
MPI_Send(175): MPI_Send(buf=0x2aaab2af2018, count=1,<br>
dtype=USER<vector>, dest=3, tag=30003, MPI_COMM_WORLD) failed<br>
MPID_Send(57): DEADLOCK: attempting to send a message to the<br>
local process without a prior matching receive<br>
###############<br>
<br>
-akshar<br>
<br>
On Tue, Sep 13, 2011 at 10:02 PM, akshar bhosale<br>
<<a href="mailto:akshar.bhosale@gmail.com" target="_blank">akshar.bhosale@gmail.com</a> <mailto:<a href="mailto:akshar.bhosale@gmail.com" target="_blank">akshar.bhosale@gmail.<u></u>com</a>><br>
<mailto:<a href="mailto:akshar.bhosale@gmail." target="_blank">akshar.bhosale@gmail.</a>_<u></u>_com<br>
<mailto:<a href="mailto:akshar.bhosale@gmail.com" target="_blank">akshar.bhosale@gmail.<u></u>com</a>>>> wrote:<br>
<br>
thanks for reply.<br>
<br>
Goal is to generate mpif90 using mpich-1.2.7p1 using gfortran<br>
which<br>
will generate executable from our fortran code.<br>
<br>
source files to be compiled are .f and .f90 files.<br>
<br>
f2c flag is given because mp[if90 was not getting generated. no<br>
other reason. we want mpif90.<br>
<br>
Now we have tried giving only FC=gfortran and no other flag of<br>
option except prefix, but still it is not generating mpif90<br>
nor mpif77.<br>
<br>
mpif90 generated by using [export F90=fortran;F90FLAGS="-ff2c".]<br>
options if tries to compile our code, it throws error<br>
<br>
<br>
<path to mpif90>/mpif90 -f90=gfortran -Wl -o ../output_code.x<br>
set.o<br>
inp.o otp.o bvsol.o user_kg.o mpi_util.o mpi_communication.o<br>
mpi_memalloc.o driver.o rxn.o advdi_1d_finitediff_mf.o<br>
aq_lib.o \<br>
-L/ioapi/Linux2_x86_64gfort -lioapi<br>
-L/np_cs/netcdf/INSTALL/lib -lnetcdf -L/usr/lib64/<br>
-lgomp /np_cs/lapack/lapack-3.2.1/__<u></u>lapack_LINUX.a<br>
/np_cs/lapack/lapack-3.2.1/__<u></u>blas_LINUX.a<br>
<br>
/build/lib/libmpich.a(farg.o): In function `mpir_iargc__':<br>
farg.f:(.text+0x6): undefined reference to `f__xargc'<br>
/build/lib/libmpich.a(farg.o): In function `mpir_getarg__':<br>
farg.f:(.text+0x38): undefined reference to `getarg_'<br>
collect2: ld returned 1 exit status<br>
make: *** [../output_code.x] Error 1<br>
<br>
-akshar<br>
<br>
<br>
<br>
<br>
<br>
<br>
On Tue, Sep 13, 2011 at 8:52 PM, Gus Correa<br>
<<a href="mailto:gus@ldeo.columbia.edu" target="_blank">gus@ldeo.columbia.edu</a> <mailto:<a href="mailto:gus@ldeo.columbia.edu" target="_blank">gus@ldeo.columbia.edu</a>><br>
<mailto:<a href="mailto:gus@ldeo.columbia.edu" target="_blank">gus@ldeo.columbia.edu</a><br>
<mailto:<a href="mailto:gus@ldeo.columbia.edu" target="_blank">gus@ldeo.columbia.edu</a>><u></u>>__> wrote:<br>
<br>
Hi Pavan and Akshar<br>
<br>
I see, it's MPICH-1.<br>
May I ask why?<br>
<br>
Would a workaround perhaps be to build only mpif77 (no<br>
mpif90),<br>
replace 'use mpi' by '#include "mpif.h"' in the<br>
application code,<br>
and recompile it with mpif77?<br>
<br>
I wonder if -ff2c works at all with Fortran90.<br>
(See man page detail below.)<br>
<br>
Anyway, I remember that there were complaints of runtime<br>
errors (P4 errors) with mpich-1,<br>
reported on this and other mailing lists,<br>
when running on current Linux kernels.<br>
Even with simple codes like the cpi example.<br>
Using MPICH-1 may be an uphill battle.<br>
<br>
I hope this helps,<br>
Gus Correa<br>
<br>
>From man gfortran (4.1.2):<br>
<br>
-ff2c<br>
Generate code designed to be compatible with code<br>
generated by g77 and f2c.<br>
<br>
The calling conventions used by g77 (originally<br>
implemented in f2c) require functions that return type<br>
default<br>
"REAL" to actually return the C type<br>
"double", and functions that return type<br>
"COMPLEX" to<br>
return the values via an extra argument in the calling<br>
sequence<br>
that points to where to store the<br>
return value. Under the default GNU calling<br>
conventions, such functions simply return their results<br>
as they<br>
would in GNU C -- default "REAL" functions<br>
return the C type "float", and "COMPLEX" functions<br>
return the GNU C type "complex". Additionally, this option<br>
implies the -fsecond-underscore option,<br>
unless -fno-second-underscore is explicitly<br>
requested.<br>
<br>
This does not affect the generation of code that<br>
interfaces with the libgfortran library.<br>
<br>
Caution: It is not a good idea to mix Fortran code<br>
compiled with "-ff2c" with code compiled with the default<br>
"-fno-f2c" calling conventions as, calling<br>
"COMPLEX" or default "REAL" functions between<br>
program<br>
parts which were compiled with different calling conventions<br>
will break at execution time.<br>
<br>
Caution: This will break code which passes<br>
intrinsic<br>
functions of type default "REAL" or "COMPLEX" as actual<br>
arguments, as the library implementations<br>
use the -fno-f2c calling conventions.<br>
<br>
<br>
<br>
<br>
Pavan Balaji wrote:<br>
<br>
<br>
Gus: He doesn't want to use MPICH2. He's using MPICH-1.<br>
<br>
-- Pavan<br>
<br>
On 09/13/2011 09:51 AM, Gus Correa wrote:<br>
<br>
Hi Akshar<br>
<br>
Maybe the F90FLAGS="-ff2c" flag is causing the<br>
problem?<br>
What if you remove it and use gfortran for F77<br>
and FC?<br>
<br>
<br>
Also, my 'configure -help' (a bit old, MPICH2<br>
1.3.2p1)<br>
mentions FC, not F90, as the environment variable<br>
to be set.<br>
<br>
For what it is worth, MPICH2 builds fine for us, with<br>
gcc, g++ and gfortran (for F77 and FC).<br>
<br>
My two cents,<br>
Gus Correa<br>
<br>
akshar bhosale wrote:<br>
<br>
Hi,<br>
<br>
If i specify F77 anf F90 as gfortran, it<br>
doesn't<br>
create mpif90 and<br>
mpif77 at all.<br>
Please see attached config log<br>
If i specify F90=gfortran and<br>
F90FLAGS="-ff2c", the<br>
it creates mpif90<br>
and mpif77 but is generating below issue.<br>
Kindly help.<br>
-akshar<br>
<br>
On Tue, Sep 13, 2011 at 9:46 AM, Rajeev<br>
Thakur<<a href="mailto:thakur@mcs.anl.gov" target="_blank">thakur@mcs.anl.gov</a><br>
<mailto:<a href="mailto:thakur@mcs.anl.gov" target="_blank">thakur@mcs.anl.gov</a>> <mailto:<a href="mailto:thakur@mcs.anl.gov" target="_blank">thakur@mcs.anl.gov</a><br>
<mailto:<a href="mailto:thakur@mcs.anl.gov" target="_blank">thakur@mcs.anl.gov</a>>><br>
<mailto:<a href="mailto:thakur@mcs.anl.gov" target="_blank">thakur@mcs.anl.gov</a><br>
<mailto:<a href="mailto:thakur@mcs.anl.gov" target="_blank">thakur@mcs.anl.gov</a>><br>
<mailto:<a href="mailto:thakur@mcs.anl.gov" target="_blank">thakur@mcs.anl.gov</a><br>
<mailto:<a href="mailto:thakur@mcs.anl.gov" target="_blank">thakur@mcs.anl.gov</a>>>>> wrote:<br>
<br>
In the configure step, if you specify<br>
both F77<br>
and F90 as gfortran,<br>
it should work.<br>
<br>
Rajeev<br>
<br>
On Sep 12, 2011, at 9:49 PM, akshar<br>
bhosale wrote:<br>
<br>
> Hi,<br>
> thanks.<br>
> but, in case of mpicc, it can be ignored,<br>
but in case of mpif90,<br>
it is still an issue.<br>
> e.g. hello_mpi.f90 program<br>
> ####################<br>
> program main<br>
> use mpi<br>
> !<br>
> ! implicit none<br>
> !<br>
> integer error<br>
> integer id<br>
> integer p<br>
> real ( kind = 8 ) wtime<br>
> !<br>
> ! Initialize MPI.<br>
> !<br>
> call MPI_Init ( error )<br>
> !<br>
> ! Get the number of processes.<br>
> !<br>
> call MPI_Comm_size ( MPI_COMM_WORLD, p,<br>
error )<br>
><br>
> !<br>
> ! Get the individual process ID.<br>
> !<br>
> call MPI_Comm_rank (<br>
MPI_COMM_WORLD, id,<br>
error )<br>
> !<br>
> ! Print a message.<br>
> !<br>
> if ( id == 0 ) then<br>
><br>
> wtime = MPI_Wtime ( )<br>
><br>
> write ( *, '(a)' ) ' '<br>
> write ( *, '(a)' ) 'HELLO_MPI -<br>
Master<br>
process:'<br>
> write ( *, '(a)' ) '<br>
FORTRAN90/MPI version'<br>
> write ( *, '(a)' ) ' '<br>
> write ( *, '(a)' ) ' An MPI test<br>
program.'<br>
> write ( *, '(a)' ) ' '<br>
> write ( *, '(a,i8)' ) ' The<br>
number of<br>
processes is ', p<br>
> write ( *, '(a)' ) ' '<br>
><br>
> end if<br>
><br>
> write ( *, '(a)' ) ' '<br>
> write ( *, '(a,i8,a)' ) ' Process<br>
', id,<br>
' says "Hello, world!"'<br>
><br>
> if ( id == 0 ) then<br>
><br>
> write ( *, '(a)' ) ' '<br>
> write ( *, '(a)' ) 'HELLO_MPI -<br>
Master<br>
process:'<br>
> write ( *, '(a)' ) ' Normal end of<br>
execution: "Goodbye,<br>
world!".'<br>
><br>
> wtime = MPI_Wtime ( ) - wtime<br>
> write ( *, '(a)' ) ' '<br>
> write ( *, '(a,g14.6,a)' ) ' Elapsed<br>
wall clock time = ',<br>
wtime, ' seconds.'<br>
><br>
> end if<br>
> !<br>
> ! Shut down MPI.<br>
> !<br>
> call MPI_Finalize ( error )<br>
><br>
> stop<br>
> end<br>
> ############################<br>
><br>
> $ ../../../build/bin/mpif90 hello_mpi.f90<br>
><br>
/scratch1/np_cs/trial1/build/_<u></u>___lib/libmpich.a(farg.o):<br>
In function<br>
`mpir_iargc__':<br>
> farg.f:(.text+0x6): undefined<br>
reference to<br>
`f__xargc'<br>
><br>
/scratch1/np_cs/trial1/build/_<u></u>___lib/libmpich.a(farg.o):<br>
In function<br>
`mpir_getarg__':<br>
> farg.f:(.text+0x38): undefined<br>
reference to<br>
`getarg_'<br>
> collect2: ld returned 1 exit status<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> On Mon, Sep 12, 2011 at 9:42 AM,<br>
Rajeev Thakur<br>
<<a href="mailto:thakur@mcs.anl.gov" target="_blank">thakur@mcs.anl.gov</a><br>
<mailto:<a href="mailto:thakur@mcs.anl.gov" target="_blank">thakur@mcs.anl.gov</a>><br></div></div>
<mailto:<a href="mailto:thakur@mcs.anl.gov" target="_blank">thakur@mcs.anl.gov</a><div><div></div><div class="h5"><br>
<mailto:<a href="mailto:thakur@mcs.anl.gov" target="_blank">thakur@mcs.anl.gov</a>>><_<u></u>_mailto:<a href="mailto:tha__kur@mcs.anl.gov" target="_blank">tha__kur@mcs.anl.gov</a><br>
<mailto:<a href="mailto:tha__kur@mcs.anl.gov" target="_blank">tha__kur@mcs.anl.gov</a>><br>
<br>
<mailto:<a href="mailto:thakur@mcs.anl.gov" target="_blank">thakur@mcs.anl.gov</a><br>
<mailto:<a href="mailto:thakur@mcs.anl.gov" target="_blank">thakur@mcs.anl.gov</a>>>>> wrote:<br>
> Ignore that. Compile a real program<br>
as mpicc<br>
foo.c.<br>
><br>
> On Sep 11, 2011, at 8:38 PM, akshar<br>
bhosale<br>
wrote:<br>
><br>
> > Hi,<br>
> > thank you for reply.<br>
> ><br>
> > I tried to install it make it using<br>
following options now and i<br>
get following error with undefined<br>
reference to<br>
main. options given<br>
while configuring the same are :<br>
> > export F90=fortran;F90FLAGS="-ff2c".<br>
> > but error of undefined reference<br>
to main<br>
is observed in every<br>
executable like :<br>
> ><br>
> > ./mpicc -v<br>
> > mpicc for 1.2.7 (release) of :<br>
2005/06/22<br>
16:33:49<br>
> > Using built-in specs.<br>
> > Target: x86_64-redhat-linux<br>
> > Configured with: ../configure<br>
--prefix=/usr<br>
--mandir=/usr/share/man<br>
--infodir=/usr/share/info --enable-shared<br>
--enable-threads=posix<br>
--enable-checking=release<br>
--with-system-zlib<br>
--enable-__cxa_atexit<br>
--disable-libunwind-exceptions<br>
--enable-libgcj-multifile<br>
--enable-languages=c,c++,objc,<u></u>____obj-c++,java,fortran,ada<br>
--enable-java-awt=gtk --disable-dssi<br>
--disable-plugin<br>
--with-java-home=/usr/lib/jvm/<u></u>____java-1.4.2-gcj-1.4.2.0/jre<br>
--with-cpu=generic --host=x86_64-redhat-linux<br>
> > Thread model: posix<br>
> > gcc version 4.1.2 20080704 (Red<br>
Hat 4.1.2-50)<br>
> > /usr/libexec/gcc/x86_64-____<u></u>redhat-linux/4.1.2/collect2<br>
--eh-frame-hdr -m elf_x86_64 --hash-style=gnu<br>
-dynamic-linker<br>
/lib64/ld-linux-x86-64.so.2<br>
/usr/lib/gcc/x86_64-redhat-___<u></u>_linux/4.1.2/../../../../<u></u>lib64/____crt1.o<br>
/usr/lib/gcc/x86_64-redhat-___<u></u>_linux/4.1.2/../../../../<u></u>lib64/____crti.o<br>
/usr/lib/gcc/x86_64-redhat-___<u></u>_linux/4.1.2/crtbegin.o<br>
-L/scratch1/np_cs/trial2/____<u></u>build/lib<br>
-L/opt/intel/mkl/<a href="http://10.2.2.025/____lib/em64t" target="_blank">10.2.2.025/__<u></u>__lib/em64t</a><br>
<<a href="http://10.2.2.025/__lib/em64t" target="_blank">http://10.2.2.025/__lib/em64t</a><u></u>><br>
<<a href="http://10.2.2.025/lib/em64t" target="_blank">http://10.2.2.025/lib/em64t</a>><<u></u>__<a href="http://10.2.2.025/__lib/em64t" target="_blank">http://10.2.2.025/__lib/<u></u>em64t</a><br>
<br>
<<a href="http://10.2.2.025/lib/em64t" target="_blank">http://10.2.2.025/lib/em64t</a>>><br>
-L/opt/intel/mkl/<a href="http://10.2.2.025/____lib/em64t" target="_blank">10.2.2.025/__<u></u>__lib/em64t</a><br>
<<a href="http://10.2.2.025/__lib/em64t" target="_blank">http://10.2.2.025/__lib/em64t</a><u></u>><br>
<<a href="http://10.2.2.025/lib/em64t" target="_blank">http://10.2.2.025/lib/em64t</a>><<u></u>__<a href="http://10.2.2.025/__lib/em64t" target="_blank">http://10.2.2.025/__lib/<u></u>em64t</a><br>
<br>
<<a href="http://10.2.2.025/lib/em64t" target="_blank">http://10.2.2.025/lib/em64t</a>>><br>
-L/usr/lib/gcc/x86_64-redhat-_<u></u>___linux/4.1.2<br>
-L/usr/lib/gcc/x86_64-redhat-_<u></u>___linux/4.1.2<br>
-L/usr/lib/gcc/x86_64-redhat-_<u></u>___linux/4.1.2/../../../../<u></u>lib64<br>
-L/lib/../lib64 -L/usr/lib/../lib64 -lmpich<br>
-lpthread -lrt -lgcc<br>
--as-needed -lgcc_s --no-as-needed -lc -lgcc<br>
--as-needed -lgcc_s<br>
--no-as-needed<br>
/usr/lib/gcc/x86_64-redhat-___<u></u>_linux/4.1.2/crtend.o<br>
/usr/lib/gcc/x86_64-redhat-___<u></u>_linux/4.1.2/../../../../<u></u>lib64/____crtn.o<br>
> ><br>
/usr/lib/gcc/x86_64-redhat-___<u></u>_linux/4.1.2/../../../../<u></u>lib64/____crt1.o:<br>
In<br>
function `_start':<br>
> > (.text+0x20): undefined reference<br>
to `main'<br>
> > collect2: ld returned 1 exit status<br>
> ><br>
> > ./mpif90 -v<br>
> > mpif90 for 1.2.7 (release) of :<br>
2005/06/22 16:33:49<br>
> > Driving: gfortran<br>
-L/scratch1/np_cs/trial2/____<u></u>build/lib -v<br>
-lmpichf90 -lmpich -lpthread -lrt<br>
-lgfortranbegin -lgfortran -lm<br>
-shared-libgcc<br>
> > Using built-in specs.<br>
> > Target: x86_64-redhat-linux<br>
> > Configured with: ../configure<br>
--prefix=/usr<br>
--mandir=/usr/share/man<br>
--infodir=/usr/share/info --enable-shared<br>
--enable-threads=posix<br>
--enable-checking=release<br>
--with-system-zlib<br>
--enable-__cxa_atexit<br>
--disable-libunwind-exceptions<br>
--enable-libgcj-multifile<br>
--enable-languages=c,c++,objc,<u></u>____obj-c++,java,fortran,ada<br>
--enable-java-awt=gtk --disable-dssi<br>
--disable-plugin<br>
--with-java-home=/usr/lib/jvm/<u></u>____java-1.4.2-gcj-1.4.2.0/jre<br>
--with-cpu=generic --host=x86_64-redhat-linux<br>
> > Thread model: posix<br>
> > gcc version 4.1.2 20080704 (Red<br>
Hat 4.1.2-50)<br>
> > /usr/libexec/gcc/x86_64-____<u></u>redhat-linux/4.1.2/collect2<br>
--eh-frame-hdr -m elf_x86_64 --hash-style=gnu<br>
-dynamic-linker<br>
/lib64/ld-linux-x86-64.so.2<br>
/usr/lib/gcc/x86_64-redhat-___<u></u>_linux/4.1.2/../../../../<u></u>lib64/____crt1.o<br>
/usr/lib/gcc/x86_64-redhat-___<u></u>_linux/4.1.2/../../../../<u></u>lib64/____crti.o<br>
/usr/lib/gcc/x86_64-redhat-___<u></u>_linux/4.1.2/crtbegin.o<br>
-L/scratch1/np_cs/trial2/____<u></u>build/lib<br>
-L/opt/intel/mkl/<a href="http://10.2.2.025/____lib/em64t" target="_blank">10.2.2.025/__<u></u>__lib/em64t</a><br>
<<a href="http://10.2.2.025/__lib/em64t" target="_blank">http://10.2.2.025/__lib/em64t</a><u></u>><br>
<<a href="http://10.2.2.025/lib/em64t" target="_blank">http://10.2.2.025/lib/em64t</a>><<u></u>__<a href="http://10.2.2.025/__lib/em64t" target="_blank">http://10.2.2.025/__lib/<u></u>em64t</a><br>
<br>
<<a href="http://10.2.2.025/lib/em64t" target="_blank">http://10.2.2.025/lib/em64t</a>>><br>
-L/opt/intel/mkl/<a href="http://10.2.2.025/____lib/em64t" target="_blank">10.2.2.025/__<u></u>__lib/em64t</a><br>
<<a href="http://10.2.2.025/__lib/em64t" target="_blank">http://10.2.2.025/__lib/em64t</a><u></u>><br>
<<a href="http://10.2.2.025/lib/em64t" target="_blank">http://10.2.2.025/lib/em64t</a>><<u></u>__<a href="http://10.2.2.025/__lib/em64t" target="_blank">http://10.2.2.025/__lib/<u></u>em64t</a><br>
<br></div></div><div class="im">
<<a href="http://10.2.2.025/lib/em64t" target="_blank">http://10.2.2.025/lib/em64t</a>>><br>
-L/usr/lib/gcc/x86_64-redhat-_<u></u>___linux/4.1.2<br>
-L/usr/lib/gcc/x86_64-redhat-_<u></u>___linux/4.1.2<br>
-L/usr/lib/gcc/x86_64-redhat-_<u></u>___linux/4.1.2/../../../../<u></u>lib64<br>
-L/lib/../lib64 -L/usr/lib/../lib64<br>
-lmpichf90<br>
-lmpich -lpthread<br>
-lrt -lgfortranbegin -lgfortran -lm -lgcc_s<br>
-lgcc -lc -lgcc_s -lgcc<br>
/usr/lib/gcc/x86_64-redhat-___<u></u>_linux/4.1.2/crtend.o<br>
/usr/lib/gcc/x86_64-redhat-___<u></u>_linux/4.1.2/../../../../<u></u>lib64/____crtn.o<br>
> ><br>
/usr/lib/gcc/x86_64-redhat-___<u></u>_linux/4.1.2/libgfortranbegin.<u></u>____a(fmain.o):<br>
In function `main':<br>
> > (.text+0xa): undefined reference<br>
to `MAIN__'<br>
> > collect2: ld returned 1 exit status<br>
> ><br>
> > Am i missing somethin?<br>
> > thank you<br>
> > -akshar<br>
> ><br>
> > On Mon, Sep 12, 2011 at 1:24 AM,<br>
William<br>
Gropp<br>
<<a href="mailto:wgropp@illinois.edu" target="_blank">wgropp@illinois.edu</a><br>
<mailto:<a href="mailto:wgropp@illinois.edu" target="_blank">wgropp@illinois.edu</a>><br></div>
<mailto:<a href="mailto:wgropp@illinois.edu" target="_blank">wgropp@illinois.edu</a><div><div></div><div class="h5"><br>
<mailto:<a href="mailto:wgropp@illinois.edu" target="_blank">wgropp@illinois.edu</a>>><<u></u>__mailto:<a href="mailto:wg__ropp@illinois.edu" target="_blank">wg__ropp@illinois.edu</a><br>
<mailto:<a href="mailto:wg__ropp@illinois.edu" target="_blank">wg__ropp@illinois.edu</a>><br>
<br>
<mailto:<a href="mailto:wgropp@illinois.edu" target="_blank">wgropp@illinois.edu</a><br>
<mailto:<a href="mailto:wgropp@illinois.edu" target="_blank">wgropp@illinois.edu</a>>>><u></u>> wrote:<br>
> > You can use gfortran for F77 and<br>
F90. If<br>
your requirement is<br>
to use gfortran for F77 and a different<br>
fortran<br>
for F90, then they<br>
will need to use consistent linker names,<br>
calling conventions, data<br>
sizes, and libraries. The config.log<br>
file will<br>
have details on why<br>
configure decided that the Fortran 77 and<br>
Fortran 90 compilers were<br>
not compatible.<br>
> ><br>
> > Bill<br>
> ><br>
> ><br>
> > On Sep 9, 2011, at 4:28 PM, akshar<br>
bhosale wrote:<br>
> ><br>
> > hi,<br>
> > we have requirement of mpich-1.2.7<br>
with<br>
gfortran. We have fiven<br>
flags as :<br>
CC=gcc;F90=fortran;F77=____<u></u>gfortran;<br>
and tried to configure,<br>
it throws error as configure: error:<br>
Fortran 90<br>
and Fortran 77<br>
compilers are not compatible..<br>
> > We have to do it using gfortran<br>
only. os<br>
is rhel5.1 64 bit<br>
> > what extran flags settings we have<br>
to do?<br>
> ><br>
> > -akshar<br>
> ><br>
______________________________<u></u>_____________________<br>
> > mpich-discuss mailing list <a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.gov</a><br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.<u></u>gov</a>><br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl." target="_blank">mpich-discuss@mcs.anl.</a><u></u>__gov<br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.<u></u>gov</a>>><br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl" target="_blank">mpich-discuss@mcs.anl</a>.<br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl" target="_blank">mpich-discuss@mcs.anl</a>.<u></u>>____gov<br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl." target="_blank">mpich-discuss@mcs.anl.</a><u></u>__gov<br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.<u></u>gov</a>>>><br>
> > To manage subscription options or<br>
unsubscribe:<br>
> ><br>
<a href="https://lists.mcs.anl.gov/____mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/____<u></u>mailman/listinfo/mpich-discuss</a><br>
<<a href="https://lists.mcs.anl.gov/__mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/__<u></u>mailman/listinfo/mpich-discuss</a><u></u>><br>
<<a href="https://lists.mcs.anl.gov/__mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/__<u></u>mailman/listinfo/mpich-discuss</a><br>
<<a href="https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/<u></u>mailman/listinfo/mpich-discuss</a><u></u>>__><br>
> ><br>
> > William Gropp<br>
> > Director, Parallel Computing Institute<br>
> > Deputy Director for Research<br>
> > Institute for Advanced Computing<br>
Applications and Technologies<br>
> > Paul and Cynthia Saylor Professor of<br>
Computer Science<br>
> > University of Illinois<br>
Urbana-Champaign<br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
______________________________<u></u>_____________________<br>
> > mpich-discuss mailing list <a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.gov</a><br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.<u></u>gov</a>><br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl." target="_blank">mpich-discuss@mcs.anl.</a><u></u>__gov<br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.<u></u>gov</a>>><br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl" target="_blank">mpich-discuss@mcs.anl</a>.<br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl" target="_blank">mpich-discuss@mcs.anl</a>.<u></u>>____gov<br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl." target="_blank">mpich-discuss@mcs.anl.</a><u></u>__gov<br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.<u></u>gov</a>>>><br>
> > To manage subscription options or<br>
unsubscribe:<br>
> ><br>
<a href="https://lists.mcs.anl.gov/____mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/____<u></u>mailman/listinfo/mpich-discuss</a><br>
<<a href="https://lists.mcs.anl.gov/__mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/__<u></u>mailman/listinfo/mpich-discuss</a><u></u>><br></div></div><div class="im">
<<a href="https://lists.mcs.anl.gov/__mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/__<u></u>mailman/listinfo/mpich-discuss</a><br>
<<a href="https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/<u></u>mailman/listinfo/mpich-discuss</a><u></u>>__><br>
><br>
><br>
______________________________<u></u>_____________________<br>
> mpich-discuss mailing list <a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.gov</a><br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.<u></u>gov</a>><br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl." target="_blank">mpich-discuss@mcs.anl.</a><u></u>__gov<br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.<u></u>gov</a>>><br></div><div class="im">
<mailto:<a href="mailto:mpich-discuss@mcs.anl" target="_blank">mpich-discuss@mcs.anl</a>.<br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl" target="_blank">mpich-discuss@mcs.anl</a>.<u></u>>____gov<br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl." target="_blank">mpich-discuss@mcs.anl.</a><u></u>__gov<br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.<u></u>gov</a>>>><br>
> To manage subscription options or<br>
unsubscribe:<br>
><br>
<a href="https://lists.mcs.anl.gov/____mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/____<u></u>mailman/listinfo/mpich-discuss</a><br>
<<a href="https://lists.mcs.anl.gov/__mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/__<u></u>mailman/listinfo/mpich-discuss</a><u></u>><br></div><div class="im">
<<a href="https://lists.mcs.anl.gov/__mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/__<u></u>mailman/listinfo/mpich-discuss</a><br>
<<a href="https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/<u></u>mailman/listinfo/mpich-discuss</a><u></u>>__><br>
><br>
><br>
______________________________<u></u>_____________________<br>
> mpich-discuss mailing list <a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.gov</a><br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.<u></u>gov</a>><br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl." target="_blank">mpich-discuss@mcs.anl.</a><u></u>__gov<br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.<u></u>gov</a>>><br></div><div class="im">
<mailto:<a href="mailto:mpich-discuss@mcs.anl" target="_blank">mpich-discuss@mcs.anl</a>.<br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl" target="_blank">mpich-discuss@mcs.anl</a>.<u></u>>____gov<br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl." target="_blank">mpich-discuss@mcs.anl.</a><u></u>__gov<br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.<u></u>gov</a>>>><br>
> To manage subscription options or<br>
unsubscribe:<br>
><br>
<a href="https://lists.mcs.anl.gov/____mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/____<u></u>mailman/listinfo/mpich-discuss</a><br>
<<a href="https://lists.mcs.anl.gov/__mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/__<u></u>mailman/listinfo/mpich-discuss</a><u></u>><br></div><div class="im">
<<a href="https://lists.mcs.anl.gov/__mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/__<u></u>mailman/listinfo/mpich-discuss</a><br>
<<a href="https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/<u></u>mailman/listinfo/mpich-discuss</a><u></u>>__><br>
<br>
______________________________<u></u>_____________________<br>
mpich-discuss mailing list <a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.gov</a><br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.<u></u>gov</a>><br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl." target="_blank">mpich-discuss@mcs.anl.</a><u></u>__gov<br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.<u></u>gov</a>>><br></div><div class="im">
<mailto:<a href="mailto:mpich-discuss@mcs.anl" target="_blank">mpich-discuss@mcs.anl</a>.<br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl" target="_blank">mpich-discuss@mcs.anl</a>.<u></u>>____gov<br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl." target="_blank">mpich-discuss@mcs.anl.</a><u></u>__gov<br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.<u></u>gov</a>>>><br>
To manage subscription options or<br>
unsubscribe:<br>
<a href="https://lists.mcs.anl.gov/____mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/____<u></u>mailman/listinfo/mpich-discuss</a><br>
<<a href="https://lists.mcs.anl.gov/__mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/__<u></u>mailman/listinfo/mpich-discuss</a><u></u>><br></div><div><div></div><div class="h5">
<<a href="https://lists.mcs.anl.gov/__mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/__<u></u>mailman/listinfo/mpich-discuss</a><br>
<<a href="https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/<u></u>mailman/listinfo/mpich-discuss</a><u></u>>__><br>
<br>
<br>
<br>
------------------------------<u></u>____--------------------------<u></u>--__--__------------<br>
<br>
______________________________<u></u>_____________________<br>
mpich-discuss mailing list <a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.gov</a> <mailto:<a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.<u></u>gov</a>><br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl." target="_blank">mpich-discuss@mcs.anl.</a><u></u>__gov<br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.<u></u>gov</a>>><br>
To manage subscription options or unsubscribe:<br>
<a href="https://lists.mcs.anl.gov/____mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/____<u></u>mailman/listinfo/mpich-discuss</a><br>
<<a href="https://lists.mcs.anl.gov/__mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/__<u></u>mailman/listinfo/mpich-discuss</a><u></u>><br>
<<a href="https://lists.mcs.anl.gov/__mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/__<u></u>mailman/listinfo/mpich-discuss</a><br>
<<a href="https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/<u></u>mailman/listinfo/mpich-discuss</a><u></u>>__><br>
<br>
<br>
______________________________<u></u>_____________________<br>
mpich-discuss mailing list <a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.gov</a> <mailto:<a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.<u></u>gov</a>><br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl." target="_blank">mpich-discuss@mcs.anl.</a><u></u>__gov<br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.<u></u>gov</a>>><br>
To manage subscription options or unsubscribe:<br>
<a href="https://lists.mcs.anl.gov/____mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/____<u></u>mailman/listinfo/mpich-discuss</a><br>
<<a href="https://lists.mcs.anl.gov/__mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/__<u></u>mailman/listinfo/mpich-discuss</a><u></u>><br>
<<a href="https://lists.mcs.anl.gov/__mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/__<u></u>mailman/listinfo/mpich-discuss</a><br>
<<a href="https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/<u></u>mailman/listinfo/mpich-discuss</a><u></u>>__><br>
<br>
<br>
<br>
______________________________<u></u>_____________________<br>
mpich-discuss mailing list <a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.gov</a><br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.<u></u>gov</a>><br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl." target="_blank">mpich-discuss@mcs.anl.</a><u></u>__gov<br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.<u></u>gov</a>>><br>
To manage subscription options or unsubscribe:<br>
<a href="https://lists.mcs.anl.gov/____mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/____<u></u>mailman/listinfo/mpich-discuss</a><br>
<<a href="https://lists.mcs.anl.gov/__mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/__<u></u>mailman/listinfo/mpich-discuss</a><u></u>><br></div></div><div class="im">
<<a href="https://lists.mcs.anl.gov/__mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/__<u></u>mailman/listinfo/mpich-discuss</a><br>
<<a href="https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/<u></u>mailman/listinfo/mpich-discuss</a><u></u>>__><br>
<br>
<br>
<br>
<br>
------------------------------<u></u>__----------------------------<u></u>--__------------<br>
<br>
______________________________<u></u>___________________<br>
mpich-discuss mailing list <a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.gov</a><br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.<u></u>gov</a>><br>
To manage subscription options or unsubscribe:<br>
<a href="https://lists.mcs.anl.gov/__mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/__<u></u>mailman/listinfo/mpich-discuss</a><br>
<<a href="https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/<u></u>mailman/listinfo/mpich-discuss</a><u></u>><br>
<br>
<br>
______________________________<u></u>___________________<br>
mpich-discuss mailing list <a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.gov</a><br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.<u></u>gov</a>><br>
To manage subscription options or unsubscribe:<br>
<a href="https://lists.mcs.anl.gov/__mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/__<u></u>mailman/listinfo/mpich-discuss</a><br>
<<a href="https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/<u></u>mailman/listinfo/mpich-discuss</a><u></u>><br>
<br>
<br>
<br>
------------------------------<u></u>------------------------------<u></u>------------<br>
<br>
______________________________<u></u>_________________<br>
mpich-discuss mailing list <a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.gov</a><br>
To manage subscription options or unsubscribe:<br>
<a href="https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/<u></u>mailman/listinfo/mpich-discuss</a><br>
</div></blockquote><div><div></div><div class="h5">
<br>
______________________________<u></u>_________________<br>
mpich-discuss mailing list <a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.gov</a><br>
To manage subscription options or unsubscribe:<br>
<a href="https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/<u></u>mailman/listinfo/mpich-discuss</a><br>
</div></div></blockquote></div><br>