(fwd) [mvapich-discuss] FW: MVAPICH2 does not run...

[Choudhury, Durga]

Hi Wei

I am happy to say that I finally got MVAPICH2 to run on our box. Thanks
a lot to you (and Prof. Panda) for their help and support. The problems
were mostly on our side. Our hardware is 100% home built and there were
certain issues in our Linux BSP package that ultimately prevented
MVAPICH2 to run.

I still have not tested it on all kinds of hardware that we have, so I
might be speaking too soon when I said "it works". If I have more
questions, I might bug you folks again.

Thanks again.

Durga

-----Original Message-----
From: mvapich-discuss-bounces at cse.ohio-state.edu
[mailto:mvapich-discuss-bounces at cse.ohio-state.edu] On Behalf Of wei
huang
Sent: Tuesday, January 31, 2006 6:51 PM
To: Choudhury, Durga
Cc: mvapich-discuss at cse.ohio-state.edu
Subject: RE: (fwd) [mvapich-discuss] FW: MVAPICH2 does not run...

Hi,

> We are using both mpich-1.2.7-64bits and mpich2-1.0.2p1-64bits

So are you building them from source or just use a rebuild version?
>
> Unfortunately I don't remember all the details of the change I did
> (basically I was hacking with the software until the compiler won't
> break). It were mostly very simple things like path names,
includepaths
> and things like that (although I do realize that including/linking
from
> the wrong files could be catastrophic, I am pretty sure I did the
right
> thing.) There was one major change required, however. The
"config.guess"
> file in mvapich2-0.9.2/src/mpe2/src/slog2sdk/ directory failed to
> recognize the platform. I copied the "config.guess" file in
> mvapich2-0.9.2/src/mpe/ directory into this directory (which
recognized
> the platform as mips64-unknown-gnu-linux) for the configure script to
> proceed.
>

First, do you mean src/mpe2 by src/mpe? Second, I think this part of
code
is just from MPICH2. So there is no reason to have configure problem
here.
Are you using our default compiling script or you write your own one? I
think our default scripts goes with --without-mpe. So I believe you are
using your own script to configure.

So, would you please let us know the way you configure mpich2, send us
the
whole configure log, make log, install log. And would you please send us
the exact error message you are seeing. Without them it will be very
difficult to guess what the problem is.

Thanks

>
>
> > 2. About possible network issues with name resolutions:
>
> > Like I said in the original email, the OSU software works fine on
two
>
> > Linux PCs connected back-to-back via Ethernet (i.e. they are not on
> any
>
> > network). So I find it strange that our MIPS64 cluster (which ARE
>
> > connected to outside network via front panel Ethernet) would
complain
>
> > about name resolution issues.
>
>
>
> Again, there may be some problems with your system setup if python
>
> gethostname_ex throws exception. You might want to consult your sysadm
>
> about this issue.
>
>
>
> You are probably right; but I am still confused about how this works
for
> two back-to-back connected Linux PCs (they don't even run the same
> Linux; one runs Mandrake and the other runs Fedora Core 4, perhaps
even
> the kernel versions are different.) And if you could please explain to
> me as to why do we care about a name lookup anyway.
>
>
>
> Thanks a lot for your help.
>
>
>
> Best regards
>
> Durga
>
>
>
> Thanks!
>
>
>
> Regards,
>
> Wei Huang
>
>
>
> 774 Dreese Lab, 2015 Neil Ave,
>
> Dept. of Computer Science and Engineering
>
> Ohio State University
>
> OH 43210
>
> Tel: (614)292-8501
>
>
>
>


_______________________________________________
mvapich-discuss mailing list
mvapich-discuss at cse.ohio-state.edu
http://mail.cse.ohio-state.edu/mailman/listinfo/mvapich-discuss