[mvapich-discuss] Problem Building MVAPICH-1.0-beta with PGI Compilers

[Jonathan L. Perkins]

Peter Cebull wrote:
> Weikuan Yu wrote:
>>
>> Could you please confirm the version number? is it mvapich-0.9.9 or 
>> the latest mvapich-1.0.0 from a nightly tarball?
>>
> I've tried the Feb 5th tarball from 
> http://mvapich.cse.ohio-state.edu/nightly/mvapich/branches/0.9.9, and 
> the MVAPICH 1.0 beta dated 10/26/07: 
> http://mvapich.cse.ohio-state.edu/download/mvapich/mvapich-1.0-beta.tar.gz.

In order to try our latest MVAPICH sources you can use Subversion.

"svn export https://mvapich.cse.ohio-state.edu/svn/mpi/mvapich/trunk" 
should do the trick.

> I'm starting to wonder if the build might be picking up the wrong header 
> files. We have some header files in /usr/include (mpif.h, mpi.h, etc.), 
> I guess from SGI's MPT. Maybe they're causing problems.
> 
> Peter
>>
>> Peter Cebull wrote:
>>> Jonathan L. Perkins wrote:
>>>>
>>>> Just another suggestion.  Can you try MVAPICH from our trunk and/or 
>>>> mvapich2 to see if you encounter the same issue?  Is there an older 
>>>> version of MVAPICH that you got to work with the same configuration?
>>>>
>>> I tried mvapich-0.9.9-2008-02-05 with no luck. MVAPICH2 seemed to 
>>> build okay. I've never built MVAPICH before -- our new system (SGI 
>>> Altix ICE) came with gcc and Intel versions of mvapich 0.9.9, I'm 
>>> just trying to build an equivalent configuration for the PGI compilers.
>>>
>>> It seems to be a problem finding include files. If I cd into 
>>> romio/mpi-io and try to compile close.c, it fails. I copied the 
>>> entire source tree to my desktop (OpenSUSE 10.1 and the same PGI 
>>> compilers) and close.c compiled with no problem. Back on the other 
>>> system if I copied the header files from the include directory into 
>>> romio/mpi-io, then I could compile close.c.
>>>
>>> Peter
>>>
>>
> 
> 


-- 
Jonathan Perkins
http://www.cse.ohio-state.edu/~perkinjo