- discuss - mailman3.cels.anl.gov

Re: [mpich-discuss] Error in c.txt nemesis does not exist
by Ayesha Ghani 05 Dec '12

05 Dec '12

Hi Dave Thanks for your help! I have tried to install a few versions of MPICH2 on cygwin now. For version 2-1.4, the c.txt file seems fine (no errors) but the m.txt file goes on for a while 'Entering directory' and 'Leaving directory' and then at the end outputs an error. make[1]: *** No rule to make target '/home/agha023/libraries/mpich2-1.4/src/mpl/Makefile.am' needed by '/home/agha023/libraries/mpich2-1.4/src/mpl/Makefile.in'. Stop make: *** [all-redirect] Error 1 >From searching up forums this error occurs because make couldnt find instructions in the Makefile.in to build the target. However Makefile.am and Makefile.in both exist in the directory above. Again however I can't find a solution to this problem and would greatly appreciate any help. Should I email the m.txt and c.txt files? Kind Regards Ayesha Ghani On 6 December 2012 08:03, Dave Goodell <goodell(a)mcs.anl.gov> wrote: > Try using mpich2-1.4 instead. It would not be surprising if there was a > problem with 1.5 on cygwin. > > -Dave > > On Dec 4, 2012, at 8:48 PM PST, Ayesha Ghani wrote: > > > Hello > > > > > > I was working through the installation instructions for mpich2 very > carefully this time and my .c file has an error at the end: > > 'immediate ERROR: nemesis does not exist' > > > > I would appreciate any assistance. > > > > > > Kind Regards > > Ayesha > > <c.txt>_______________________________________________ > > discuss mailing list discuss(a)mpich.org > > To manage subscription options or unsubscribe: > > https://lists.mpich.org/mailman/listinfo/discuss > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss >

1 0

Re: [mpich-discuss] Error in c.txt nemesis does not exist
by Dave Goodell 05 Dec '12

05 Dec '12

Try using mpich2-1.4 instead. It would not be surprising if there was a problem with 1.5 on cygwin. -Dave On Dec 4, 2012, at 8:48 PM PST, Ayesha Ghani wrote: > Hello > > > I was working through the installation instructions for mpich2 very carefully this time and my .c file has an error at the end: > 'immediate ERROR: nemesis does not exist' > > I would appreciate any assistance. > > > Kind Regards > Ayesha > <c.txt>_______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] Installation problems MPICH2 on cygwin
by Dave Goodell 05 Dec '12

05 Dec '12

If your "c.txt" was empty then you probably didn't successfully run configure. Since you didn't run configure successfully, no makefiles were generated, causing the error message in your m.txt file. -Dave On Dec 4, 2012, at 6:09 PM PST, Ayesha Ghani wrote: > Hi > > I was following the MPICH2 installation guide ad got up to step 6 alright. The c.txt file was empty after step 5 but I got an error in the .m file following step 6, 'Build MPICH2' > > Do you have an idea of what is wrong or how i can fix the problem? > > > Kind Regards > Ayesha Ghani > > > <m.txt>_______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss

1 0

Error in c.txt nemesis does not exist
by Ayesha Ghani 04 Dec '12

04 Dec '12

Hello I was working through the installation instructions for mpich2 very carefully this time and my .c file has an error at the end: 'immediate ERROR: nemesis does not exist' I would appreciate any assistance. Kind Regards Ayesha

1 0

Fwd: Installation problems MPICH2 on cygwin
by Ayesha Ghani 04 Dec '12

04 Dec '12

Hi I was following the MPICH2 installation guide ad got up to step 6 alright. The c.txt file was empty after step 5 but I got an error in the .m file following step 6, 'Build MPICH2' Do you have an idea of what is wrong or how i can fix the problem? Kind Regards Ayesha Ghani

1 0

Re: [mpich-discuss] Why does MPI_Init() get NULL argc and argv when running Fortran programs?
by clara 04 Dec '12

04 Dec '12

Thanks a lot. On Tue, Dec 4, 2012 at 3:36 AM, Jeff Hammond <jhammond(a)alcf.anl.gov> wrote: > As far as I can tell, there's no standard way to access argc/argv from > Fortran until Fortran 2003 > (http://fortranwiki.org/fortran/show/Command-line+arguments) Until > MPI-3, the Fortran bindings were targeting FORTRAN 77 and Fortran 90 > and 95 (and somewhat awkwardly), so there was no reasonable way to try > to deal with them. > > Now that there are Fortran 2008 bindings in MPI-3, it might be > interesting to consider how to handle argc/argv in a nice way just as > is done for C. I don't know if anyone has thought of what happens > when Fortran 2003+ users use the argc/argv access routines. It would > seem that the same problem would exist that is present if one accesses > argc/argv in C before MPI_INIT is called (i.e. argc/argv will have > mpiexec-related arguments, not just the ones relative to the user > program). > > I created a ticket with the MPI Forum about this: > https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/351. > > Best, > > Jeff > > On Mon, Dec 3, 2012 at 9:19 AM, Rajeev Thakur <thakur(a)mcs.anl.gov> wrote: > > The Fortran binding for MPI_Init is > > > > MPI_INIT(IERROR) > > > > There are no command line arguments. > > > > Rajeev > > > > > > On Dec 3, 2012, at 6:22 AM, clara wrote: > > > >> Hi, > >> > >> I added a print statement at the beginning of MPI_Init() in mpich2-1.4 > in order to check the arguments of MPI_Init(). When running a Fortran > program, e.g. ep.S.1, the arguments of MPI_Init() are NULL; however, when > running a C program, e.g. is.S.1, *argc of MPI_Init() is 1 and (*argv)[0] > points to the name of the executed file is.S.1. > >> Can anyone tell us why there is difference in dealing with arguments of > MPI_Init() between C and Fortran programs? How could arguments be > transferred to MPI_Init() for Fortran programs in mpich2? Thanks. > >> > >> Best, > >> Clara > >> _______________________________________________ > >> discuss mailing list discuss(a)mpich.org > >> To manage subscription options or unsubscribe: > >> https://lists.mpich.org/mailman/listinfo/discuss > > > > _______________________________________________ > > discuss mailing list discuss(a)mpich.org > > To manage subscription options or unsubscribe: > > https://lists.mpich.org/mailman/listinfo/discuss > > > > -- > Jeff Hammond > Argonne Leadership Computing Facility > University of Chicago Computation Institute > jhammond(a)alcf.anl.gov / (630) 252-5381 > http://www.linkedin.com/in/jeffhammond > https://wiki.alcf.anl.gov/parts/index.php/User:Jhammond > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss >

