June 2013 - discuss - mailman3.cels.anl.gov

Re: [mpich-discuss] install + config on windows
by Antonio J. Peña 11 Jun '13

11 Jun '13

Hi Benoit, As our support for Windows platforms has been discontinued, we cannot guarantee MPICH is going to be able to be compiled in newer versions of the Windows compilers and/or the operating system itself. Unless Jayesh has any comments on this regard, I'm not aware of any experience of MPICH + Windows 7. I apologize for the inconvenience. Thanks, Antonio On Monday, June 10, 2013 08:04:03 AM spatiogis wrote: > Hello, > > actually, it seems that Mpich must be compiled to work. The point is that > the "Readme" file gives an explanation to compile the programs with Visual > studio 2003. Anyway this last software is very difficult to make work on > windows 7. > > Is there finally a way to compile Mpich on windows 7 with Visual Studio ? > > best regards, > > Benoit Véler > > > Hi, > > > > From the log output it looks like credentials (password) for > > > > Utilisateur was not correct. > > > > Is Utilisateur a valid Windows user on your machine? Have you > > > > registered the username/password correctly (Try re-registering the > > username+password by typing "mpiexec -register" at the command prompt)? > > > > Regards, > > Jayesh > > > > ----- Original Message ----- > > From: "spatiogis" <geo(a)spatiogis.fr> > > To: discuss(a)mpich.org > > Sent: Friday, May 3, 2013 11:58:00 AM > > Subject: Re: [mpich-discuss] install + config on windows > > > > Hello, > > > > for this command : > > > > # C:\Progra~1\MPICH2\bin\mpiexec -verbose -n 2 > > > > C:\Progra~1\MPICH2\examples\cpi.exe > > > > result : > > > > ....../SMPDU_Sock_post_readv > > > > ...../SMPDU_Sock_post_read > > ..../smpd_handle_op_connect > > ....sock_waiting for the next event. > > ....\SMPDU_Sock_wait > > ..../SMPDU_Sock_wait > > ....SOCK_OP_READ event.error = 0, result = 0, context=left > > ....\smpd_handle_op_read > > .....\smpd_state_reading_challenge_string > > ......read challenge string: '1.4.1p1 18467' > > ......\smpd_verify_version > > ....../smpd_verify_version > > ......Verification of smpd version succeeded > > ......\smpd_hash > > ....../smpd_hash > > ......\SMPDU_Sock_post_write > > .......\SMPDU_Sock_post_writev > > ......./SMPDU_Sock_post_writev > > ....../SMPDU_Sock_post_write > > ...../smpd_state_reading_challenge_string > > ..../smpd_handle_op_read > > ....sock_waiting for the next event. > > ....\SMPDU_Sock_wait > > ..../SMPDU_Sock_wait > > ....SOCK_OP_WRITE event.error = 0, result = 0, context=left > > ....\smpd_handle_op_write > > .....\smpd_state_writing_challenge_response > > ......wrote challenge response: 'dafd1d07c1e6e9cb5fae968403d0d933' > > ......\SMPDU_Sock_post_read > > .......\SMPDU_Sock_post_readv > > ......./SMPDU_Sock_post_readv > > ....../SMPDU_Sock_post_read > > ...../smpd_state_writing_challenge_response > > ..../smpd_handle_op_write > > ....sock_waiting for the next event. > > ....\SMPDU_Sock_wait > > ..../SMPDU_Sock_wait > > ....SOCK_OP_READ event.error = 0, result = 0, context=left > > ....\smpd_handle_op_read > > .....\smpd_state_reading_connect_result > > ......read connect result: 'SUCCESS' > > ......\SMPDU_Sock_post_write > > .......\SMPDU_Sock_post_writev > > ......./SMPDU_Sock_post_writev > > ....../SMPDU_Sock_post_write > > ...../smpd_state_reading_connect_result > > ..../smpd_handle_op_read > > ....sock_waiting for the next event. > > ....\SMPDU_Sock_wait > > ..../SMPDU_Sock_wait > > ....SOCK_OP_WRITE event.error = 0, result = 0, context=left > > ....\smpd_handle_op_write > > .....\smpd_state_writing_process_session_request > > ......wrote process session request: 'process' > > ......\SMPDU_Sock_post_read > > .......\SMPDU_Sock_post_readv > > ......./SMPDU_Sock_post_readv > > ....../SMPDU_Sock_post_read > > ...../smpd_state_writing_process_session_request > > ..../smpd_handle_op_write > > ....sock_waiting for the next event. > > ....\SMPDU_Sock_wait > > ..../SMPDU_Sock_wait > > ....SOCK_OP_READ event.error = 0, result = 0, context=left > > ....\smpd_handle_op_read > > .....\smpd_state_reading_cred_request > > ......read cred request: 'credentials' > > ......\smpd_hide_string_arg > > .......\first_token > > ......./first_token > > .......\compare_token > > ......./compare_token > > .......\next_token > > ........\first_token > > ......../first_token > > ........\first_token > > ......../first_token > > ......./next_token > > ....../smpd_hide_string_arg > > ....../smpd_hide_string_arg > > ......\smpd_hide_string_arg > > .......\first_token > > ......./first_token > > .......\compare_token > > ......./compare_token > > .......\next_token > > ........\first_token > > ......../first_token > > ........\first_token > > ......../first_token > > ......./next_token > > ....../smpd_hide_string_arg > > ....../smpd_hide_string_arg > > ......\smpd_hide_string_arg > > .......\first_token > > ......./first_token > > .......\compare_token > > ......./compare_token > > .......\next_token > > ........\first_token > > ......../first_token > > ........\first_token > > ......../first_token > > ......./next_token > > ....../smpd_hide_string_arg > > ....../smpd_hide_string_arg > > ......\smpd_hide_string_arg > > .......\first_token > > ......./first_token > > .......\compare_token > > ......./compare_token > > .......\next_token > > ........\first_token > > ......../first_token > > ........\first_token > > ......../first_token > > ......./next_token > > ....../smpd_hide_string_arg > > ....../smpd_hide_string_arg > > ......\smpd_hide_string_arg > > .......\first_token > > ......./first_token > > .......\compare_token > > ......./compare_token > > .......\next_token > > ........\first_token > > ......../first_token > > ........\first_token > > ......../first_token > > ......./next_token > > ....../smpd_hide_string_arg > > ....../smpd_hide_string_arg > > .......\smpd_option_on > > ........\smpd_get_smpd_data > > .........\smpd_get_smpd_data_from_environment > > ........./smpd_get_smpd_data_from_environment > > .........\smpd_get_smpd_data_default > > ........./smpd_get_smpd_data_default > > .........Unable to get the data for the key 'nocache' > > ......../smpd_get_smpd_data > > ......./smpd_option_on > > ......\smpd_hide_string_arg > > .......\first_token > > ......./first_token > > .......\compare_token > > ......./compare_token > > .......\next_token > > ........\first_token > > ......../first_token > > ........\first_token > > ......../first_token > > ......./next_token > > ....../smpd_hide_string_arg > > ....../smpd_hide_string_arg > > ......\SMPDU_Sock_post_write > > .......\SMPDU_Sock_post_writev > > ......./SMPDU_Sock_post_writev > > ....../SMPDU_Sock_post_write > > ...../smpd_handle_op_read > > .....sock_waiting for the next event. > > .....\SMPDU_Sock_wait > > ...../SMPDU_Sock_wait > > .....SOCK_OP_WRITE event.error = 0, result = 0, context=left > > .....\smpd_handle_op_write > > ......\smpd_state_writing_cred_ack_yes > > .......wrote cred request yes ack. > > .......\SMPDU_Sock_post_write > > ........\SMPDU_Sock_post_writev > > ......../SMPDU_Sock_post_writev > > ......./SMPDU_Sock_post_write > > ....../smpd_state_writing_cred_ack_yes > > ...../smpd_handle_op_write > > .....sock_waiting for the next event. > > .....\SMPDU_Sock_wait > > ...../SMPDU_Sock_wait > > .....SOCK_OP_WRITE event.error = 0, result = 0, context=left > > .....\smpd_handle_op_write > > ......\smpd_state_writing_account > > .......wrote account: 'Utilisateur' > > .......\smpd_encrypt_data > > ......./smpd_encrypt_data > > .......\SMPDU_Sock_post_write > > ........\SMPDU_Sock_post_writev > > ......../SMPDU_Sock_post_writev > > ......./SMPDU_Sock_post_write > > ....../smpd_state_writing_account > > ...../smpd_handle_op_write > > .....sock_waiting for the next event. > > .....\SMPDU_Sock_wait > > ...../SMPDU_Sock_wait > > .....SOCK_OP_WRITE event.error = 0, result = 0, context=left > > .....\smpd_handle_op_write > > ......\smpd_hide_string_arg > > .......\first_token > > ......./first_token > > .......\compare_token > > ......./compare_token > > .......\next_token > > ........\first_token > > ......../first_token > > ........\first_token > > ......../first_token > > ......./next_token > > ....../smpd_hide_string_arg > > ....../smpd_hide_string_arg > > .......\smpd_hide_string_arg > > ........\first_token > > ......../first_token > > ........\compare_token > > ......../compare_token > > ........\next_token > > .........\first_token > > ........./first_token > > .........\first_token > > ........./first_token > > ......../next_token > > ......./smpd_hide_string_arg > > ......./smpd_hide_string_arg > > .......\SMPDU_Sock_post_read > > ........\SMPDU_Sock_post_readv > > ......../SMPDU_Sock_post_readv > > ......./SMPDU_Sock_post_read > > ......\smpd_hide_string_arg > > .......\first_token > > ......./first_token > > .......\compare_token > > ......./compare_token > > .......\next_token > > ........\first_token > > ......../first_token > > ........\first_token > > ......../first_token > > ......./next_token > > ....../smpd_hide_string_arg > > ....../smpd_hide_string_arg > > ...../smpd_handle_op_write > > .....sock_waiting for the next event. > > .....\SMPDU_Sock_wait > > ...../SMPDU_Sock_wait > > .....SOCK_OP_READ event.error = 0, result = 0, context=left > > .....\smpd_handle_op_read > > ......\smpd_state_reading_process_result > > .......read process session result: 'FAIL' > > .......\smpd_hide_string_arg > > ........\first_token > > ......../first_token > > ........\compare_token > > ......../compare_token > > ........\next_token > > .........\first_token > > ........./first_token > > .........\first_token > > ........./first_token > > ......../next_token > > ......./smpd_hide_string_arg > > ......./smpd_hide_string_arg > > .......\smpd_hide_string_arg > > ........\first_token > > ......../first_token > > ........\compare_token > > ......../compare_token > > ........\next_token > > .........\first_token > > ........./first_token > > .........\first_token > > ........./first_token > > ......../next_token > > ......./smpd_hide_string_arg > > ......./smpd_hide_string_arg > > Credentials for Utilisateur rejected connecting to Benoit > > .......process session rejected > > .......\SMPDU_Sock_post_close > > ........\SMPDU_Sock_post_read > > .........\SMPDU_Sock_post_readv > > ........./SMPDU_Sock_post_readv > > ......../SMPDU_Sock_post_read > > ......./SMPDU_Sock_post_close > > .......\smpd_post_abort_command > > ........\smpd_create_command > > .........\smpd_init_command > > ........./smpd_init_command > > ......../smpd_create_command > > ........\smpd_add_command_arg > > ......../smpd_add_command_arg > > ........\smpd_command_destination > > .........0 -> 0 : returning NULL context > > ......../smpd_command_destination > > Aborting: Unable to connect to Benoit > > ......./smpd_post_abort_command > > .......\smpd_exit > > ........\smpd_kill_all_processes > > ......../smpd_kill_all_processes > > ........\smpd_finalize_drive_maps > > ......../smpd_finalize_drive_maps > > ........\smpd_dbs_finalize > > ......../smpd_dbs_finalize > > ........\SMPDU_Sock_finalize > > ......../SMPDU_Sock_finalize > > > > C:\Users\Utilisateur> > > > >> Hi, > >> > >> Looks like you missed the "-" before the status ("smpd -status" not > >> > >> "smpd status") argument. > >> > >> It also looks like you have multiple MPI libraries installed in your > >> > >> system. Try running this command (full path to mpiexec and smpd), > >> > >> # C:\Progra~1\MPICH2\bin\smpd -status > >> > >> # C:\Progra~1\MPICH2\bin\mpiexec -verbose -n 2 > >> C:\Progra~1\MPICH2\examples\cpi.exe > >> > >> > >> Regards, > >> Jayesh > >> > >> ----- Original Message ----- > >> From: "spatiogis" <geo(a)spatiogis.fr> > >> To: "Jayesh Krishna" <jayesh(a)mcs.anl.gov> > >> Sent: Friday, May 3, 2013 11:05:34 AM > >> Subject: Re: [mpich-discuss] install + config on windows > >> > >> Hello, > >> > >> C:\Users\Utilisateur>smpd status > >> Unexpected parameters: status > >> > >> C:\Users\Utilisateur>mpiexec -verbose -n 2 > >> C:\Progra~1\MPICH2\examples\cpi.exe > >> Unknown option: -verbose > >> > >> ------------------------------------------------------------------------- > >> ---- C:\Program Files\MPICH2\examples>mpiexec -verbose -n 2 cpi.exe > >> Unknown option: -verbose > >> > >> C:\Program Files\MPICH2\examples>smpd status > >> Unexpected parameters: status > >> ------------------------------------------------------------------------- > >> ---- > >> > >> regards, Ben > >> > >>> Hi, > >>> > >>> Ok. Please send us the output of the following commands, > >>> > >>> # smpd -status > >>> # mpiexec -verbose -n 2 C:\Progra~1\MPICH2\examples\cpi.exe > >>> > >>> Please copy-paste the command and the complete output in your email. > >>> > >>> Regards, > >>> Jayesh > >>> > >>> > >>> ----- Original Message ----- > >>> From: "spatiogis" <geo(a)spatiogis.fr> > >>> To: discuss(a)mpich.org > >>> Sent: Friday, May 3, 2013 1:46:53 AM > >>> Subject: Re: [mpich-discuss] install + config on windows > >>> > >>> Hello > >>> > >>>> (PS: I am assuming from your reply in the previous email that you can > >>>> run a command like "mpiexec -n 2 C:\Progra~1\MPICH2\examples\cpi.exe" > >>>> correctly) > >>>> > >>> In fact this command doesn't run. > >>> > >>> The message is this one > >>> > >>> [01:11728]....ERROR:unable to read the cmd header on the pmi context, > >>> > >>> Error = -1 > >>> > >>> Ben > >>> > >>>> ----- Original Message ----- > >>>> From: "spatiogis" <geo(a)spatiogis.fr> > >>>> To: "Jayesh Krishna" <jayesh(a)mcs.anl.gov> > >>>> Sent: Thursday, May 2, 2013 10:48:56 AM > >>>> Subject: Re: [mpich-discuss] install + config on windows > >>>> > >>>> Hello, > >>>> > >>>>> Hi, > >>>>> > >>>>> Are you able to run any other MPI programs? Try running the example > >>>>> > >>>>> program, cpi.exe (C:\Program Files\MPICH2\examples\cpi.exe), to make > >>>>> sure that your MPICH2 installation works. > >>>>> > >>>> yes it does work > >>>> > >>>>> Installing MPICH2 on Windows 7 typically requires you to uninstall > >>>>> > >>>>> any > >>>>> previous versions of MPICH2, launch an administrative command promt > >>>>> and > >>>>> run "msiexec /i mpich2-installer.msi" to install MPICH2. > >>>>> > >>>> yes it 's been installed like this... > >>>> > >>>> In wmpiconfig, the message is the following in the 'Get settings' > >>>> > >>>> line. > >>>> > >>>> Credentials for Utilisateur rejected connecting to host > >>>> Aborting: Unable to connect to host > >>>> > >>>> The software I try to use is Taudem, which is intergrated inside > >>>> > >>>> Qgis. > >>>> Launching a taudem process inside Qgis gives the same message. > >>>> > >>>>> Regards, > >>>>> Jayesh > >>>>> > >>>> Sincerely, Ben > >>>> > >>>>> ----- Original Message ----- > >>>>> From: "spatiogis" <geo(a)spatiogis.fr> > >>>>> To: discuss(a)mpich.org > >>>>> Sent: Thursday, May 2, 2013 10:08:23 AM > >>>>> Subject: Re: [mpich-discuss] install + config on windows > >>>>> > >>>>> Hello, > >>>>> > >>>>> in my case Mpich is normally used to run .exe programs. I guess that > >>>>> > >>>>> they > >>>>> are already compiled... > >>>>> > >>>>> The .exe files are integrated into a software, and accessed from > >>>>> > >>>>> menus > >>>>> inside it. When I run one of the programs, the answer is actually > >>>>> "unable > >>>>> to query host". > >>>>> > >>>>> At the end, the process is not realised. It seems that this 'host' > >>>>> > >>>>> question is a problem to the software... > >>>>> > >>>>> Sincerely, > >>>>> > >>>>> Ben. > >>>>> > >>>>>> Hi, > >>>>>> > >>>>>> You can download MPICH2 binaries for Windows at > >>>>>> > >>>>>> http://www.mpich.org/downloads/ . > >>>>>> > >>>>>> You need to compile your MPI programs with MPICH2 to make it work. > >>>>>> > >>>>>> I > >>>>>> would recommend recompiling your code after you install MPICH2 (If > >>>>>> you > >>>>>> have MPI program binaries pre-built with MPICH2 - instead of > >>>>>> compiling > >>>>>> them on your own - make sure that you install the same version of > >>>>>> MPICH2 > >>>>>> that was used to build the binaries). > >>>>>> > >>>>>> The wmpiregister program has a bug and you can ignore this error > >>>>>> > >>>>>> message ("...unable to query host"). Can you run your MPI program > >>>>>> using > >>>>>> mpiexec from a command prompt? > >>>>>> > >>>>>> Regards, > >>>>>> Jayesh > >>>>>> > >>>>>> ----- Original Message ----- > >>>>>> From: "spatiogis" <geo(a)spatiogis.fr> > >>>>>> To: discuss(a)mpich.org > >>>>>> Sent: Tuesday, April 30, 2013 9:26:35 AM > >>>>>> Subject: [mpich-discuss] install + config on windows > >>>>>> > >>>>>> Hello, > >>>>>> > >>>>>> I'm not very good at computing, but I would like to install Mpich2 > >>>>>> > >>>>>> on > >>>>>> windows 7 - 64 bits. There is only one pc, with one user plus the > >>>>>> admin, > >>>>>> and a simple core processor. > >>>>>> > >>>>>> I would like to know if it's mandatory to have compiling softwares > >>>>>> > >>>>>> with > >>>>>> it to make it work, whereas it is asked in this case only to make > >>>>>> run > >>>>>> another software, and not for compiling (that would maybe save some > >>>>>> disk > >>>>>> space and simplify the installation) ? > >>>>>> > >>>>>> My second issue is that I must be missing something about the > >>>>>> > >>>>>> server > >>>>>> configuration. I have installed Mpich from the .msi file, then > >>>>>> configured > >>>>>> the wmpiregister program with the Domain/user informations. > >>>>>> > >>>>>> There is this message displayed when trying to connect in the > >>>>>> > >>>>>> 'configurable settings' window : 'MPICH2 not installed or unable to > >>>>>> query > >>>>>> the host'. > >>>>>> > >>>>>> What is the host actually ? > >>>>>> > >>>>>> I know I am starting from very far, I am sorry for these very > >>>>>> > >>>>>> simple > >>>>>> questions. Thanks if you can reply me, that would certainly save me > >>>>>> some > >>>>>> long hours of reading and testing ;) > >>>>>> > >>>>>> sincerely, > >>>>>> > >>>>>> Ben > >>>>>> > >>>>>> _______________________________________________ > >>>>>> 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] ckpoint-num error
by Wesley Bland 11 Jun '13

