From the looks of it, your application is linking against MPICH (mpd is
their daemon). Do you have the mpich NT version instlled on your comp by
any chance? In any case, make sure you are linking against LAM and also
running the LAM binaries.
Regards,
Anju
Mark Dickson wrote:
>Hello Siegmar,
>
>You have to avoid the use of passwords to make LAM work correctly; you will
>need to generate keys to do this. See
>http://people.smu.edu/zwang/ssh-without-password.html for details on how to
>do it on Cygwin.
>
>Mark
>
>-----Original Message-----
>From: lam-bounces_at_[hidden] [mailto:lam-bounces_at_[hidden]] On Behalf Of
>Siegmar Gross
>Sent: Wednesday, October 06, 2004 8:58 AM
>To: lam_at_[hidden]
>Subject: Re: LAM: Cygwin: compiling LAM MPI results in undefined reference
>
>Hi,
>
>
>
>>Yes, you can disable a bunch of things. For a complete list try
>>"#./configure --help" to see what all you can disable. _inet_pton
>>provided by cygipc. This is strange. Could you send us the output of
>>your configure?
>>
>>
>
>Now I was able to compile LAM MPI. I added the code from
>src/newlib/libc/sys/linux/net/inet_ntop.c" from the Cygwin CVS at the end
>of the file "lam-7.1.1/share/ssi/boot/slurm/src/ssi_boot_slurm.c". I had
>to made very few changes. You find the modified file in the appendix so that
>you can just append it yourself. Mark, thank you very much for this hint.
>Thank you very much for all other comments as well. Now I could configure
>and compile MPI. I used
>
> configure --prefix=/usr/local/lam-7.1.1 --with-exceptions \
> --with-purify --with-threads=posix --with-trillium \
> --with-rsh="ssh -q" \
> --enable-shared --without-romio --without-cs-fs \
> |& tee log.configure.Cygwin.x86
>
>I've appended the requested configuration file as well. After installing
>everything I executed "laminfo" and got the following output:
>
> LAM/MPI: 7.1.1
> Prefix: /usr/local/lam-7.1.1
> Architecture: i686-pc-cygwin
> Configured by: Admin
> Configured on: Wed Oct 6 16:04:50 2004
> Configure host: eiger
> Memory manager: none
> C bindings: yes
> C++ bindings: yes
> Fortran bindings: yes
> C compiler: gcc
> C++ compiler: g++
> Fortran compiler: g77
> Fortran symbols: double_underscore
> C profiling: yes
> C++ profiling: yes
> Fortran profiling: yes
> C++ exceptions: yes
> Thread support: yes
> ROMIO support: no
> IMPI support: no
> Debug support: no
> Purify clean: yes
> SSI boot: globus (API v1.1, Module v0.6)
> SSI boot: rsh (API v1.1, Module v1.1)
> SSI boot: slurm (API v1.1, Module v1.0)
> SSI coll: lam_basic (API v1.1, Module v7.1)
> SSI coll: shmem (API v1.1, Module v1.0)
> SSI coll: smp (API v1.1, Module v1.2)
> SSI rpi: crtcp (API v1.1, Module v1.1)
> SSI rpi: lamd (API v1.0, Module v7.1)
> SSI rpi: sysv (API v1.0, Module v7.1)
> SSI rpi: tcp (API v1.0, Module v7.1)
> SSI rpi: usysv (API v1.0, Module v7.1)
> SSI cr: self (API v1.0, Module v1.0)
>
>Next I booted lam and started a small application. I got:
>
>Mpd needs an account to launch processes with:
>account (domain/user): Admin
>password: ....
>
>The password was echoed after return so I could see that I had a spelling
>error. When I try to start the program once more I get the error
>"LaunchProcess failed; LogonUser failed ...". What can I do to get the
>password question once more? Is the password stored somewhere? Possibly
>in plain text which I wouldn't like? Should I create a special user to
>launch processes? Thank you very much for your help in advance.
>
>
>Kind regards
>
>Siegmar
>
>
>_______________________________________________
>This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
>
|
