January 2016 - discuss - mailman3.cels.anl.gov

Re: [mpich-discuss] Error buildingmpich-master-v3.2-88-gbbb40df74d46
by Siegmar Gross 20 Jan '16

20 Jan '16

Hi Rob, thank you very much for the second patch. Unfortunately it didn't solve the problem completely. I looked around and found two more files which needed your patches. After applying your patches I was able to build the system with both compilers. I patched the following files. loki bt 159 pwd /export2/src/mpich-3.2.1/mpich-master-v3.2-88-gbbb40df74d46/src/pm/hydra/mpl/src/bt loki bt 160 diff mpl_bt.c* 47,51c47 < /* we need not only the symbols but the header file too (for the cursor and < * context), so tighten up when we take the libunwind path. Thanks < * Siegmar.Gross(a)informatik.hs-fulda.de for the bug report about systems with < * libunwind libraries but no libunwind development headers */ < #elif defined MPL_HAVE_LIBUNWIND && defined(MPL_HAVE_LIBUNWIND_H) --- > #elif defined MPL_HAVE_LIBUNWIND 125c121 < #elif defined MPL_HAVE_LIBUNWIND && defined(MPL_HAVE_LIBUNWIND_H) --- > #elif defined MPL_HAVE_LIBUNWIND loki bt 161 loki bt 161 loki bt 161 loki bt 161 cd /export2/src/mpich-3.2.1/mpich-master-v3.2-88-gbbb40df74d46/src/mpi/romio/mpl/src/bt loki bt 162 diff mpl_bt.c* 47,51c47 < /* we need not only the symbols but the header file too (for the cursor and < * context), so tighten up when we take the libunwind path. Thanks < * Siegmar.Gross(a)informatik.hs-fulda.de for the bug report about systems with < * libunwind libraries but no libunwind development headers */ < #elif defined MPL_HAVE_LIBUNWIND && defined(MPL_HAVE_LIBUNWIND_H) --- > #elif defined MPL_HAVE_LIBUNWIND 125c121 < #elif defined MPL_HAVE_LIBUNWIND && defined(MPL_HAVE_LIBUNWIND_H) --- > #elif defined MPL_HAVE_LIBUNWIND loki bt 163 loki bt 163 loki bt 163 loki bt 163 cd /export2/src/mpich-3.2.1/mpich-master-v3.2-88-gbbb40df74d46/src/mpl/src/bt/ loki bt 164 diff mpl_bt.c mpl_bt.c.orig 47,51c47 < /* we need not only the symbols but the header file too (for the cursor and < * context), so tighten up when we take the libunwind path. Thanks < * Siegmar.Gross(a)informatik.hs-fulda.de for the bug report about systems with < * libunwind libraries but no libunwind development headers */ < #elif defined MPL_HAVE_LIBUNWIND && defined(MPL_HAVE_LIBUNWIND_H) --- > #elif defined MPL_HAVE_LIBUNWIND 125c121 < #elif defined MPL_HAVE_LIBUNWIND && defined(MPL_HAVE_LIBUNWIND_H) --- > #elif defined MPL_HAVE_LIBUNWIND loki bt 165 I also got a lot of errors for Sun C. I don't know if they break anything or are just a kind of "warning". loki mpich-master-v3.2-88-gbbb40df74d46-Linux.x86_64.64_cc 176 loki mpich-master-v3.2-88-gbbb40df74d46-Linux.x86_64.64_cc 176 grep error: log.make.Linux.x86_64.64_cc | sort | uniq "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/channels/nemesis/include/mpid_nem_datatypes.h", line 156: warning: syntax error: empty member declaration "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/channels/nemesis/include/mpid_nem_datatypes.h", line 161: warning: syntax error: empty member declaration "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/channels/nemesis/src/ch3_win_fns.c", line 17: warning: syntax error: empty declaration "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/include/mpid_rma_lockqueue.h", line 13: warning: syntax error: empty declaration "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/include/mpid_rma_lockqueue.h", line 14: warning: syntax error: empty declaration "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/include/mpid_rma_oplist.h", line 21: warning: syntax error: empty declaration "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/include/mpidi_recvq_statistics.h", line 13: warning: syntax error: empty declaration "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/src/ch3u_recvq.c", line 100: warning: syntax error: empty declaration "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/src/ch3u_recvq.c", line 103: warning: syntax error: empty declaration "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/src/ch3u_recvq.c", line 95: warning: syntax error: empty declaration "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/src/ch3u_recvq.c", line 96: warning: syntax error: empty declaration "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/src/ch3u_recvq.c", line 97: warning: syntax error: empty declaration "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/src/ch3u_recvq.c", line 98: warning: syntax error: empty declaration "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/src/ch3u_recvq.c", line 99: warning: syntax error: empty declaration "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/src/ch3u_rma_ops.c", line 9: warning: syntax error: empty declaration "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/src/ch3u_rma_pkthandler.c", line 10: warning: syntax error: empty declaration "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/src/ch3u_rma_pkthandler.c", line 11: warning: syntax error: empty declaration "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/src/ch3u_rma_pkthandler.c", line 12: warning: syntax error: empty declaration "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/src/ch3u_rma_pkthandler.c", line 13: warning: syntax error: empty declaration "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/src/ch3u_rma_pkthandler.c", line 14: warning: syntax error: empty declaration "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/src/ch3u_rma_pkthandler.c", line 15: warning: syntax error: empty declaration "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/src/ch3u_rma_pkthandler.c", line 16: warning: syntax error: empty declaration "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/src/ch3u_rma_pkthandler.c", line 17: warning: syntax error: empty declaration "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/src/ch3u_rma_pkthandler.c", line 18: warning: syntax error: empty declaration "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/src/ch3u_rma_pkthandler.c", line 19: warning: syntax error: empty declaration "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/src/ch3u_rma_pkthandler.c", line 20: warning: syntax error: empty declaration "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/src/ch3u_rma_pkthandler.c", line 21: warning: syntax error: empty declaration "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/src/ch3u_rma_pkthandler.c", line 22: warning: syntax error: empty declaration "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/src/ch3u_rma_pkthandler.c", line 23: warning: syntax error: empty declaration "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/src/ch3u_rma_pkthandler.c", line 24: warning: syntax error: empty declaration "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/src/ch3u_rma_pkthandler.c", line 25: warning: syntax error: empty declaration "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/src/ch3u_rma_sync.c", line 259: warning: syntax error: empty declaration "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/src/ch3u_rma_sync.c", line 260: warning: syntax error: empty declaration "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/src/ch3u_rma_sync.c", line 261: warning: syntax error: empty declaration "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/src/ch3u_rma_sync.c", line 263: warning: syntax error: empty declaration "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/src/ch3u_rma_sync.c", line 264: warning: syntax error: empty declaration "../mpich-master-v3.2-88-gbbb40df74d46/src/mpid/ch3/src/ch3u_win_fns.c", line 11: warning: syntax error: empty declaration loki mpich-master-v3.2-88-gbbb40df74d46-Linux.x86_64.64_cc 177 I'll try to test this version later and let you know if something doesn't work as expected. Best regards and thank you very much for your help again Siegmar On 01/19/16 18:45, Rob Latham wrote: > > > On 01/16/2016 02:35 AM, Siegmar Gross wrote: >> Hi Rob, >> >> I've attached the files for both compilers. >> >> Best regards and thank you very much for your help > > It looks like the compiler doesn't matter in your environment. > > I did find one more spot to update, and now with your mplconfig.h in place I get no warnings. > > From the messages you included, it still looks like MPICH is trying to compile the libunwind functions, even though > I've done everything I can to check for that. > > If the attached patch does nothing for you, then I will simply remove libunwind support until I can set up a suse > virtual machine and figure out what's going on. > > ==rob > >> >> Siegmar >> >> >> Am 15.01.2016 um 16:55 schrieb Rob Latham: >>> >>> >>> On 01/15/2016 06:56 AM, Siegmar Gross wrote: >>>> Hi Rob, >>>> >>>> I had to change "#if" to "#elif", but I still get errors. I've >>>> attached the >>>> log files. >>> >>> OK, you can see what I'm trying to do, yes? On my end, everything >>> I've done >>> to re-create your environment works for me. One more favor: send me your >>> src/mpl/include/mplconfig.h >>> >>> Thanks >>> ==rob >>> _______________________________________________ >>> 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] Test of MPICH 3.1.3 on BlueGene/Q
by Jeff Hammond 19 Jan '16