11 Jun '13

Did you check if there's actually anything in the checkpoint files? If they're empty, that probably means that you're checkpointing too frequently. On Jun 10, 2013, at 5:17 PM, john donald <johnd9886(a)gmail.com> wrote: > i raised it to 20 sec but same results > sorry i am new to checkpoint restart > i am trying this initially on one multicore pc > how should it look like if the restart succeed? should it work in the same terminal in which i am running restart command > my test app has 5000 iterations , checkpoint is taken at iteration no 300 for example , if i choose to restart from this checkpoint file should it restart near this iteration no 300 > > > 2013/6/6 Wesley Bland <wbland(a)mcs.anl.gov> > Is there actually anything in those checkpoints? With a checkpoint happening every 4 seconds you may be overdoing it. > > Wesley > > On Jun 5, 2013, at 2:14 PM, Rajeev Thakur <thakur(a)mcs.anl.gov> wrote: > > > I don't know, but see if anything on this page helps: > > http://wiki.mpich.org/mpich/index.php/Checkpointing > > > > On Jun 5, 2013, at 4:09 PM, john donald wrote: > > > >> > >> > >> ---------- Forwarded message ---------- > >> From: john donald <johnd9886(a)gmail.com> > >> Date: 2013/6/3 > >> Subject: ckpoint-num error > >> To: mpich-discuss(a)mcs.anl.gov > >> > >> > >> i used mpiexec with checkpoint and created two checkpoint files: > >> > >> mpiexec -ckpointlib blcr -ckpoint-prefix /home/john/ckpts/app.ckpoint -ckpoint-interval 4 -n 4 /home/john/app/md > >> > >> context-num0-0-0 > >> context-num1-0-0 > >> > >> > >> i am trying to make a restart > >> mpiexec -ckpointlib blcr -ckpoint-prefix /home/john/ckpts/app.ckpoint -n 4 -ckpoint-num 1 > >> > >> but nothing happened it just hangs > >> i also tried: > >> mpiexec -ckpointlib blcr -ckpoint-prefix /home/john/ckpts/app.ckpoint -n 4 -ckpoint-num 0-0-0 > >> also hangs > >> > >> _______________________________________________ > >> 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 > _______________________________________________ > 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] Fwd: ckpoint-num error
by john donald 10 Jun '13

