[MPICH] WRF and MPICH2

[Scott Atchley]

And it runs!

I will patch the WRF clean script to delete this soft-link.

Thanks,

Scott

On Aug 17, 2007, at 3:48 PM, Scott Atchley wrote:

> Hi Rajeev,
>
> <grins>
>
> I previously built WRF with mpich-mx. In $WRF/share, there is  
> mpif.h which is a soft-link to $MPICH-MX/include/mpif.h.
>
> Apparently, WRF's ./clean -a does not remove it. I changed it to  
> point to MPICH2's mpif.h and I am recompiling.
>
> Thanks to Rajeev and Brian Dobbins for pointing this out. :-)
>
> Scott
>
> On Aug 17, 2007, at 3:11 PM, Rajeev Thakur wrote:
>
>> Yes this looks like a case where a compiler or mpif.h got used  
>> from some
>> other MPI implementation.
>>
>> Rajeev
>>
>>> -----Original Message-----
>>> From: owner-mpich-discuss at mcs.anl.gov
>>> [mailto:owner-mpich-discuss at mcs.anl.gov] On Behalf Of Scott Atchley
>>> Sent: Friday, August 17, 2007 1:11 PM
>>> To: mpich-discuss at mcs.anl.gov
>>> Subject: [MPICH] WRF and MPICH2
>>>
>>> Hi all,
>>>
>>> I am trying to run WRF2.1 using MPICH2's ch3:ssm over gigabit
>>> Ethernet. When I start the job, I get:
>>>
>>> [cli_0]: aborting job:
>>> Fatal error in MPI_Comm_size: Invalid communicator, error stack:
>>> MPI_Comm_size(112): MPI_Comm_size(comm=0x5b,
>>> size=0x7fff18349588) failed
>>> MPI_Comm_size(70).: Invalid communicator
>>>
>>> for each process. I have compiled MPICH2 and WRF with PGI 6.2.6 and
>>> 7.0.7 with the same results. If I run it with -gdb, there are no
>>> symbols and I cannot debug. I tried compiling MPICH2 with --enable-
>>> g=all and then running it with -gdb, but it hangs and never gives me
>>> a gdb command line.
>>>
>>> Does anyone have experience with this?
>>>
>>> Thanks,
>>>
>>> Scott
>>>
>>>
>>
>