19 Jan '16

Because Blue Gene doesn't have fork() or any other OS mechanism for spawning processes after job start, it has never had a nontrivial implementation of MPI_Comm_spawn and thus has never passed the MPICH test suite. By nontrivial, I mean one that does something other than fail in a compliant way because world_size = universe_size (which may not have happened but which I proposed as a trivial way to achieve MPI-2.2 compliance). For Blue Gene/Q acceptance testing, every MPICH test (from some version of the test suite circa 2012, which I do not recall offhand) passed except those explicitly excluded. The exclusions were anything related to dynamic processes, connect-accept, etc. and language bindings (certainly Fortran; I don't know what we said about C++, but I don't think that is relevant here). Fortran was excluded because that has nothing to do with the guts of MPI, the network, etc. It is strictly a test of the Fortran compiler and the Fortran bindings. So if some MPICH Fortran test is failing, it is either a compiler issue or a problem with MPICH Fortran bindings. I hope this helps. Jeff On Tue, Jan 19, 2016 at 8:59 AM, Rob Latham <robl(a)mcs.anl.gov> wrote: > > > On 01/17/2016 08:16 PM, Dominic Chien wrote: > >> Hi, >> >> I have built MPICH 3.1.3 on Bluegene/Q, based on the following >> configuration >> ../configure --host=powerpc64-bgq-linux --with-device=pamid:BGQ >> --with-file-system=gpfs:BGQ >> --with-bgq-install-dir=/bgsys/drivers/V1R2M0/ppc64 --disable-wrapper-rpath >> --enable-fast=nochkmsg,notiming,O3 --with-assert-level=0 >> --disable-error-messages --disable-debuginfo --enable-thread-cs=per-object >> --with-atomic-primitives --enable-handle-allocation=tls >> --enable-refcount=lock-free --disable-predefined-refcount >> --with-cross-file=src/mpid/pamid/cross/bgq8 >> --prefix=/scratch/home/chiensh/apps/mpich/3.1.3-opt/ --disable-spawn >> >> The resultant mpich has passed most of the tests (679) and 9 are failed >> (see below), but I am not sure if these errors are critical. Can anyone >> comment on this? >> >> > I don't know if MPICH ever passed 100% of the mpich tests on Blue Gene > (maybe back in 1.5.1 days, but we had fewer tests then, too). > > These 9 errors all look like something an application might run into: > probing messages, truncated messages, RMA via the fortran interface, > examining the status object. > > If your application does any of those things I'd pay particular attention > to the results. It's entirely possible that your application won't touch > the parts of MPICH that are not fully up to spec on Blue Gene. > > So, I would say these errors are concerning, but not critical. Press on > and let us know how things go with your application! > > ==rob > > > > Many Thanks! >> >> Regards, >> Dominic Chien >> >> ========================================================= >> not ok 283 - ./init/timeout 2 >> --- >> Directory: ./init >> File: timeout >> Num-procs: 2 >> Date: "Wed Jan 13 13:55:50 2016" >> ... >> ## Test output (expected 'No Errors'): >> ## srun returned a zero status but the program returned a nonzero status >> ========================================================= >> ========================================================= >> not ok 324 - ./pt2pt/mprobe 2 >> --- >> Directory: ./pt2pt >> File: mprobe >> Num-procs: 2 >> Date: "Wed Jan 13 14:07:47 2016" >> ... >> ## Test output (expected 'No Errors'): >> ## 2016-01-13 14:07:47.846 (WARN ) [0xfff8d988bb0] >> 78050:ibm.runjob.client.Job: terminated by signal 11 >> ## 2016-01-13 14:07:47.846 (WARN ) [0xfff8d988bb0] >> 78050:ibm.runjob.client.Job: abnormal termination by signal 11 from rank 1 >> ========================================================= >> ========================================================= >> not ok 538 - ./f77/rma/wingetf 5 >> --- >> Directory: ./f77/rma >> File: wingetf >> Num-procs: 5 >> Date: "Wed Jan 13 16:28:10 2016" >> ... >> ## Test output (expected 'No Errors'): >> ## 0 buf( 1 , 11 ) = 751 expected 251 >> ## 0 buf( 2 , 11 ) = 752 expected 252 >> ## 0 buf( 3 , 11 ) = 753 expected 253 >> ## 0 buf( 4 , 11 ) = 754 expected 254 >> ## 0 buf( 5 , 11 ) = 755 expected 255 >> ## 0 buf( 6 , 11 ) = 756 expected 256 >> ## 0 buf( 7 , 11 ) = 757 expected 257 >> ## 0 buf( 8 , 11 ) = 758 expected 258 >> ## 0 buf( 9 , 11 ) = 759 expected 259 >> ## 0 buf( 10 , 11 ) = 760 expected 260 >> ## Found 25 errors >> ========================================================= >> ========================================================= >> not ok 640 - ./f90/rma/wingetf90 5 >> --- >> Directory: ./f90/rma >> File: wingetf90 >> Num-procs: 5 >> Date: "Wed Jan 13 18:10:17 2016" >> ... >> ## Test output (expected 'No Errors'): >> ## 4 buf( 1 ,0) = 0 expected 976 >> ## 4 buf( 2 ,0) = 24525328 expected 977 >> ## 4 buf( 3 ,0) = 31 expected 978 >> ## 4 buf( 4 ,0) = -1073759872 expected 979 >> ## 4 buf( 5 ,0) = 1107296292 expected 980 >> ## 4 buf( 6 ,0) = -1073758504 expected 981 >> ## 4 buf( 7 ,0) = 0 expected 982 >> ## 4 buf( 8 ,0) = 22184620 expected 983 >> ## 4 buf( 9 ,0) = 0 expected 984 >> ## 4 buf( 10 ,0) = 25808064 expected 985 >> ## Found 50 errors >> ========================================================= >> ========================================================= >> not ok 668 - ./errors/pt2pt/truncmsg1 2 >> --- >> Directory: ./errors/pt2pt >> File: truncmsg1 >> Num-procs: 2 >> Date: "Wed Jan 13 18:16:19 2016" >> ... >> ## Test output (expected 'No Errors'): >> ## MPI_Recv (short) returned MPI_SUCCESS instead of truncated message >> ## MPI_Recv (irecv-short) returned MPI_SUCCESS instead of truncated >> message >> ## MPI_Recv (medium) returned MPI_SUCCESS instead of truncated message >> ## Found 3 errors >> ========================================================= >> ========================================================= >> not ok 670 - ./errors/pt2pt/errinstatts 2 >> --- >> Directory: ./errors/pt2pt >> File: errinstatts >> Num-procs: 2 >> Date: "Wed Jan 13 18:16:45 2016" >> ... >> ## Test output (expected 'No Errors'): >> ## Did not get ERR_IN_STATUS in Testsome (outcount = 2, should equal 2); >> class returned was 0 >> ## Found 1 errors >> ========================================================= >> ========================================================= >> not ok 671 - ./errors/pt2pt/errinstatta 2 >> --- >> Directory: ./errors/pt2pt >> File: errinstatta >> Num-procs: 2 >> Date: "Wed Jan 13 18:16:58 2016" >> ... >> ## Test output (expected 'No Errors'): >> ## Did not get ERR_IN_STATUS in Testall >> ## Found 1 errors >> ========================================================= >> ========================================================= >> not ok 672 - ./errors/pt2pt/errinstatws 2 >> --- >> Directory: ./errors/pt2pt >> File: errinstatws >> Num-procs: 2 >> Date: "Wed Jan 13 18:17:11 2016" >> ... >> ## Test output (expected 'No Errors'): >> ## Did not get ERR_IN_STATUS in Waitsome. Got 0. >> ## Found 1 errors >> ========================================================= >> ========================================================= >> not ok 673 - ./errors/pt2pt/errinstatwa 2 >> --- >> Directory: ./errors/pt2pt >> File: errinstatwa >> Num-procs: 2 >> Date: "Wed Jan 13 18:17:23 2016" >> ... >> ## Test output (expected 'No Errors'): >> ## Did not get ERR_IN_STATUS in Waitall >> ## Found 1 errors >> ========================================================= >> >> >> _______________________________________________ >> 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 jeff.science(a)gmail.com http://jeffhammond.github.io/ _______________________________________________ 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 buildingmpich-master-v3.2-88-gbbb40df74d46
by Rob Latham 19 Jan '16