10 Jun '13

i raised it to 20 sec but same results sorry i am new to checkpoint restart i am trying this initially on one multicore pc how should it look like if the restart succeed? should it work in the same terminal in which i am running restart command my test app has 5000 iterations , checkpoint is taken at iteration no 300 for example , if i choose to restart from this checkpoint file should it restart near this iteration no 300 2013/6/6 Wesley Bland <wbland(a)mcs.anl.gov> > Is there actually anything in those checkpoints? With a checkpoint > happening every 4 seconds you may be overdoing it. > > Wesley > > On Jun 5, 2013, at 2:14 PM, Rajeev Thakur <thakur(a)mcs.anl.gov> wrote: > > > I don't know, but see if anything on this page helps: > > http://wiki.mpich.org/mpich/index.php/Checkpointing > > > > On Jun 5, 2013, at 4:09 PM, john donald wrote: > > > >> > >> > >> ---------- Forwarded message ---------- > >> From: john donald <johnd9886(a)gmail.com> > >> Date: 2013/6/3 > >> Subject: ckpoint-num error > >> To: mpich-discuss(a)mcs.anl.gov > >> > >> > >> i used mpiexec with checkpoint and created two checkpoint files: > >> > >> mpiexec -ckpointlib blcr -ckpoint-prefix /home/john/ckpts/app.ckpoint > -ckpoint-interval 4 -n 4 /home/john/app/md > >> > >> context-num0-0-0 > >> context-num1-0-0 > >> > >> > >> i am trying to make a restart > >> mpiexec -ckpointlib blcr -ckpoint-prefix /home/john/ckpts/app.ckpoint > -n 4 -ckpoint-num 1 > >> > >> but nothing happened it just hangs > >> i also tried: > >> mpiexec -ckpointlib blcr -ckpoint-prefix /home/john/ckpts/app.ckpoint > -n 4 -ckpoint-num 0-0-0 > >> also hangs > >> > >> _______________________________________________ > >> 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 > _______________________________________________ > 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] MPE is available in mpich-3.0.4 ? rlog doesn't work in configure process.
by Jeff Hammond 10 Jun '13