1 0

Re: [mpich-discuss] Why does MPI_Init() get NULL argc and argv when running Fortran programs?
by Jeff Hammond 03 Dec '12

03 Dec '12

As far as I can tell, there's no standard way to access argc/argv from Fortran until Fortran 2003 (http://fortranwiki.org/fortran/show/Command-line+arguments) Until MPI-3, the Fortran bindings were targeting FORTRAN 77 and Fortran 90 and 95 (and somewhat awkwardly), so there was no reasonable way to try to deal with them. Now that there are Fortran 2008 bindings in MPI-3, it might be interesting to consider how to handle argc/argv in a nice way just as is done for C. I don't know if anyone has thought of what happens when Fortran 2003+ users use the argc/argv access routines. It would seem that the same problem would exist that is present if one accesses argc/argv in C before MPI_INIT is called (i.e. argc/argv will have mpiexec-related arguments, not just the ones relative to the user program). I created a ticket with the MPI Forum about this: https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/351. Best, Jeff On Mon, Dec 3, 2012 at 9:19 AM, Rajeev Thakur <thakur(a)mcs.anl.gov> wrote: > The Fortran binding for MPI_Init is > > MPI_INIT(IERROR) > > There are no command line arguments. > > Rajeev > > > On Dec 3, 2012, at 6:22 AM, clara wrote: > >> Hi, >> >> I added a print statement at the beginning of MPI_Init() in mpich2-1.4 in order to check the arguments of MPI_Init(). When running a Fortran program, e.g. ep.S.1, the arguments of MPI_Init() are NULL; however, when running a C program, e.g. is.S.1, *argc of MPI_Init() is 1 and (*argv)[0] points to the name of the executed file is.S.1. >> Can anyone tell us why there is difference in dealing with arguments of MPI_Init() between C and Fortran programs? How could arguments be transferred to MPI_Init() for Fortran programs in mpich2? Thanks. >> >> Best, >> Clara >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss -- Jeff Hammond Argonne Leadership Computing Facility University of Chicago Computation Institute jhammond(a)alcf.anl.gov / (630) 252-5381 http://www.linkedin.com/in/jeffhammond https://wiki.alcf.anl.gov/parts/index.php/User:Jhammond

1 0

Re: [mpich-discuss] Why does MPI_Init() get NULL argc and argv when running Fortran programs?
by Rajeev Thakur 03 Dec '12

03 Dec '12

The Fortran binding for MPI_Init is MPI_INIT(IERROR) There are no command line arguments. Rajeev On Dec 3, 2012, at 6:22 AM, clara wrote: > Hi, > > I added a print statement at the beginning of MPI_Init() in mpich2-1.4 in order to check the arguments of MPI_Init(). When running a Fortran program, e.g. ep.S.1, the arguments of MPI_Init() are NULL; however, when running a C program, e.g. is.S.1, *argc of MPI_Init() is 1 and (*argv)[0] points to the name of the executed file is.S.1. > Can anyone tell us why there is difference in dealing with arguments of MPI_Init() between C and Fortran programs? How could arguments be transferred to MPI_Init() for Fortran programs in mpich2? Thanks. > > Best, > Clara > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss

1 0

Why does MPI_Init() get NULL argc and argv when running Fortran programs?
by clara 03 Dec '12

03 Dec '12

Hi, I added a print statement at the beginning of MPI_Init() in mpich2-1.4 in order to check the arguments of MPI_Init(). When running a Fortran program, e.g. ep.S.1, the arguments of MPI_Init() are NULL; however, when running a C program, e.g. is.S.1, *argc of MPI_Init() is 1 and (*argv)[0] points to the name of the executed file is.S.1. Can anyone tell us why there is difference in dealing with arguments of MPI_Init() between C and Fortran programs? How could arguments be transferred to MPI_Init() for Fortran programs in mpich2? Thanks. Best, Clara

1 0

Why does MPI_Init() get NULL argc and argv when running Fortran programs?
by clara 03 Dec '12

03 Dec '12

Hi, I added a printf statement at the beginning of MPI_Init() in mpich2-1.4 in order to check the arguments of MPI_Init(). When running a Fortran program, e.g. ep.S.1, the arguments of MPI_Init() are NULL; however, when running a C program, e.g. is.S.1, *argc of MPI_Init() is 1 and (*argv)[0] points to the name of the executed file is.S.1. Can anyone tell us why there is difference in dealing with arguments of MPI_Init() between C and Fortran programs? How could arguments be transferred to MPI_Init() for Fortran programs in mpich2? Thanks. Best, Clara

1 0