19 Jan '16

On 01/16/2016 02:35 AM, Siegmar Gross wrote: > Hi Rob, > > I've attached the files for both compilers. > > Best regards and thank you very much for your help It looks like the compiler doesn't matter in your environment. I did find one more spot to update, and now with your mplconfig.h in place I get no warnings. From the messages you included, it still looks like MPICH is trying to compile the libunwind functions, even though I've done everything I can to check for that. If the attached patch does nothing for you, then I will simply remove libunwind support until I can set up a suse virtual machine and figure out what's going on. ==rob > > Siegmar > > > Am 15.01.2016 um 16:55 schrieb Rob Latham: >> >> >> On 01/15/2016 06:56 AM, Siegmar Gross wrote: >>> Hi Rob, >>> >>> I had to change "#if" to "#elif", but I still get errors. I've >>> attached the >>> log files. >> >> OK, you can see what I'm trying to do, yes? On my end, everything >> I've done >> to re-create your environment works for me. One more favor: send me your >> src/mpl/include/mplconfig.h >> >> Thanks >> ==rob >> _______________________________________________ >> 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] Test of MPICH 3.1.3 on BlueGene/Q
by Rob Latham 19 Jan '16

19 Jan '16

On 01/17/2016 08:16 PM, Dominic Chien wrote: > Hi, > > I have built MPICH 3.1.3 on Bluegene/Q, based on the following configuration > ../configure --host=powerpc64-bgq-linux --with-device=pamid:BGQ --with-file-system=gpfs:BGQ --with-bgq-install-dir=/bgsys/drivers/V1R2M0/ppc64 --disable-wrapper-rpath --enable-fast=nochkmsg,notiming,O3 --with-assert-level=0 --disable-error-messages --disable-debuginfo --enable-thread-cs=per-object --with-atomic-primitives --enable-handle-allocation=tls --enable-refcount=lock-free --disable-predefined-refcount --with-cross-file=src/mpid/pamid/cross/bgq8 --prefix=/scratch/home/chiensh/apps/mpich/3.1.3-opt/ --disable-spawn > > The resultant mpich has passed most of the tests (679) and 9 are failed (see below), but I am not sure if these errors are critical. Can anyone comment on this? > I don't know if MPICH ever passed 100% of the mpich tests on Blue Gene (maybe back in 1.5.1 days, but we had fewer tests then, too). These 9 errors all look like something an application might run into: probing messages, truncated messages, RMA via the fortran interface, examining the status object. If your application does any of those things I'd pay particular attention to the results. It's entirely possible that your application won't touch the parts of MPICH that are not fully up to spec on Blue Gene. So, I would say these errors are concerning, but not critical. Press on and let us know how things go with your application! ==rob > Many Thanks! > > Regards, > Dominic Chien > > ========================================================= > not ok 283 - ./init/timeout 2 > --- > Directory: ./init > File: timeout > Num-procs: 2 > Date: "Wed Jan 13 13:55:50 2016" > ... > ## Test output (expected 'No Errors'): > ## srun returned a zero status but the program returned a nonzero status > ========================================================= > ========================================================= > not ok 324 - ./pt2pt/mprobe 2 > --- > Directory: ./pt2pt > File: mprobe > Num-procs: 2 > Date: "Wed Jan 13 14:07:47 2016" > ... > ## Test output (expected 'No Errors'): > ## 2016-01-13 14:07:47.846 (WARN ) [0xfff8d988bb0] 78050:ibm.runjob.client.Job: terminated by signal 11 > ## 2016-01-13 14:07:47.846 (WARN ) [0xfff8d988bb0] 78050:ibm.runjob.client.Job: abnormal termination by signal 11 from rank 1 > ========================================================= > ========================================================= > not ok 538 - ./f77/rma/wingetf 5 > --- > Directory: ./f77/rma > File: wingetf > Num-procs: 5 > Date: "Wed Jan 13 16:28:10 2016" > ... > ## Test output (expected 'No Errors'): > ## 0 buf( 1 , 11 ) = 751 expected 251 > ## 0 buf( 2 , 11 ) = 752 expected 252 > ## 0 buf( 3 , 11 ) = 753 expected 253 > ## 0 buf( 4 , 11 ) = 754 expected 254 > ## 0 buf( 5 , 11 ) = 755 expected 255 > ## 0 buf( 6 , 11 ) = 756 expected 256 > ## 0 buf( 7 , 11 ) = 757 expected 257 > ## 0 buf( 8 , 11 ) = 758 expected 258 > ## 0 buf( 9 , 11 ) = 759 expected 259 > ## 0 buf( 10 , 11 ) = 760 expected 260 > ## Found 25 errors > ========================================================= > ========================================================= > not ok 640 - ./f90/rma/wingetf90 5 > --- > Directory: ./f90/rma > File: wingetf90 > Num-procs: 5 > Date: "Wed Jan 13 18:10:17 2016" > ... > ## Test output (expected 'No Errors'): > ## 4 buf( 1 ,0) = 0 expected 976 > ## 4 buf( 2 ,0) = 24525328 expected 977 > ## 4 buf( 3 ,0) = 31 expected 978 > ## 4 buf( 4 ,0) = -1073759872 expected 979 > ## 4 buf( 5 ,0) = 1107296292 expected 980 > ## 4 buf( 6 ,0) = -1073758504 expected 981 > ## 4 buf( 7 ,0) = 0 expected 982 > ## 4 buf( 8 ,0) = 22184620 expected 983 > ## 4 buf( 9 ,0) = 0 expected 984 > ## 4 buf( 10 ,0) = 25808064 expected 985 > ## Found 50 errors > ========================================================= > ========================================================= > not ok 668 - ./errors/pt2pt/truncmsg1 2 > --- > Directory: ./errors/pt2pt > File: truncmsg1 > Num-procs: 2 > Date: "Wed Jan 13 18:16:19 2016" > ... > ## Test output (expected 'No Errors'): > ## MPI_Recv (short) returned MPI_SUCCESS instead of truncated message > ## MPI_Recv (irecv-short) returned MPI_SUCCESS instead of truncated message > ## MPI_Recv (medium) returned MPI_SUCCESS instead of truncated message > ## Found 3 errors > ========================================================= > ========================================================= > not ok 670 - ./errors/pt2pt/errinstatts 2 > --- > Directory: ./errors/pt2pt > File: errinstatts > Num-procs: 2 > Date: "Wed Jan 13 18:16:45 2016" > ... > ## Test output (expected 'No Errors'): > ## Did not get ERR_IN_STATUS in Testsome (outcount = 2, should equal 2); class returned was 0 > ## Found 1 errors > ========================================================= > ========================================================= > not ok 671 - ./errors/pt2pt/errinstatta 2 > --- > Directory: ./errors/pt2pt > File: errinstatta > Num-procs: 2 > Date: "Wed Jan 13 18:16:58 2016" > ... > ## Test output (expected 'No Errors'): > ## Did not get ERR_IN_STATUS in Testall > ## Found 1 errors > ========================================================= > ========================================================= > not ok 672 - ./errors/pt2pt/errinstatws 2 > --- > Directory: ./errors/pt2pt > File: errinstatws > Num-procs: 2 > Date: "Wed Jan 13 18:17:11 2016" > ... > ## Test output (expected 'No Errors'): > ## Did not get ERR_IN_STATUS in Waitsome. Got 0. > ## Found 1 errors > ========================================================= > ========================================================= > not ok 673 - ./errors/pt2pt/errinstatwa 2 > --- > Directory: ./errors/pt2pt > File: errinstatwa > Num-procs: 2 > Date: "Wed Jan 13 18:17:23 2016" > ... > ## Test output (expected 'No Errors'): > ## Did not get ERR_IN_STATUS in Waitall > ## Found 1 errors > ========================================================= > > > _______________________________________________ > 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