10 Jun '13

Okay, I guess this is a bug in the autoconf. I'm glad you have identified the workaround. I'll put this in Trac so that it doesn't get lost. Jeff On Mon, Jun 10, 2013 at 1:27 PM, fernando_luz <fernando_luz(a)tpn.usp.br> wrote: > Jeff, > > I ran your configuration and I obtained the same error (I attached > config_01.log) > > I think the main problem is in the composition of compile line > (config_01.log:145), the include path and the library path was found, but > not inserted in a correct way (without -I and -L). > > When I specified the -I for --with-mpiinc and -L for --with-mpilibs, the > configuration works (config_02.log) > > I use the autoconf version 2.68, and to generate the configure, I ran > autogen.sh, but some warnings was shown (warning_autogen.log) > > Fernando > > > > On 06/10/2013 02:56 PM, Jeff Hammond wrote: >> >> I don't think there's anything wrong with this, but can you confirm >> that the following does not work? >> >> ./configure --prefix=/home/fernando_luz/usr/mpe >> --with-mpicc=/home/fernando_luz/usr/mpich/bin/mpicc --disable-f77 >> >> I would expect that --with-mpicc is sufficient and that mpilibs and >> mpiinc can be populated automatically using this information. >> >> Jeff >> >> On Mon, Jun 10, 2013 at 8:26 AM, fernando_luz <fernando_luz(a)tpn.usp.br> >> wrote: >>> >>> I made this modification in configure and I have success >>> >>> ./configure --prefix=/home/fernando_luz/usr/mpe >>> --with-mpicc=/home/fernando_luz/usr/mpich/bin/mpicc >>> --with-mpilibs=-L/home/fernando_luz/usr/mpich/lib/ >>> --with-mpiinc=-I/home/fernando_luz/usr/mpich/include/ --disable-f77 >>> >>> but it's the correct way to execute the configure? >>> >>> Regards >>> >>> >>> On 06/10/2013 11:16 AM, fernando_luz wrote: >>> >>> Hi Jeff and Antonio, >>> >>> >>> I checked my mpich installation and everything is ok. >>> >>> I used the variables CC=mpicc and MPI_CC=mpicc and I don't have any >>> success. >>> >>> Looking the log, my guess is the command to link the conftest.c wasn't >>> built >>> in a correct way, because the Include flag '-I' and the library path '-L' >>> was not inserted in the command line. >>> >>> configure:4099: /home/fernando_luz/usr/mpich/bin/mpicc -o conftest >>> /home/fernando_luz/usr/mpich/include/ conftest.c >>> /home/fernando_luz/usr/mpich/lib/ >&5 >>> >>> Running this command in the terminal (with -I and -L) I have success. >>> >>> It's my first time using the autoconf, and I don't have an idea where I >>> can >>> modify this. >>> >>> Regards >>> >>> On 06/07/2013 07:38 PM, Jeff Hammond wrote: >>> >>> Did you read it? It's got the reason that configure is failing pretty >>> clearly stated. You need to debug your configure invocation. Maybe use >>> CC=mpicc etc instead... >>> >>> Jeff >>> >>> Sent from my iPhone >>> >>> On Jun 7, 2013, at 3:04 PM, fernando_luz <fernando_luz(a)tpn.usp.br> wrote: >>> >>> In attachment. >>> >>> Fernando >>> >>> On 06/07/2013 04:56 PM, Jeff Hammond wrote: >>> >>> please attach config.log. >>> >>> jeff >>> >>> On Fri, Jun 7, 2013 at 1:07 PM, fernando_luz <fernando_luz(a)tpn.usp.br> >>> wrote: >>> >>> Hi Rajeev, >>> >>> Thanks for the answers. >>> >>> I get the source code in repository, but I didn't succeed in the compile >>> process. >>> I ran the autogen.sh and after this I tried to configure my installation >>> and >>> I received the following error message. >>> >>> >>> fernando_luz@TPN000300:~/git/mpe$ ./configure >>> --prefix=/home/fernando_luz/usr/mpe >>> --with-mpicc=/home/fernando_luz/usr/mpich/bin/mpicc >>> --with-mpilibs=/home/fernando_luz/usr/mpich/lib/ >>> --with-mpiinc=/home/fernando_luz/usr/mpich/include/ >>> Configuring MPE Profiling System with >>> '--prefix=/home/fernando_luz/usr/mpe' >>> '--with-mpicc=/home/fernando_luz/usr/mpich/bin/mpicc' >>> '--with-mpilibs=/home/fernando_luz/usr/mpich/lib/' >>> '--with-mpiinc=/home/fernando_luz/usr/mpich/include/' >>> 'MPI_CC=/home/fernando_luz/usr/mpich/bin/mpicc' >>> 'MPI_INC=/home/fernando_luz/usr/mpich/include' >>> 'MPI_LIBS=/home/fernando_luz/usr/mpich/lib' >>> checking for current directory name... /home/fernando_luz/git/mpe >>> checking gnumake... yes using --no-print-directory >>> checking BSD 4.4 make... no - whew >>> checking OSF V3 make... no >>> checking for virtual path format... VPATH >>> User supplied MPI implmentation (Good Luck!) >>> checking for leftover Makefiles in subpackages ... none >>> checking for gcc... cc >>> checking whether the C compiler works... yes >>> checking for C compiler default output file name... a.out >>> checking for suffix of executables... >>> checking whether we are cross compiling... no >>> checking for suffix of object files... o >>> checking whether we are using the GNU C compiler... yes >>> checking whether cc accepts -g... yes >>> checking for cc option to accept ISO C89... none needed >>> checking whether MPI_CC has been set ... >>> /home/fernando_luz/usr/mpich/bin/mpicc >>> checking whether we are using the GNU Fortran 77 compiler... no >>> checking whether f77 accepts -g... no >>> checking whether MPI_F77 has been set ... f77 >>> checking for the linkage of the supplied MPI C definitions ... no >>> configure: error: Cannot link with basic MPI C program! >>> Check your MPI include paths, MPI libraries and MPI CC compiler >>> >>> Where /home/fernando_luz/usr/mpich/ is my mpi installation (MPICH-3.0.4). >>> >>> I prefer to use the mpe in repository because in the site, the last >>> version >>> was dated in 2010 and in the git repository the last commit was in 2012. >>> >>> Regards >>> >>> Fernando >>> >>> >>> >>> On 06/04/2013 03:05 PM, Rajeev Thakur wrote: >>> >>> It can be downloaded from >>> http://www.mcs.anl.gov/research/projects/perfvis/download/index.htm. >>> >>> The source repository is at http://git.mpich.org/mpe.git/ >>> >>> Rajeev >>> >>> On Jun 4, 2013, at 12:48 PM, Jeff Hammond wrote: >>> >>> MPE isn't actively developed and should sit strictly on top of any MPI >>> implementation so you can just grab MPE from an older release of >>> MPICH. >>> >>> My guess is that MPE will be a standalone download at some point in the >>> future. >>> >>> Jeff >>> >>> On Tue, Jun 4, 2013 at 10:59 AM, fernando_luz <fernando_luz(a)tpn.usp.br> >>> wrote: >>> >>> Hi, >>> >>> I didn't find the MPE source in mpich-3.0.4 package. Where I can >>> download >>> the source? It is still compatible with mpich? >>> >>> And I tried to install the logging support available in this release, >>> but my >>> try didn't was successful. I received the follow error: >>> >>> /home/fernando_luz/software/mpich-3.0.4/src/util/logging/rlog/configure: >>> line 3694: PAC_CC_SUBDIR_SHLIBS: command not found >>> configure: creating ./config.status >>> config.status: error: cannot find input file: `Makefile.in' >>> configure: error: src/util/logging/rlog configure failed >>> >>> I attached the c.txt file used in the configuration. >>> >>> Regards >>> >>> Fernando >>> >>> _______________________________________________ >>> 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 >>> ALCF docs: http://www.alcf.anl.gov/user-guides >>> _______________________________________________ >>> 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 >>> >>> _______________________________________________ >>> discuss mailing list discuss(a)mpich.org >>> To manage subscription options or unsubscribe: >>> https://lists.mpich.org/mailman/listinfo/discuss >>> >>> >>> <config.log> >>> _______________________________________________ >>> 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 >>> >>> >>> _______________________________________________ >>> 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 >> >> >> > > > _______________________________________________ > 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 ALCF docs: http://www.alcf.anl.gov/user-guides

