[MPICH] build mpich2 with Myrinet GM

[Darius Buntinas]

Can you send us the output of configure as well as config.log?

Thanks,
-d

On 02/26/2008 11:35 AM, Wei-keng Liao wrote:
> I got an error during make:
> 
> ../include/mpid_nem_atomics.h(31): catastrophic error: #error directive: 
> No swap function defined for this architecture
>   #error No swap function defined for this architecture
>    ^
> compilation aborted for mpid_nem_alloc.c (code 4)
> 
> I am using configure options:
>           --with-device=ch3:nemesis:gm  \
>           --with-gm=/opt/gm \
>           --enable-f77 --enable-f90 --enable-cxx \
>           --enable-fast \
>           --enable-romio \
>           --without-mpe \
>           --with-file-system=ufs
> 
> and the command "uname -a" on the machine is
> Linux tg-login4 2.4.21-309.tg1 #1 SMP Thu Jun 1 17:07:28 CDT 2006 ia64 
> unknown
> 
> I am using Intel compiler v 9.1.043
> 
> Wei-keng
> 
> 
> On Tue, 26 Feb 2008, Darius Buntinas wrote:
>> On 02/26/2008 10:08 AM, Wei-keng Liao wrote:
>>> I have a few questions on build mpich2-1.0.6p1 with Myrinet GM library.
>>>
>>> On my target machine, the GM library (include, lib, bin, etc.) is in
>>> /opt/gm. According to MPICH README, I used the 2 options below when
>>> configuring: 
>>>     --with-device=ch3:nemesis:gm  and --with-gm=/opt/gm
>>>
>>> I can see both libgm.a and libgm.so are in /opt/gm/lib.
>>>
>>> Q1: Do I need other configure options or setting environment variables
>>>     (in addition to CC, FC, CXX, F90)? Should I set LDFLAGS to
>>>     "-L/opt/gm/lib -lgm" ?
>> Nope, the --with-gm=/opt/gm should take care of all of that for you.
>>
>>> Q2: Since nemesis does not support MPI dynamic process routines yet and I 
>>>     need those routines, can I use --with-device=ch3:sock:gm instead?
>> No, only nemesis supports gm.
>>
>>> Q3: Do I need anything else (source codes, library) from Myrinet to build 
>>>     mpich? Or the /opt/gm is good enough?
>> All you need is libgm.a and gm.h.
>>
>>> Q4: Once the mpich is built, is there a way to verify that GM is actually 
>>>     used?
>> Well, you should see a performance improvement over using sockets.  Run a
>> ping-pong test; you should see latencies around 10us or less.
>>
>> -d
>>
>