Test of MPICH 3.1.3 on BlueGene/Q
by Dominic Chien 17 Jan '16

17 Jan '16

Hi, I have built MPICH 3.1.3 on Bluegene/Q, based on the following configuration ../configure --host=powerpc64-bgq-linux --with-device=pamid:BGQ --with-file-system=gpfs:BGQ --with-bgq-install-dir=/bgsys/drivers/V1R2M0/ppc64 --disable-wrapper-rpath --enable-fast=nochkmsg,notiming,O3 --with-assert-level=0 --disable-error-messages --disable-debuginfo --enable-thread-cs=per-object --with-atomic-primitives --enable-handle-allocation=tls --enable-refcount=lock-free --disable-predefined-refcount --with-cross-file=src/mpid/pamid/cross/bgq8 --prefix=/scratch/home/chiensh/apps/mpich/3.1.3-opt/ --disable-spawn The resultant mpich has passed most of the tests (679) and 9 are failed (see below), but I am not sure if these errors are critical. Can anyone comment on this? Many Thanks! Regards, Dominic Chien ========================================================= not ok 283 - ./init/timeout 2 --- Directory: ./init File: timeout Num-procs: 2 Date: "Wed Jan 13 13:55:50 2016" ... ## Test output (expected 'No Errors'): ## srun returned a zero status but the program returned a nonzero status ========================================================= ========================================================= not ok 324 - ./pt2pt/mprobe 2 --- Directory: ./pt2pt File: mprobe Num-procs: 2 Date: "Wed Jan 13 14:07:47 2016" ... ## Test output (expected 'No Errors'): ## 2016-01-13 14:07:47.846 (WARN ) [0xfff8d988bb0] 78050:ibm.runjob.client.Job: terminated by signal 11 ## 2016-01-13 14:07:47.846 (WARN ) [0xfff8d988bb0] 78050:ibm.runjob.client.Job: abnormal termination by signal 11 from rank 1 ========================================================= ========================================================= not ok 538 - ./f77/rma/wingetf 5 --- Directory: ./f77/rma File: wingetf Num-procs: 5 Date: "Wed Jan 13 16:28:10 2016" ... ## Test output (expected 'No Errors'): ## 0 buf( 1 , 11 ) = 751 expected 251 ## 0 buf( 2 , 11 ) = 752 expected 252 ## 0 buf( 3 , 11 ) = 753 expected 253 ## 0 buf( 4 , 11 ) = 754 expected 254 ## 0 buf( 5 , 11 ) = 755 expected 255 ## 0 buf( 6 , 11 ) = 756 expected 256 ## 0 buf( 7 , 11 ) = 757 expected 257 ## 0 buf( 8 , 11 ) = 758 expected 258 ## 0 buf( 9 , 11 ) = 759 expected 259 ## 0 buf( 10 , 11 ) = 760 expected 260 ## Found 25 errors ========================================================= ========================================================= not ok 640 - ./f90/rma/wingetf90 5 --- Directory: ./f90/rma File: wingetf90 Num-procs: 5 Date: "Wed Jan 13 18:10:17 2016" ... ## Test output (expected 'No Errors'): ## 4 buf( 1 ,0) = 0 expected 976 ## 4 buf( 2 ,0) = 24525328 expected 977 ## 4 buf( 3 ,0) = 31 expected 978 ## 4 buf( 4 ,0) = -1073759872 expected 979 ## 4 buf( 5 ,0) = 1107296292 expected 980 ## 4 buf( 6 ,0) = -1073758504 expected 981 ## 4 buf( 7 ,0) = 0 expected 982 ## 4 buf( 8 ,0) = 22184620 expected 983 ## 4 buf( 9 ,0) = 0 expected 984 ## 4 buf( 10 ,0) = 25808064 expected 985 ## Found 50 errors ========================================================= ========================================================= not ok 668 - ./errors/pt2pt/truncmsg1 2 --- Directory: ./errors/pt2pt File: truncmsg1 Num-procs: 2 Date: "Wed Jan 13 18:16:19 2016" ... ## Test output (expected 'No Errors'): ## MPI_Recv (short) returned MPI_SUCCESS instead of truncated message ## MPI_Recv (irecv-short) returned MPI_SUCCESS instead of truncated message ## MPI_Recv (medium) returned MPI_SUCCESS instead of truncated message ## Found 3 errors ========================================================= ========================================================= not ok 670 - ./errors/pt2pt/errinstatts 2 --- Directory: ./errors/pt2pt File: errinstatts Num-procs: 2 Date: "Wed Jan 13 18:16:45 2016" ... ## Test output (expected 'No Errors'): ## Did not get ERR_IN_STATUS in Testsome (outcount = 2, should equal 2); class returned was 0 ## Found 1 errors ========================================================= ========================================================= not ok 671 - ./errors/pt2pt/errinstatta 2 --- Directory: ./errors/pt2pt File: errinstatta Num-procs: 2 Date: "Wed Jan 13 18:16:58 2016" ... ## Test output (expected 'No Errors'): ## Did not get ERR_IN_STATUS in Testall ## Found 1 errors ========================================================= ========================================================= not ok 672 - ./errors/pt2pt/errinstatws 2 --- Directory: ./errors/pt2pt File: errinstatws Num-procs: 2 Date: "Wed Jan 13 18:17:11 2016" ... ## Test output (expected 'No Errors'): ## Did not get ERR_IN_STATUS in Waitsome. Got 0. ## Found 1 errors ========================================================= ========================================================= not ok 673 - ./errors/pt2pt/errinstatwa 2 --- Directory: ./errors/pt2pt File: errinstatwa Num-procs: 2 Date: "Wed Jan 13 18:17:23 2016" ... ## Test output (expected 'No Errors'): ## Did not get ERR_IN_STATUS in Waitall ## Found 1 errors ========================================================= _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Test of MPICH 3.1.3 on BlueGene/Q
by Dominic Chien 17 Jan '16