1 0

Re: [mpich-discuss] MPE is available in mpich-3.0.4 ? rlog doesn't work in configure process.
by fernando_luz 10 Jun '13

10 Jun '13

Jeff, I ran your configuration and I obtained the same error (I attached config_01.log) I think the main problem is in the composition of compile line (config_01.log:145), the include path and the library path was found, but not inserted in a correct way (without -I and -L). When I specified the -I for --with-mpiinc and -L for --with-mpilibs, the configuration works (config_02.log) I use the autoconf version 2.68, and to generate the configure, I ran autogen.sh, but some warnings was shown (warning_autogen.log) Fernando On 06/10/2013 02:56 PM, Jeff Hammond wrote: > I don't think there's anything wrong with this, but can you confirm > that the following does not work? > > ./configure --prefix=/home/fernando_luz/usr/mpe > --with-mpicc=/home/fernando_luz/usr/mpich/bin/mpicc --disable-f77 > > I would expect that --with-mpicc is sufficient and that mpilibs and > mpiinc can be populated automatically using this information. > > Jeff > > On Mon, Jun 10, 2013 at 8:26 AM, fernando_luz <fernando_luz(a)tpn.usp.br> wrote: >> I made this modification in configure and I have success >> >> ./configure --prefix=/home/fernando_luz/usr/mpe >> --with-mpicc=/home/fernando_luz/usr/mpich/bin/mpicc >> --with-mpilibs=-L/home/fernando_luz/usr/mpich/lib/ >> --with-mpiinc=-I/home/fernando_luz/usr/mpich/include/ --disable-f77 >> >> but it's the correct way to execute the configure? >> >> Regards >> >> >> On 06/10/2013 11:16 AM, fernando_luz wrote: >> >> Hi Jeff and Antonio, >> >> >> I checked my mpich installation and everything is ok. >> >> I used the variables CC=mpicc and MPI_CC=mpicc and I don't have any success. >> >> Looking the log, my guess is the command to link the conftest.c wasn't built >> in a correct way, because the Include flag '-I' and the library path '-L' >> was not inserted in the command line. >> >> configure:4099: /home/fernando_luz/usr/mpich/bin/mpicc -o conftest >> /home/fernando_luz/usr/mpich/include/ conftest.c >> /home/fernando_luz/usr/mpich/lib/ >&5 >> >> Running this command in the terminal (with -I and -L) I have success. >> >> It's my first time using the autoconf, and I don't have an idea where I can >> modify this. >> >> Regards >> >> On 06/07/2013 07:38 PM, Jeff Hammond wrote: >> >> Did you read it? It's got the reason that configure is failing pretty >> clearly stated. You need to debug your configure invocation. Maybe use >> CC=mpicc etc instead... >> >> Jeff >> >> Sent from my iPhone >> >> On Jun 7, 2013, at 3:04 PM, fernando_luz <fernando_luz(a)tpn.usp.br> wrote: >> >> In attachment. >> >> Fernando >> >> On 06/07/2013 04:56 PM, Jeff Hammond wrote: >> >> please attach config.log. >> >> jeff >> >> On Fri, Jun 7, 2013 at 1:07 PM, fernando_luz <fernando_luz(a)tpn.usp.br> >> wrote: >> >> Hi Rajeev, >> >> Thanks for the answers. >> >> I get the source code in repository, but I didn't succeed in the compile >> process. >> I ran the autogen.sh and after this I tried to configure my installation and >> I received the following error message. >> >> >> fernando_luz@TPN000300:~/git/mpe$ ./configure >> --prefix=/home/fernando_luz/usr/mpe >> --with-mpicc=/home/fernando_luz/usr/mpich/bin/mpicc >> --with-mpilibs=/home/fernando_luz/usr/mpich/lib/ >> --with-mpiinc=/home/fernando_luz/usr/mpich/include/ >> Configuring MPE Profiling System with '--prefix=/home/fernando_luz/usr/mpe' >> '--with-mpicc=/home/fernando_luz/usr/mpich/bin/mpicc' >> '--with-mpilibs=/home/fernando_luz/usr/mpich/lib/' >> '--with-mpiinc=/home/fernando_luz/usr/mpich/include/' >> 'MPI_CC=/home/fernando_luz/usr/mpich/bin/mpicc' >> 'MPI_INC=/home/fernando_luz/usr/mpich/include' >> 'MPI_LIBS=/home/fernando_luz/usr/mpich/lib' >> checking for current directory name... /home/fernando_luz/git/mpe >> checking gnumake... yes using --no-print-directory >> checking BSD 4.4 make... no - whew >> checking OSF V3 make... no >> checking for virtual path format... VPATH >> User supplied MPI implmentation (Good Luck!) >> checking for leftover Makefiles in subpackages ... none >> checking for gcc... cc >> checking whether the C compiler works... yes >> checking for C compiler default output file name... a.out >> checking for suffix of executables... >> checking whether we are cross compiling... no >> checking for suffix of object files... o >> checking whether we are using the GNU C compiler... yes >> checking whether cc accepts -g... yes >> checking for cc option to accept ISO C89... none needed >> checking whether MPI_CC has been set ... >> /home/fernando_luz/usr/mpich/bin/mpicc >> checking whether we are using the GNU Fortran 77 compiler... no >> checking whether f77 accepts -g... no >> checking whether MPI_F77 has been set ... f77 >> checking for the linkage of the supplied MPI C definitions ... no >> configure: error: Cannot link with basic MPI C program! >> Check your MPI include paths, MPI libraries and MPI CC compiler >> >> Where /home/fernando_luz/usr/mpich/ is my mpi installation (MPICH-3.0.4). >> >> I prefer to use the mpe in repository because in the site, the last version >> was dated in 2010 and in the git repository the last commit was in 2012. >> >> Regards >> >> Fernando >> >> >> >> On 06/04/2013 03:05 PM, Rajeev Thakur wrote: >> >> It can be downloaded from >> http://www.mcs.anl.gov/research/projects/perfvis/download/index.htm. >> >> The source repository is at http://git.mpich.org/mpe.git/ >> >> Rajeev >> >> On Jun 4, 2013, at 12:48 PM, Jeff Hammond wrote: >> >> MPE isn't actively developed and should sit strictly on top of any MPI >> implementation so you can just grab MPE from an older release of >> MPICH. >> >> My guess is that MPE will be a standalone download at some point in the >> future. >> >> Jeff >> >> On Tue, Jun 4, 2013 at 10:59 AM, fernando_luz <fernando_luz(a)tpn.usp.br> >> wrote: >> >> Hi, >> >> I didn't find the MPE source in mpich-3.0.4 package. Where I can >> download >> the source? It is still compatible with mpich? >> >> And I tried to install the logging support available in this release, >> but my >> try didn't was successful. I received the follow error: >> >> /home/fernando_luz/software/mpich-3.0.4/src/util/logging/rlog/configure: >> line 3694: PAC_CC_SUBDIR_SHLIBS: command not found >> configure: creating ./config.status >> config.status: error: cannot find input file: `Makefile.in' >> configure: error: src/util/logging/rlog configure failed >> >> I attached the c.txt file used in the configuration. >> >> Regards >> >> Fernando >> >> _______________________________________________ >> 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 >> ALCF docs: http://www.alcf.anl.gov/user-guides >> _______________________________________________ >> 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 >> >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss >> >> >> <config.log> >> _______________________________________________ >> 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 >> >> >> _______________________________________________ >> 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] MPE is available in mpich-3.0.4 ? rlog doesn't work in configure process.
by Jeff Hammond 10 Jun '13

10 Jun '13

I don't think there's anything wrong with this, but can you confirm that the following does not work? ./configure --prefix=/home/fernando_luz/usr/mpe --with-mpicc=/home/fernando_luz/usr/mpich/bin/mpicc --disable-f77 I would expect that --with-mpicc is sufficient and that mpilibs and mpiinc can be populated automatically using this information. Jeff On Mon, Jun 10, 2013 at 8:26 AM, fernando_luz <fernando_luz(a)tpn.usp.br> wrote: > I made this modification in configure and I have success > > ./configure --prefix=/home/fernando_luz/usr/mpe > --with-mpicc=/home/fernando_luz/usr/mpich/bin/mpicc > --with-mpilibs=-L/home/fernando_luz/usr/mpich/lib/ > --with-mpiinc=-I/home/fernando_luz/usr/mpich/include/ --disable-f77 > > but it's the correct way to execute the configure? > > Regards > > > On 06/10/2013 11:16 AM, fernando_luz wrote: > > Hi Jeff and Antonio, > > > I checked my mpich installation and everything is ok. > > I used the variables CC=mpicc and MPI_CC=mpicc and I don't have any success. > > Looking the log, my guess is the command to link the conftest.c wasn't built > in a correct way, because the Include flag '-I' and the library path '-L' > was not inserted in the command line. > > configure:4099: /home/fernando_luz/usr/mpich/bin/mpicc -o conftest > /home/fernando_luz/usr/mpich/include/ conftest.c > /home/fernando_luz/usr/mpich/lib/ >&5 > > Running this command in the terminal (with -I and -L) I have success. > > It's my first time using the autoconf, and I don't have an idea where I can > modify this. > > Regards > > On 06/07/2013 07:38 PM, Jeff Hammond wrote: > > Did you read it? It's got the reason that configure is failing pretty > clearly stated. You need to debug your configure invocation. Maybe use > CC=mpicc etc instead... > > Jeff > > Sent from my iPhone > > On Jun 7, 2013, at 3:04 PM, fernando_luz <fernando_luz(a)tpn.usp.br> wrote: > > In attachment. > > Fernando > > On 06/07/2013 04:56 PM, Jeff Hammond wrote: > > please attach config.log. > > jeff > > On Fri, Jun 7, 2013 at 1:07 PM, fernando_luz <fernando_luz(a)tpn.usp.br> > wrote: > > Hi Rajeev, > > Thanks for the answers. > > I get the source code in repository, but I didn't succeed in the compile > process. > I ran the autogen.sh and after this I tried to configure my installation and > I received the following error message. > > > fernando_luz@TPN000300:~/git/mpe$ ./configure > --prefix=/home/fernando_luz/usr/mpe > --with-mpicc=/home/fernando_luz/usr/mpich/bin/mpicc > --with-mpilibs=/home/fernando_luz/usr/mpich/lib/ > --with-mpiinc=/home/fernando_luz/usr/mpich/include/ > Configuring MPE Profiling System with '--prefix=/home/fernando_luz/usr/mpe' > '--with-mpicc=/home/fernando_luz/usr/mpich/bin/mpicc' > '--with-mpilibs=/home/fernando_luz/usr/mpich/lib/' > '--with-mpiinc=/home/fernando_luz/usr/mpich/include/' > 'MPI_CC=/home/fernando_luz/usr/mpich/bin/mpicc' > 'MPI_INC=/home/fernando_luz/usr/mpich/include' > 'MPI_LIBS=/home/fernando_luz/usr/mpich/lib' > checking for current directory name... /home/fernando_luz/git/mpe > checking gnumake... yes using --no-print-directory > checking BSD 4.4 make... no - whew > checking OSF V3 make... no > checking for virtual path format... VPATH > User supplied MPI implmentation (Good Luck!) > checking for leftover Makefiles in subpackages ... none > checking for gcc... cc > checking whether the C compiler works... yes > checking for C compiler default output file name... a.out > checking for suffix of executables... > checking whether we are cross compiling... no > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether cc accepts -g... yes > checking for cc option to accept ISO C89... none needed > checking whether MPI_CC has been set ... > /home/fernando_luz/usr/mpich/bin/mpicc > checking whether we are using the GNU Fortran 77 compiler... no > checking whether f77 accepts -g... no > checking whether MPI_F77 has been set ... f77 > checking for the linkage of the supplied MPI C definitions ... no > configure: error: Cannot link with basic MPI C program! > Check your MPI include paths, MPI libraries and MPI CC compiler > > Where /home/fernando_luz/usr/mpich/ is my mpi installation (MPICH-3.0.4). > > I prefer to use the mpe in repository because in the site, the last version > was dated in 2010 and in the git repository the last commit was in 2012. > > Regards > > Fernando > > > > On 06/04/2013 03:05 PM, Rajeev Thakur wrote: > > It can be downloaded from > http://www.mcs.anl.gov/research/projects/perfvis/download/index.htm. > > The source repository is at http://git.mpich.org/mpe.git/ > > Rajeev > > On Jun 4, 2013, at 12:48 PM, Jeff Hammond wrote: > > MPE isn't actively developed and should sit strictly on top of any MPI > implementation so you can just grab MPE from an older release of > MPICH. > > My guess is that MPE will be a standalone download at some point in the > future. > > Jeff > > On Tue, Jun 4, 2013 at 10:59 AM, fernando_luz <fernando_luz(a)tpn.usp.br> > wrote: > > Hi, > > I didn't find the MPE source in mpich-3.0.4 package. Where I can > download > the source? It is still compatible with mpich? > > And I tried to install the logging support available in this release, > but my > try didn't was successful. I received the follow error: > > /home/fernando_luz/software/mpich-3.0.4/src/util/logging/rlog/configure: > line 3694: PAC_CC_SUBDIR_SHLIBS: command not found > configure: creating ./config.status > config.status: error: cannot find input file: `Makefile.in' > configure: error: src/util/logging/rlog configure failed > > I attached the c.txt file used in the configuration. > > Regards > > Fernando > > _______________________________________________ > 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 > ALCF docs: http://www.alcf.anl.gov/user-guides > _______________________________________________ > 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 > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > > > <config.log> > _______________________________________________ > 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 > > > _______________________________________________ > 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 ALCF docs: http://www.alcf.anl.gov/user-guides

