[mpich-discuss] Problems with running make

Sat Mar 1 05:18:31 CST 2014

Gus and others,
many thanks for your comments and suggestions. I am unsure whether I 
need fortran included as I am not in control of the software to be run 
on this linux cluster. I have asked but not yet got a reply...

However, I did a yum search gfortran and installed the 
gcc-gfortran.x86_64 (I hope that was the one you referred to). I 
followed up with the ./configure ... as per your suggestion. That did 
not work. I then tried with only ./configure --prefix=/my/bin/folder. 
That worked so I also did make and make install.

I have a machinefile with three linux computers, all sharing the same 
mpi binaries. Running hostname on all 20 cores works, so I guess I 
should conclude that mpi works, right?

I then tried the software I am supposed to run on the cluster. It works 
on all nodes on the master computer, but not if other computers are 
involved. I have captured the output from such failed attempt to run 
that software on all available nodes on all available computers in the 
cluster, see below. I have attached c2.txt and m2.txt (and the output of 
the failed run) in the attached gzipped file (the failed run in run2.txt 
and in the image below may not be from the same failed run...).

So, is it an issue for the software developers or is it an issue with mpich?

I would appreciate if you could let me know if mpich is properly 
compiled and installed and whether I should follow up with the 
application developers instead. I now that they are successfully running 
this code on V1.4.1.

Thanks for your prompt support.

Cheers,
Ron

On 1/03/2014 08:19, Gus Correa wrote:
> Hi Ron
>
> Your config.log shows that configure is picking up Gnu
> /usr/bin/f77 as the Fortran compiler.
> See an excerpt of config.log below.
>
> The Gnu f77/g77, which cannot compile Fortran-90 and later code.
>
> You may want to install gfortran.
> Configure didn't find gfortran.
> However, you can install it easily from RPM through yum.
>
> Once you install gfortran, to avoid picking up wrong compilers,
> you can also point configure to the compilers.
> Assuming you want to use all Gnu compilers, this would do it:
>
> ./configure CC=gcc, CXX=g++, F77=gfortran, FC=gfortran, 
> --prefix=/wherever/you/want ...
>
> Another possibility is follow Reuti's suggestion of
> not compiling the MPICH Fortran-90 interface.
>
> I hope this helps,
> Gus Correa
>
> ******* from your config.log *********
> ...
> configure:17977: result: no
> configure:17947: checking for gfortran
> configure:17977: result: no
> configure:17947: checking for f77
> configure:17963: found /usr/bin/f77
> configure:17974: result: f77
> configure:18000: checking for Fortran 77 compiler version
> configure:18009: f77 --version >&5
> GNU Fortran (GCC) 3.4.6 20060404 (Red Hat 3.4.6-19.el6)
> ...
> *****************************************
>
> On 02/28/2014 05:02 AM, Reuti wrote:
>> Hi,
>>
>> Am 28.02.2014 um 09:22 schrieb Ron Palmer:
>>
>>> I am struggling with running make on MPICH, V3.1. I believe that 
>>> ./configure went well but I do not understand what caused the errors 
>>> in make. I thought it may be associated with the fortran compile but 
>>> I have F77 installed (though somewhat confused whether fortran 90 is 
>>> also installed).  The README file suggested that I send an email to 
>>> this list with nominated four text files attached.
>>
>> You can try to skip f90:
>>
>> $ ./configure --disable-fc ...
>>
>> -- Reuti
>>
>>
>>> The end of the m.txt file is included here for easy access, full 
>>> details are attached...
>>>
>>>   CC       src/mpi/topo/nhb_alltoallw.lo
>>>   CC       src/binding/f90/create_f90_int.lo
>>>   CC       src/binding/f90/create_f90_real.lo
>>> src/binding/f90/create_f90_real.c: In function 
>>> 'PMPI_Type_create_f90_real':
>>> src/binding/f90/create_f90_real.c:73: error: expected expression 
>>> before ',' token
>>> src/binding/f90/create_f90_real.c:74: error: expected expression 
>>> before ',' token
>>> make[2]: *** [src/binding/f90/create_f90_real.lo] Error 1
>>> make[2]: Leaving directory `/inv/mpich-3.1'
>>> make[1]: *** [all-recursive] Error 1
>>> make[1]: Leaving directory `/inv/mpich-3.1'
>>> make: *** [all] Error 2
>>>
>>> I look forward to any suggestions any of you may have.
>>> Regards, Ron
>>>
>>>
>>> <mpi_logs.tar.gz>_______________________________________________
>>> discuss mailing list     discuss at mpich.org
>>> To manage subscription options or unsubscribe:
>>> https://lists.mpich.org/mailman/listinfo/discuss
>>
>> _______________________________________________
>> discuss mailing list     discuss at mpich.org
>> To manage subscription options or unsubscribe:
>> https://lists.mpich.org/mailman/listinfo/discuss
>
> _______________________________________________
> discuss mailing list     discuss at mpich.org
> To manage subscription options or unsubscribe:
> https://lists.mpich.org/mailman/listinfo/discuss

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mpich.org/pipermail/discuss/attachments/20140301/910e35bc/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ghdahehb.png
Type: image/png
Size: 52787 bytes
Desc: not available
URL: <http://lists.mpich.org/pipermail/discuss/attachments/20140301/910e35bc/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: run2.tar.gz
Type: application/gzip
Size: 20981 bytes
Desc: not available
URL: <http://lists.mpich.org/pipermail/discuss/attachments/20140301/910e35bc/attachment.bin>