17 Jan '16

Hi, I have built MPICH 3.1.3 on Bluegene/Q, based on the following configuration ../configure --host=powerpc64-bgq-linux --with-device=pamid:BGQ --with-file-system=gpfs:BGQ --with-bgq-install-dir=/bgsys/drivers/V1R2M0/ppc64 --disable-wrapper-rpath --enable-fast=nochkmsg,notiming,O3 --with-assert-level=0 --disable-error-messages --disable-debuginfo --enable-thread-cs=per-object --with-atomic-primitives --enable-handle-allocation=tls --enable-refcount=lock-free --disable-predefined-refcount --with-cross-file=src/mpid/pamid/cross/bgq8 --prefix=/scratch/home/chiensh/apps/mpich/3.1.3-opt/ --disable-spawn The resultant mpich has passed most of the tests (679) and 9 are failed (see below), but I am not sure if these errors are critical. Can anyone comment on this? Many Thanks! Regards, Dominic Chien ========================================================= not ok 283 - ./init/timeout 2 --- Directory: ./init File: timeout Num-procs: 2 Date: "Wed Jan 13 13:55:50 2016" ... ## Test output (expected 'No Errors'): ## srun returned a zero status but the program returned a nonzero status ========================================================= ========================================================= not ok 324 - ./pt2pt/mprobe 2 --- Directory: ./pt2pt File: mprobe Num-procs: 2 Date: "Wed Jan 13 14:07:47 2016" ... ## Test output (expected 'No Errors'): ## 2016-01-13 14:07:47.846 (WARN ) [0xfff8d988bb0] 78050:ibm.runjob.client.Job: terminated by signal 11 ## 2016-01-13 14:07:47.846 (WARN ) [0xfff8d988bb0] 78050:ibm.runjob.client.Job: abnormal termination by signal 11 from rank 1 ========================================================= ========================================================= not ok 538 - ./f77/rma/wingetf 5 --- Directory: ./f77/rma File: wingetf Num-procs: 5 Date: "Wed Jan 13 16:28:10 2016" ... ## Test output (expected 'No Errors'): ## 0 buf( 1 , 11 ) = 751 expected 251 ## 0 buf( 2 , 11 ) = 752 expected 252 ## 0 buf( 3 , 11 ) = 753 expected 253 ## 0 buf( 4 , 11 ) = 754 expected 254 ## 0 buf( 5 , 11 ) = 755 expected 255 ## 0 buf( 6 , 11 ) = 756 expected 256 ## 0 buf( 7 , 11 ) = 757 expected 257 ## 0 buf( 8 , 11 ) = 758 expected 258 ## 0 buf( 9 , 11 ) = 759 expected 259 ## 0 buf( 10 , 11 ) = 760 expected 260 ## Found 25 errors ========================================================= ========================================================= not ok 640 - ./f90/rma/wingetf90 5 --- Directory: ./f90/rma File: wingetf90 Num-procs: 5 Date: "Wed Jan 13 18:10:17 2016" ... ## Test output (expected 'No Errors'): ## 4 buf( 1 ,0) = 0 expected 976 ## 4 buf( 2 ,0) = 24525328 expected 977 ## 4 buf( 3 ,0) = 31 expected 978 ## 4 buf( 4 ,0) = -1073759872 expected 979 ## 4 buf( 5 ,0) = 1107296292 expected 980 ## 4 buf( 6 ,0) = -1073758504 expected 981 ## 4 buf( 7 ,0) = 0 expected 982 ## 4 buf( 8 ,0) = 22184620 expected 983 ## 4 buf( 9 ,0) = 0 expected 984 ## 4 buf( 10 ,0) = 25808064 expected 985 ## Found 50 errors ========================================================= ========================================================= not ok 668 - ./errors/pt2pt/truncmsg1 2 --- Directory: ./errors/pt2pt File: truncmsg1 Num-procs: 2 Date: "Wed Jan 13 18:16:19 2016" ... ## Test output (expected 'No Errors'): ## MPI_Recv (short) returned MPI_SUCCESS instead of truncated message ## MPI_Recv (irecv-short) returned MPI_SUCCESS instead of truncated message ## MPI_Recv (medium) returned MPI_SUCCESS instead of truncated message ## Found 3 errors ========================================================= ========================================================= not ok 670 - ./errors/pt2pt/errinstatts 2 --- Directory: ./errors/pt2pt File: errinstatts Num-procs: 2 Date: "Wed Jan 13 18:16:45 2016" ... ## Test output (expected 'No Errors'): ## Did not get ERR_IN_STATUS in Testsome (outcount = 2, should equal 2); class returned was 0 ## Found 1 errors ========================================================= ========================================================= not ok 671 - ./errors/pt2pt/errinstatta 2 --- Directory: ./errors/pt2pt File: errinstatta Num-procs: 2 Date: "Wed Jan 13 18:16:58 2016" ... ## Test output (expected 'No Errors'): ## Did not get ERR_IN_STATUS in Testall ## Found 1 errors ========================================================= ========================================================= not ok 672 - ./errors/pt2pt/errinstatws 2 --- Directory: ./errors/pt2pt File: errinstatws Num-procs: 2 Date: "Wed Jan 13 18:17:11 2016" ... ## Test output (expected 'No Errors'): ## Did not get ERR_IN_STATUS in Waitsome. Got 0. ## Found 1 errors ========================================================= ========================================================= not ok 673 - ./errors/pt2pt/errinstatwa 2 --- Directory: ./errors/pt2pt File: errinstatwa Num-procs: 2 Date: "Wed Jan 13 18:17:23 2016" ... ## Test output (expected 'No Errors'): ## Did not get ERR_IN_STATUS in Waitall ## Found 1 errors ========================================================= _______________________________________________ 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] A issue while running an application with mpich2
by Balaji, Pavan 17 Jan '16