1 0

Re: [mpich-discuss] Process exited without calling finalize
by Lee, Eibhlin 10 Jun '13

10 Jun '13

Please disregard. I had forgotten to name the hosts differently. Thank you Eibhlin ________________________________ From: discuss-bounces(a)mpich.org [discuss-bounces(a)mpich.org] on behalf of Lee, Eibhlin [eibhlin.lee10(a)imperial.ac.uk] Sent: 10 June 2013 15:42 To: discuss(a)mpich.org Subject: [mpich-discuss] Process exited without calling finalize Hello, I am getting an error similar to that of some of the first MPICH versions when testing whether MPICH-3.0.4 has downloaded properly on my RaspberryPi. I downloaded and (thought) I installed mpich-3.0.4 correctly using the configure add ons --with-pm=smpd and --with-pmi=smpd I set the smpd phrase using smpd -getphrase. Did smpd -s. Then copied the image to a second machine. The test file cpi runs as expected on the master (only) and also on the slave (only). However, when I try to run cpi: mpiexec -phrase abc -machinefile file -n 2 /home/pi/examples/cpi Where abc is the phrase for both machines and file contains two IP addresses. I get the error: Fatal error in MPI_Init: Other MPI error, error stack: MPIR_Init_thread(433).................: MPID_Init(176)........................: channel initialization failed MPIDI_CH3_Init(70)....................: MPID_nem_init(238)....................: MPIDI_CH3I_Seg_commit(366)............: MPIU_SHMW_Hnd_deserialize(324)........: MPIU_SHMW_Seg_open(865)...............: MPIU_SHMW_Seg_create_attach_templ(637): open failed - No such file or directory job aborted: rank: node: exit code[: error message] 0: 129.32.139.gfd: -2 1: 129.32.139.plm: 1: process 1 exited without calling finalize where gfd and plm are the endings of the IP address. Please help me figure out what I've done wrong. Regards, Eibhlin

