Re: Re: Charmrun issues and namd on Win 64

From: Gengbin Zheng (gzheng_at_ks.uiuc.edu)
Date: Wed Jul 11 2007 - 01:34:26 CDT

Hi Ilya,

Unfortunately we don't have access to the windows intel compiler so we
don't have experience on that. You should stick to one compiler for both
Charm++ and NAMD. The compiler padding may be different.

Gengbin

Ilya Chorny wrote:
> Gengbin,
>
> I am having trouble with charmd when compiled with the intel compiler.
> All x64. It gives me a socket error when I try to run charmrun. Is
> there any issues when using charmrun/charmd compiled with cl and namd
> compiled with icl?
>
> Thanks,
>
> Ilya
>
>
> On 7/6/07, *Gengbin Zheng* <gzheng_at_ks.uiuc.edu
> <mailto:gzheng_at_ks.uiuc.edu>> wrote:
>
>
> This is fixed in charm cvs version. Basically charmrun treated your "
> \\winclus\share\namd\namd2" as a relative path and added the current
> path "Z:\namd" in front of it.
>
> You can also modify your code in
> charm/src/arch/net/charmrun/charmrun.c,
> around line 796 to:
>
> #if defined(_WIN32) && !defined(__CYGWIN__)
> if (argv[1][1]==':' || argv[1][0]=='\\' && argv[1][1]=='\\') {
> /*E.g.:
> "C:\foo\bar.exe*/ <<<<<<<<<<<<<<<<< REPLACE
> #else
> if (argv[1][0]=='/') { /*E.g.: "\foo\bar"*/
> #endif
> /*Absolute path to node-program*/
> arg_nodeprog_a = argv[1];
>
>
> Just replace the second line above.
>
> Gengbin
>
> Ilya Chorny wrote:
>
> > Hello All,
> >
> > I am trying to run a job using windows CCS (x64).
> >
> > When I run the job using the Windows share directory convention
> (i.e.
> > \\fileserver\sharedfile\). I forgot the name of the convention.
> I get
> > a charmrun error because charmrun submits the job a as, for example
> > "Z:\namd\\" (see below). I can get around this by mounting the
> > directory on each machine, but I am interested to see if it is
> > possible to do this without mounting the directory. I don't
> > necessarily want to mount the directory on each node if I don't have
> > to. Any thoughts?
> >
> > Thanks,
> >
> > Ilya
> >
> >
> >
> > Charmrun> charmrun started...
> > Charmrun> using ./nodelist as nodesfile
> > Charmrun> adding client 0: "192.168.0.1 <http://192.168.0.1> <
> http://192.168.0.1>", IP:
> > 192.168.0.1 <http://192.168.0.1> <http://192.168.0.1>
> > Charmrun> adding client 1: " 192.168.0.2 <http://192.168.0.2>
> <http://192.168.0.2>",
> > IP:192.168.0.2 <http://192.168.0.2> <http://192.168.0.2>
> > Charmrun> adding client 2: " 192.168.0.1 <http://192.168.0.1>
> <http://192.168.0.1>",
> > IP:192.168.0.1 <http://192.168.0.1> <http://192.168.0.1 >
> > Charmrun> adding client 3: "192.168.0.2 <http://192.168.0.2>
> <http://192.168.0.2>",
> > IP:192.168.0.2 <http://192.168.0.2> < http://192.168.0.2>
> > Charmrun> Charmrun = 192.168.0.1 <http://192.168.0.1>
> <http://192.168.0.1>, port = 1225
> > Charmrun> packing arg: \\winclus\share\namd\alanin
> > Charmrun> Starting node program 0 on '192.168.0.1
> <http://192.168.0.1>
> > <http://192.168.0.1>' as Z:\namd\\\winclus\share\namd\namd2.
> > Error 'U' starting remote node program on 192.168.0.1--
> > unknown error.
> >
> > --
> > Ilya Chorny Ph.D.
>
>
>
>
>
> --
> Ilya Chorny Ph.D.

This archive was generated by hypermail 2.1.6 : Wed Feb 29 2012 - 15:44:57 CST