17 Jan '16

That's a generic error message saying, well, something is wrong with your application. The only additional piece of information is that the exit code is 134, which is actually a signal (128 + 6, where "6" is the signal code == SIGABRT). Meaning, your application aborted with the SIGABRT signal. Here's some information from our stackoverflow friends: http://stackoverflow.com/questions/3413166/when-does-a-process-get-sigabrt-… This has nothing to do with MPICH or MPI. You need to debug your application. -- Pavan > On Jan 16, 2016, at 4:22 AM, 20122009刘琛 <13630583107(a)163.com> wrote: > > I have this issue while running an benchmark with mpich2 ,but it always ended up like the picture<QQ20160116-0.png><QQ20160116-1.png> > what is wrong with my application?I am new to MPICH2. > This is the command I used : > mpirun -f machine_file -n 4 ./filename and other benchmark-specified params. > machine_file contains an IP ,which is my computer's IP. > Thanks for your help! > > > 新的一年，让我陪你奋斗，让我陪你辛苦！-2016携手前行>> > > > > 新的一年，让我陪你奋斗，让我陪你辛苦！-2016携手前行>> > > <QQ20160116-0.png><QQ20160116-1.png>_______________________________________________ > 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 buildingmpich-master-v3.2-88-gbbb40df74d46
by Siegmar Gross 16 Jan '16

16 Jan '16