1 0

Process exited without calling finalize
by Lee, Eibhlin 10 Jun '13

10 Jun '13

Hello, I am getting an error similar to that of some of the first MPICH versions when testing whether MPICH-3.0.4 has downloaded properly on my RaspberryPi. I downloaded and (thought) I installed mpich-3.0.4 correctly using the configure add ons --with-pm=smpd and --with-pmi=smpd I set the smpd phrase using smpd -getphrase. Did smpd -s. Then copied the image to a second machine. The test file cpi runs as expected on the master (only) and also on the slave (only). However, when I try to run cpi: mpiexec -phrase abc -machinefile file -n 2 /home/pi/examples/cpi Where abc is the phrase for both machines and file contains two IP addresses. I get the error: Fatal error in MPI_Init: Other MPI error, error stack: MPIR_Init_thread(433).................: MPID_Init(176)........................: channel initialization failed MPIDI_CH3_Init(70)....................: MPID_nem_init(238)....................: MPIDI_CH3I_Seg_commit(366)............: MPIU_SHMW_Hnd_deserialize(324)........: MPIU_SHMW_Seg_open(865)...............: MPIU_SHMW_Seg_create_attach_templ(637): open failed - No such file or directory job aborted: rank: node: exit code[: error message] 0: 129.32.139.gfd: -2 1: 129.32.139.plm: 1: process 1 exited without calling finalize where gfd and plm are the endings of the IP address. Please help me figure out what I've done wrong. Regards, Eibhlin

1 0

Re: [mpich-discuss] MPE is available in mpich-3.0.4 ? rlog doesn't work in configure process.
by fernando_luz 10 Jun '13

10 Jun '13

