> |>I'm trying to get lam working on winxp with cygwin. I've grabbed the
> |>latest CVS (not a snapshot). I compiled it (w/o romio) and installed it
> |>without problems. I compiled the hello example and running it singly
> |>(./hello) works as expected. However, I can't run it in a booted universe.
> |>
> |>$ cat machines
> |>fib1
> |>$ lamboot machines
> |>
> |>LAM 7.1a1cvs/MPI 2 C++ - Indiana University
> |>
> |>$ lamnodes
> |>n0 fib1.somewhere.cc:1:origin,this_node
> |>$ mpirun N hello
> |><a long time>
> |>mpirun (set_stdio): Connection aborted
> |
> |
> | I am assuming that you are using the native cygwin terminal. There are
> | known issues with native cygwin terminal if you boot LAM universe and
> | "mpirun" on the same terminal.
> |
> | Can you try switching over to "xterm"? This will allow you to use LAM on
> | cygwin as would on any other platform and is highly recommended. See more
> | on the XFree86 project to find out how to get xterm running on cygwin.
> |
> | You can try the following too:
> |
> | Start 2 seperate cygwin terminals. By this I mean - "Dont invoke the other
> | terminal#2 from terminal#1, but actually start cygwin from its ".exe"
> | twice. Boot LAM Universe from terminal#1. Always boot LAM from this
> | terminal. Use the other terminal(#2) to execute your MPI programs.
> |
> | Anju
> |
> |
>
> I tried running from separate xterms and separate console sessions with
> the same results.
Hi,
We are unable to replicate the problem on our machines. Could you send us
the configure and build logs? Which version of Cygwin are you running?
Anju.
|