Hi Rob, today I tried to build version 77592165aa3, but I got the same errors for a different file so that it seems that the problem has nothing to do with the reorganization. Can I help with anything else? loki x 133 cat mpich/.git/HEAD ref: refs/heads/3.2.1-77592165aa3 loki x 105 cat mpich-Linux.x86_64.64_gcc/log.make.Linux.x86_64.64_gcc if test ! -h ./src/include/mpio.h ; then \ rm -f ./src/include/mpio.h ; \ ( cd ./src/include && \ ln -s ../mpi/romio/include/mpio.h ) ; \ fi make all-recursive make[1]: Entering directory '/export2/src/mpich-3.2.1/x/mpich-Linux.x86_64.64_gcc' Making all in /export2/src/mpich-3.2.1/x/mpich-Linux.x86_64.64_gcc/src/mpl make[2]: Entering directory '/export2/src/mpich-3.2.1/x/mpich-Linux.x86_64.64_gcc/src/mpl' CC src/mplstr.lo CC src/mpltrmem.lo CC src/mplenv.lo CC src/mplmsg.lo CC src/mplsock.lo CC src/mplutil.lo ../../../mpich/src/mpl/src/mplutil.c: In function ‘backtrace_libunwind’: ../../../mpich/src/mpl/src/mplutil.c:50:5: error: unknown type name ‘unw_cursor_t’ unw_cursor_t cursor; ^ ../../../mpich/src/mpl/src/mplutil.c:51:5: error: unknown type name ‘unw_context_t’ unw_context_t uc; ^ ... Best regards Siegmar Am 15.01.2016 um 13:45 schrieb Siegmar Gross: > Hi Halim, hi Rob, > > I've checked out version 77592165aa3, but at the moment I cannot > use it, because we have only libtool-2.4.2 and you need at least > libtool-2.4.4 so that autogen.sh failed. Our admin tries to > install the latest versions of all necessary tools. I don't know > if he succeeds today, because his working hours are over in 45 > minutes. I'll try as soon as possible. > > > Best regards > > Siegmar > > > On 01/14/16 17:33, Halim Amer wrote: >> you can check out that version from our git repo: >> git clone http://git.mpich.org/mpich.git >> cd mpich >> git checkout 77592165aa3 >> >> --Halim >> www.mcs.anl.gov/~aamer >> >> On 1/14/16 9:52 AM, Siegmar Gross wrote: >>> Hi, >>> >>> where can I find "version 77592165aa3"? I have only the following >>> archives after the release of mpich-3.2.tar.gz. >>> >>> loki mpich-3.2.1 113 ls -C1 *.gz >>> mpich-master-v3.2-42-g67631a5c0e9e.tar.gz >>> mpich-master-v3.2-87-g7150bbc02ec8.tar.gz >>> mpich-master-v3.2-88-gbbb40df74d46.tar.gz >>> >>> I've attached both config.log files from my gcc and cc version. >>> >>> I've searched for "libunwind tools" for our Linux version. It seems that >>> they are available for "Suse Linux Enterprise Server", but I didn't find >>> them for "Suse Linux Enterprise Desktop", which we use for most of our >>> machines. Shall I ask our Admin to install them? >>> >>> >>> Best regards >>> >>> Siegmar >>> >>> >>> On 01/14/16 16:25, Rob Latham wrote: >>>> >>>> >>>> On 01/14/2016 07:21 AM, Siegmar Gross wrote: >>>>> Hi, >>>>> >>>>> today I tried to build mpich-master-v3.2-88-gbbb40df74d46 on my machine >>>>> (SUSE Linux Enterprise Server 12.0 x86_64) with gcc-5.2.0 and Sun C >>>>> 5.13. >>>>> I used the following command to build the system for gcc. >>>> >>>> This looks like the "portable backtrace" functionality I added >>>> recently. Maybe I need to work on the "portable" part >>>> of that. >>>> >>>> MPICH thinks your environment has the libunwind tools, and so it is >>>> trying to use libunwind to display the backtrace. >>>> >>>> Unfortunately there's one more complication: a reorganization of the >>>> MPL sources (commit 12c912ec6372). >>>> >>>> If you can provide me with two pieces of information that would be great: >>>> >>>> - what if you check out MPICH from a few weeks back? I want to rule >>>> out the source reorg, and if you check out version >>>> 77592165aa3, that will have just my changes and none of the reorg >>>> changes. >>>> >>>> - Can you send me your src/mpl/config.log ? (not the config.log from >>>> top-level mpich, but the config.log subconfigure >>>> from src/mpl) I would like to see what backtrace libraries configure >>>> found in your environment. Then I can reproduce >>>> it on my end. >>>> >>>> ==rob >>>> >>>>> >>>>> mkdir >>>>> mpich-master-v3.2-88-gbbb40df74d46-${SYSTEM_ENV}.${MACHINE_ENV}.64_gcc >>>>> cd >>>>> mpich-master-v3.2-88-gbbb40df74d46-${SYSTEM_ENV}.${MACHINE_ENV}.64_gcc >>>>> >>>>> ../mpich-master-v3.2-88-gbbb40df74d46/configure \ >>>>> --prefix=/usr/local/mpich-3.2.1_64_gcc \ >>>>> --libdir=/usr/local/mpich-3.2.1_64_gcc/lib64 \ >>>>> --includedir=/usr/local/mpich-3.2.1_64_gcc/include64 \ >>>>> CC="gcc" CXX="g++" F77="gfortran" FC="gfortran" \ >>>>> CFLAGS="-m64 -z noexecstack" CXXFLAGS="-m64" FFLAGS="-m64" >>>>> FCFLAGS="-m64" \ >>>>> LDFLAGS="-m64" \ >>>>> --enable-fortran=yes --enable-cxx --enable-romio \ >>>>> --enable-debuginfo --enable-smpcoll \ >>>>> --enable-threads=multiple --with-thread-package=posix \ >>>>> --enable-shared \ >>>>> |& tee log.configure.$SYSTEM_ENV.$MACHINE_ENV.64_gcc >>>>> >>>>> make |& tee log.make.$SYSTEM_ENV.$MACHINE_ENV.64_gcc >>>>> >>>>> >>>>> "make" broke with the following error for "cc". >>>>> >>>>> loki mpich-master-v3.2-88-gbbb40df74d46-Linux.x86_64.64_cc 111 cat >>>>> log.make.Linux.x86_64.64_cc >>>>> if test ! -h ./src/include/mpio.h ; then \ >>>>> rm -f ./src/include/mpio.h ; \ >>>>> ( cd ./src/include && \ >>>>> ln -s ../mpi/romio/include/mpio.h ) ; \ >>>>> fi >>>>> make all-recursive >>>>> make[1]: Entering directory >>>>> '/export2/src/mpich-3.2.1/mpich-master-v3.2-88-gbbb40df74d46-Linux.x86_64.64_cc' >>>>> >>>>> >>>>> >>>>> Making all in >>>>> /export2/src/mpich-3.2.1/mpich-master-v3.2-88-gbbb40df74d46-Linux.x86_64.64_cc/src/mpl >>>>> >>>>> >>>>> >>>>> make[2]: Entering directory >>>>> '/export2/src/mpich-3.2.1/mpich-master-v3.2-88-gbbb40df74d46-Linux.x86_64.64_cc/src/mpl' >>>>> >>>>> >>>>> >>>>> CC src/bt/mpl_bt.lo >>>>> "../../../mpich-master-v3.2-88-gbbb40df74d46/src/mpl/src/bt/mpl_bt.c", >>>>> line 50: undefined symbol: unw_cursor_t >>>>> "../../../mpich-master-v3.2-88-gbbb40df74d46/src/mpl/src/bt/mpl_bt.c", >>>>> line 50: syntax error before or at: cursor >>>>> "../../../mpich-master-v3.2-88-gbbb40df74d46/src/mpl/src/bt/mpl_bt.c", >>>>> line 51: undefined symbol: unw_context_t >>>>> "../../../mpich-master-v3.2-88-gbbb40df74d46/src/mpl/src/bt/mpl_bt.c", >>>>> line 52: undefined symbol: unw_word_t >>>>> "../../../mpich-master-v3.2-88-gbbb40df74d46/src/mpl/src/bt/mpl_bt.c", >>>>> line 57: warning: implicit function declaration: unw_getcontext >>>>> "../../../mpich-master-v3.2-88-gbbb40df74d46/src/mpl/src/bt/mpl_bt.c", >>>>> line 57: undefined symbol: uc >>>>> "../../../mpich-master-v3.2-88-gbbb40df74d46/src/mpl/src/bt/mpl_bt.c", >>>>> line 58: warning: implicit function declaration: unw_init_local >>>>> "../../../mpich-master-v3.2-88-gbbb40df74d46/src/mpl/src/bt/mpl_bt.c", >>>>> line 58: undefined symbol: cursor >>>>> "../../../mpich-master-v3.2-88-gbbb40df74d46/src/mpl/src/bt/mpl_bt.c", >>>>> line 59: warning: implicit function declaration: unw_step >>>>> "../../../mpich-master-v3.2-88-gbbb40df74d46/src/mpl/src/bt/mpl_bt.c", >>>>> line 60: warning: implicit function declaration: unw_get_reg >>>>> "../../../mpich-master-v3.2-88-gbbb40df74d46/src/mpl/src/bt/mpl_bt.c", >>>>> line 60: undefined symbol: UNW_REG_IP >>>>> "../../../mpich-master-v3.2-88-gbbb40df74d46/src/mpl/src/bt/mpl_bt.c", >>>>> line 60: undefined symbol: ip >>>>> "../../../mpich-master-v3.2-88-gbbb40df74d46/src/mpl/src/bt/mpl_bt.c", >>>>> line 61: warning: implicit function declaration: unw_get_proc_name >>>>> "../../../mpich-master-v3.2-88-gbbb40df74d46/src/mpl/src/bt/mpl_bt.c", >>>>> line 62: undefined symbol: offset >>>>> cc: acomp failed for >>>>> ../../../mpich-master-v3.2-88-gbbb40df74d46/src/mpl/src/bt/mpl_bt.c >>>>> Makefile:923: recipe for target 'src/bt/mpl_bt.lo' failed >>>>> make[2]: *** [src/bt/mpl_bt.lo] Error 1 >>>>> make[2]: Leaving directory >>>>> '/export2/src/mpich-3.2.1/mpich-master-v3.2-88-gbbb40df74d46-Linux.x86_64.64_cc/src/mpl' >>>>> >>>>> >>>>> >>>>> Makefile:38434: recipe for target 'all-recursive' failed >>>>> make[1]: *** [all-recursive] Error 1 >>>>> make[1]: Leaving directory >>>>> '/export2/src/mpich-3.2.1/mpich-master-v3.2-88-gbbb40df74d46-Linux.x86_64.64_cc' >>>>> >>>>> >>>>> >>>>> Makefile:10304: recipe for target 'all' failed >>>>> make: *** [all] Error 2 >>>>> loki mpich-master-v3.2-88-gbbb40df74d46-Linux.x86_64.64_cc 112 >>>>> >>>>> >>>>> >>>>> "make" broke with the following error for "gcc". >>>>> >>>>> loki mpich-master-v3.2-88-gbbb40df74d46-Linux.x86_64.64_gcc 114 cat >>>>> log.make.Linux.x86_64.64_gcc >>>>> if test ! -h ./src/include/mpio.h ; then \ >>>>> rm -f ./src/include/mpio.h ; \ >>>>> ( cd ./src/include && \ >>>>> ln -s ../mpi/romio/include/mpio.h ) ; \ >>>>> fi >>>>> make all-recursive >>>>> make[1]: Entering directory >>>>> '/export2/src/mpich-3.2.1/mpich-master-v3.2-88-gbbb40df74d46-Linux.x86_64.64_gcc' >>>>> >>>>> >>>>> >>>>> Making all in >>>>> /export2/src/mpich-3.2.1/mpich-master-v3.2-88-gbbb40df74d46-Linux.x86_64.64_gcc/src/mpl >>>>> >>>>> >>>>> >>>>> make[2]: Entering directory >>>>> '/export2/src/mpich-3.2.1/mpich-master-v3.2-88-gbbb40df74d46-Linux.x86_64.64_gcc/src/mpl' >>>>> >>>>> >>>>> >>>>> CC src/bt/mpl_bt.lo >>>>> ../../../mpich-master-v3.2-88-gbbb40df74d46/src/mpl/src/bt/mpl_bt.c: In >>>>> function ‘backtrace_libunwind’: >>>>> ../../../mpich-master-v3.2-88-gbbb40df74d46/src/mpl/src/bt/mpl_bt.c:50:5: >>>>> error: >>>>> unknown type name ‘unw_cursor_t’ >>>>> unw_cursor_t cursor; >>>>> ^ >>>>> ../../../mpich-master-v3.2-88-gbbb40df74d46/src/mpl/src/bt/mpl_bt.c:51:5: >>>>> error: >>>>> unknown type name ‘unw_context_t’ >>>>> unw_context_t uc; >>>>> ^ >>>>> ../../../mpich-master-v3.2-88-gbbb40df74d46/src/mpl/src/bt/mpl_bt.c:52:5: >>>>> error: >>>>> unknown type name ‘unw_word_t’ >>>>> unw_word_t ip, offset; >>>>> ^ >>>>> ../../../mpich-master-v3.2-88-gbbb40df74d46/src/mpl/src/bt/mpl_bt.c:57:5: >>>>> warning: >>>>> implicit declaration of function ‘unw_getcontext’ >>>>> [-Wimplicit-function-declaration] >>>>> unw_getcontext(&uc); >>>>> ^ >>>>> ../../../mpich-master-v3.2-88-gbbb40df74d46/src/mpl/src/bt/mpl_bt.c:58:5: >>>>> warning: >>>>> implicit declaration of function ‘unw_init_local’ >>>>> [-Wimplicit-function-declaration] >>>>> unw_init_local(&cursor, &uc); >>>>> ^ >>>>> ../../../mpich-master-v3.2-88-gbbb40df74d46/src/mpl/src/bt/mpl_bt.c:59:12: >>>>> >>>>> warning: implicit declaration of function ‘unw_step’ >>>>> [-Wimplicit-function-declaration] >>>>> while (unw_step(&cursor) > 0) { >>>>> ^ >>>>> ../../../mpich-master-v3.2-88-gbbb40df74d46/src/mpl/src/bt/mpl_bt.c:60:9: >>>>> warning: >>>>> implicit declaration of function ‘unw_get_reg’ >>>>> [-Wimplicit-function-declaration] >>>>> unw_get_reg(&cursor, UNW_REG_IP, &ip); >>>>> ^ >>>>> ../../../mpich-master-v3.2-88-gbbb40df74d46/src/mpl/src/bt/mpl_bt.c:60:30: >>>>> >>>>> error: ‘UNW_REG_IP’ undeclared (first use in this function) >>>>> unw_get_reg(&cursor, UNW_REG_IP, &ip); >>>>> ^ >>>>> ../../../mpich-master-v3.2-88-gbbb40df74d46/src/mpl/src/bt/mpl_bt.c:60:30: >>>>> >>>>> note: each undeclared identifier is reported only once for each function >>>>> it appears in >>>>> ../../../mpich-master-v3.2-88-gbbb40df74d46/src/mpl/src/bt/mpl_bt.c:61:9: >>>>> warning: >>>>> implicit declaration of function ‘unw_get_proc_name’ >>>>> [-Wimplicit-function-declaration] >>>>> unw_get_proc_name(&cursor, buffer, >>>>> ^ >>>>> Makefile:920: recipe for target 'src/bt/mpl_bt.lo' failed >>>>> make[2]: *** [src/bt/mpl_bt.lo] Error 1 >>>>> make[2]: Leaving directory >>>>> '/export2/src/mpich-3.2.1/mpich-master-v3.2-88-gbbb40df74d46-Linux.x86_64.64_gcc/src/mpl' >>>>> >>>>> >>>>> >>>>> Makefile:38434: recipe for target 'all-recursive' failed >>>>> make[1]: *** [all-recursive] Error 1 >>>>> make[1]: Leaving directory >>>>> '/export2/src/mpich-3.2.1/mpich-master-v3.2-88-gbbb40df74d46-Linux.x86_64.64_gcc' >>>>> >>>>> >>>>> >>>>> Makefile:10304: recipe for target 'all' failed >>>>> make: *** [all] Error 2 >>>>> loki mpich-master-v3.2-88-gbbb40df74d46-Linux.x86_64.64_gcc 114 >>>>> >>>>> >>>>> >>>>> I would be grateful if somebody can fix the problem. Thank you very >>>>> much for any help in advance. >>>>> >>>>> >>>>> Kind regards >>>>> >>>>> Siegmar >>>>> _______________________________________________ >>>>> 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 _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

A issue while running an application with mpich2
by 20122009刘琛 16 Jan '16

16 Jan '16

I have this issue while running an benchmark with mpich2 ,but it always ended up like the picture what is wrong with my application?I am new to MPICH2. This is the command I used : mpirun -f machine_file -n 4 ./filename and other benchmark-specified params. machine_file contains an IP ,which is my computer's IP. Thanks for your help! 新的一年，让我陪你奋斗，让我陪你辛苦！-2016携手前行>> _______________________________________________ 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 buildingmpich-master-v3.2-88-gbbb40df74d46
by Siegmar Gross 16 Jan '16

16 Jan '16

Hi Rob, I've attached the files for both compilers. Best regards and thank you very much for your help Siegmar Am 15.01.2016 um 16:55 schrieb Rob Latham: > > > On 01/15/2016 06:56 AM, Siegmar Gross wrote: >> Hi Rob, >> >> I had to change "#if" to "#elif", but I still get errors. I've attached the >> log files. > > OK, you can see what I'm trying to do, yes? On my end, everything I've done > to re-create your environment works for me. One more favor: send me your > src/mpl/include/mplconfig.h > > Thanks > ==rob > _______________________________________________ > 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