I made this modification in configure and I have success ./configure --prefix=/home/fernando_luz/usr/mpe --with-mpicc=/home/fernando_luz/usr/mpich/bin/mpicc --with-mpilibs=-L/home/fernando_luz/usr/mpich/lib/ --with-mpiinc=-I/home/fernando_luz/usr/mpich/include/ --disable-f77 but it's the correct way to execute the configure? Regards On 06/10/2013 11:16 AM, fernando_luz wrote: > Hi Jeff and Antonio, > > > I checked my mpich installation and everything is ok. > > I used the variables CC=mpicc and MPI_CC=mpicc and I don't have any > success. > > Looking the log, my guess is the command to link the conftest.c wasn't > built in a correct way, because the Include flag '-I' and the library > path '-L' was not inserted in the command line. > > configure:4099: /home/fernando_luz/usr/mpich/bin/mpicc -o conftest > /home/fernando_luz/usr/mpich/include/ conftest.c > /home/fernando_luz/usr/mpich/lib/ >&5 > > Running this command in the terminal (with -I and -L) I have success. > > It's my first time using the autoconf, and I don't have an idea where > I can modify this. > > Regards > > On 06/07/2013 07:38 PM, Jeff Hammond wrote: >> Did you read it? It's got the reason that configure is failing pretty >> clearly stated. You need to debug your configure invocation. Maybe use >> CC=mpicc etc instead... >> >> Jeff >> >> Sent from my iPhone >> >> On Jun 7, 2013, at 3:04 PM, fernando_luz <fernando_luz(a)tpn.usp.br> >> wrote: >> >>> In attachment. >>> >>> Fernando >>> >>> On 06/07/2013 04:56 PM, Jeff Hammond wrote: >>>> please attach config.log. >>>> >>>> jeff >>>> >>>> On Fri, Jun 7, 2013 at 1:07 PM, fernando_luz >>>> <fernando_luz(a)tpn.usp.br> wrote: >>>>> Hi Rajeev, >>>>> >>>>> Thanks for the answers. >>>>> >>>>> I get the source code in repository, but I didn't succeed in the >>>>> compile >>>>> process. >>>>> I ran the autogen.sh and after this I tried to configure my >>>>> installation and >>>>> I received the following error message. >>>>> >>>>> >>>>> fernando_luz@TPN000300:~/git/mpe$ ./configure >>>>> --prefix=/home/fernando_luz/usr/mpe >>>>> --with-mpicc=/home/fernando_luz/usr/mpich/bin/mpicc >>>>> --with-mpilibs=/home/fernando_luz/usr/mpich/lib/ >>>>> --with-mpiinc=/home/fernando_luz/usr/mpich/include/ >>>>> Configuring MPE Profiling System with >>>>> '--prefix=/home/fernando_luz/usr/mpe' >>>>> '--with-mpicc=/home/fernando_luz/usr/mpich/bin/mpicc' >>>>> '--with-mpilibs=/home/fernando_luz/usr/mpich/lib/' >>>>> '--with-mpiinc=/home/fernando_luz/usr/mpich/include/' >>>>> 'MPI_CC=/home/fernando_luz/usr/mpich/bin/mpicc' >>>>> 'MPI_INC=/home/fernando_luz/usr/mpich/include' >>>>> 'MPI_LIBS=/home/fernando_luz/usr/mpich/lib' >>>>> checking for current directory name... /home/fernando_luz/git/mpe >>>>> checking gnumake... yes using --no-print-directory >>>>> checking BSD 4.4 make... no - whew >>>>> checking OSF V3 make... no >>>>> checking for virtual path format... VPATH >>>>> User supplied MPI implmentation (Good Luck!) >>>>> checking for leftover Makefiles in subpackages ... none >>>>> checking for gcc... cc >>>>> checking whether the C compiler works... yes >>>>> checking for C compiler default output file name... a.out >>>>> checking for suffix of executables... >>>>> checking whether we are cross compiling... no >>>>> checking for suffix of object files... o >>>>> checking whether we are using the GNU C compiler... yes >>>>> checking whether cc accepts -g... yes >>>>> checking for cc option to accept ISO C89... none needed >>>>> checking whether MPI_CC has been set ... >>>>> /home/fernando_luz/usr/mpich/bin/mpicc >>>>> checking whether we are using the GNU Fortran 77 compiler... no >>>>> checking whether f77 accepts -g... no >>>>> checking whether MPI_F77 has been set ... f77 >>>>> checking for the linkage of the supplied MPI C definitions ... no >>>>> configure: error: Cannot link with basic MPI C program! >>>>> Check your MPI include paths, MPI libraries and MPI CC compiler >>>>> >>>>> Where /home/fernando_luz/usr/mpich/ is my mpi installation >>>>> (MPICH-3.0.4). >>>>> >>>>> I prefer to use the mpe in repository because in the site, the >>>>> last version >>>>> was dated in 2010 and in the git repository the last commit was in >>>>> 2012. >>>>> >>>>> Regards >>>>> >>>>> Fernando >>>>> >>>>> >>>>> >>>>> On 06/04/2013 03:05 PM, Rajeev Thakur wrote: >>>>>> It can be downloaded from >>>>>> http://www.mcs.anl.gov/research/projects/perfvis/download/index.htm. >>>>>> >>>>>> The source repository is at http://git.mpich.org/mpe.git/ >>>>>> >>>>>> Rajeev >>>>>> >>>>>> On Jun 4, 2013, at 12:48 PM, Jeff Hammond wrote: >>>>>> >>>>>>> MPE isn't actively developed and should sit strictly on top of >>>>>>> any MPI >>>>>>> implementation so you can just grab MPE from an older release of >>>>>>> MPICH. >>>>>>> >>>>>>> My guess is that MPE will be a standalone download at some point >>>>>>> in the >>>>>>> future. >>>>>>> >>>>>>> Jeff >>>>>>> >>>>>>> On Tue, Jun 4, 2013 at 10:59 AM, fernando_luz >>>>>>> <fernando_luz(a)tpn.usp.br> >>>>>>> wrote: >>>>>>>> Hi, >>>>>>>> >>>>>>>> I didn't find the MPE source in mpich-3.0.4 package. Where I can >>>>>>>> download >>>>>>>> the source? It is still compatible with mpich? >>>>>>>> >>>>>>>> And I tried to install the logging support available in this >>>>>>>> release, >>>>>>>> but my >>>>>>>> try didn't was successful. I received the follow error: >>>>>>>> >>>>>>>> /home/fernando_luz/software/mpich-3.0.4/src/util/logging/rlog/configure: >>>>>>>> >>>>>>>> line 3694: PAC_CC_SUBDIR_SHLIBS: command not found >>>>>>>> configure: creating ./config.status >>>>>>>> config.status: error: cannot find input file: `Makefile.in' >>>>>>>> configure: error: src/util/logging/rlog configure failed >>>>>>>> >>>>>>>> I attached the c.txt file used in the configuration. >>>>>>>> >>>>>>>> Regards >>>>>>>> >>>>>>>> Fernando >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>>>>> ALCF docs: http://www.alcf.anl.gov/user-guides >>>>>>> _______________________________________________ >>>>>>> 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 >>>>> _______________________________________________ >>>>> discuss mailing list discuss(a)mpich.org >>>>> To manage subscription options or unsubscribe: >>>>> https://lists.mpich.org/mailman/listinfo/discuss >>>> >>> <config.log> >>> _______________________________________________ >>> 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 > > _______________________________________________ > 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] MPE is available in mpich-3.0.4 ? rlog doesn't work in configure process.
by fernando_luz 10 Jun '13

10 Jun '13

Hi Jeff and Antonio, I checked my mpich installation and everything is ok. I used the variables CC=mpicc and MPI_CC=mpicc and I don't have any success. Looking the log, my guess is the command to link the conftest.c wasn't built in a correct way, because the Include flag '-I' and the library path '-L' was not inserted in the command line. configure:4099: /home/fernando_luz/usr/mpich/bin/mpicc -o conftest /home/fernando_luz/usr/mpich/include/ conftest.c /home/fernando_luz/usr/mpich/lib/ >&5 Running this command in the terminal (with -I and -L) I have success. It's my first time using the autoconf, and I don't have an idea where I can modify this. Regards On 06/07/2013 07:38 PM, Jeff Hammond wrote: > Did you read it? It's got the reason that configure is failing pretty > clearly stated. You need to debug your configure invocation. Maybe use > CC=mpicc etc instead... > > Jeff > > Sent from my iPhone > > On Jun 7, 2013, at 3:04 PM, fernando_luz <fernando_luz(a)tpn.usp.br> wrote: > >> In attachment. >> >> Fernando >> >> On 06/07/2013 04:56 PM, Jeff Hammond wrote: >>> please attach config.log. >>> >>> jeff >>> >>> On Fri, Jun 7, 2013 at 1:07 PM, fernando_luz <fernando_luz(a)tpn.usp.br> wrote: >>>> Hi Rajeev, >>>> >>>> Thanks for the answers. >>>> >>>> I get the source code in repository, but I didn't succeed in the compile >>>> process. >>>> I ran the autogen.sh and after this I tried to configure my installation and >>>> I received the following error message. >>>> >>>> >>>> fernando_luz@TPN000300:~/git/mpe$ ./configure >>>> --prefix=/home/fernando_luz/usr/mpe >>>> --with-mpicc=/home/fernando_luz/usr/mpich/bin/mpicc >>>> --with-mpilibs=/home/fernando_luz/usr/mpich/lib/ >>>> --with-mpiinc=/home/fernando_luz/usr/mpich/include/ >>>> Configuring MPE Profiling System with '--prefix=/home/fernando_luz/usr/mpe' >>>> '--with-mpicc=/home/fernando_luz/usr/mpich/bin/mpicc' >>>> '--with-mpilibs=/home/fernando_luz/usr/mpich/lib/' >>>> '--with-mpiinc=/home/fernando_luz/usr/mpich/include/' >>>> 'MPI_CC=/home/fernando_luz/usr/mpich/bin/mpicc' >>>> 'MPI_INC=/home/fernando_luz/usr/mpich/include' >>>> 'MPI_LIBS=/home/fernando_luz/usr/mpich/lib' >>>> checking for current directory name... /home/fernando_luz/git/mpe >>>> checking gnumake... yes using --no-print-directory >>>> checking BSD 4.4 make... no - whew >>>> checking OSF V3 make... no >>>> checking for virtual path format... VPATH >>>> User supplied MPI implmentation (Good Luck!) >>>> checking for leftover Makefiles in subpackages ... none >>>> checking for gcc... cc >>>> checking whether the C compiler works... yes >>>> checking for C compiler default output file name... a.out >>>> checking for suffix of executables... >>>> checking whether we are cross compiling... no >>>> checking for suffix of object files... o >>>> checking whether we are using the GNU C compiler... yes >>>> checking whether cc accepts -g... yes >>>> checking for cc option to accept ISO C89... none needed >>>> checking whether MPI_CC has been set ... >>>> /home/fernando_luz/usr/mpich/bin/mpicc >>>> checking whether we are using the GNU Fortran 77 compiler... no >>>> checking whether f77 accepts -g... no >>>> checking whether MPI_F77 has been set ... f77 >>>> checking for the linkage of the supplied MPI C definitions ... no >>>> configure: error: Cannot link with basic MPI C program! >>>> Check your MPI include paths, MPI libraries and MPI CC compiler >>>> >>>> Where /home/fernando_luz/usr/mpich/ is my mpi installation (MPICH-3.0.4). >>>> >>>> I prefer to use the mpe in repository because in the site, the last version >>>> was dated in 2010 and in the git repository the last commit was in 2012. >>>> >>>> Regards >>>> >>>> Fernando >>>> >>>> >>>> >>>> On 06/04/2013 03:05 PM, Rajeev Thakur wrote: >>>>> It can be downloaded from >>>>> http://www.mcs.anl.gov/research/projects/perfvis/download/index.htm. >>>>> >>>>> The source repository is at http://git.mpich.org/mpe.git/ >>>>> >>>>> Rajeev >>>>> >>>>> On Jun 4, 2013, at 12:48 PM, Jeff Hammond wrote: >>>>> >>>>>> MPE isn't actively developed and should sit strictly on top of any MPI >>>>>> implementation so you can just grab MPE from an older release of >>>>>> MPICH. >>>>>> >>>>>> My guess is that MPE will be a standalone download at some point in the >>>>>> future. >>>>>> >>>>>> Jeff >>>>>> >>>>>> On Tue, Jun 4, 2013 at 10:59 AM, fernando_luz <fernando_luz(a)tpn.usp.br> >>>>>> wrote: >>>>>>> Hi, >>>>>>> >>>>>>> I didn't find the MPE source in mpich-3.0.4 package. Where I can >>>>>>> download >>>>>>> the source? It is still compatible with mpich? >>>>>>> >>>>>>> And I tried to install the logging support available in this release, >>>>>>> but my >>>>>>> try didn't was successful. I received the follow error: >>>>>>> >>>>>>> /home/fernando_luz/software/mpich-3.0.4/src/util/logging/rlog/configure: >>>>>>> line 3694: PAC_CC_SUBDIR_SHLIBS: command not found >>>>>>> configure: creating ./config.status >>>>>>> config.status: error: cannot find input file: `Makefile.in' >>>>>>> configure: error: src/util/logging/rlog configure failed >>>>>>> >>>>>>> I attached the c.txt file used in the configuration. >>>>>>> >>>>>>> Regards >>>>>>> >>>>>>> Fernando >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>>>> ALCF docs: http://www.alcf.anl.gov/user-guides >>>>>> _______________________________________________ >>>>>> 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 >>>> _______________________________________________ >>>> discuss mailing list discuss(a)mpich.org >>>> To manage subscription options or unsubscribe: >>>> https://lists.mpich.org/mailman/listinfo/discuss >>> >> <config.log> >> _______________________________________________ >> 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