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

Re: [mpich-discuss] MPI I/O spilt collective implementation: MPI_File_write_all_begin blocking or non-blocking?
by Rob Latham 08 Feb '16

08 Feb '16

On 02/08/2016 06:04 PM, pramod kumbhar wrote: > thanks! MPI_File_iwrite_all working as expected. I'm always glad to see folks looking at the MPI-IO routines. Let us know how your research progresses. ==rob > > -Pramod > > On Tue, Feb 9, 2016 at 12:52 AM, Balaji, Pavan <balaji(a)anl.gov > <mailto:[email protected]>> wrote: > > > I believe it is valid to do that in split collectives. If you want > truly nonblocking nature, the standard way to do it would be to use > nonblocking collective I/O, i.e., MPI_File_iwrite_all. This is > guaranteed to not block during the MPI_File_iwrite_all call. > > -- Pavan > > > On Feb 8, 2016, at 5:48 PM, pramod kumbhar > <pramod.s.kumbhar(a)gmail.com <mailto:[email protected]>> wrote: > > > > Hello All, > > > > I am testing MPI_FIle_write_all_begin/_end and it seems like > > MPI_File_write_all_begin waits for i/o completion. > > > > Could someone confirm the implementation of these routines? > > > > Thanks, > > Pramod > > _______________________________________________ > > discuss mailing list discuss(a)mpich.org <mailto:[email protected]> > > To manage subscription options or unsubscribe: > > https://lists.mpich.org/mailman/listinfo/discuss > > _______________________________________________ > discuss mailing list discuss(a)mpich.org <mailto:[email protected]> > 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] MPI I/O spilt collective implementation: MPI_File_write_all_begin blocking or non-blocking?
by pramod kumbhar 08 Feb '16

08 Feb '16

thanks! MPI_File_iwrite_all working as expected. -Pramod On Tue, Feb 9, 2016 at 12:52 AM, Balaji, Pavan <balaji(a)anl.gov> wrote: > > I believe it is valid to do that in split collectives. If you want truly > nonblocking nature, the standard way to do it would be to use nonblocking > collective I/O, i.e., MPI_File_iwrite_all. This is guaranteed to not block > during the MPI_File_iwrite_all call. > > -- Pavan > > > On Feb 8, 2016, at 5:48 PM, pramod kumbhar <pramod.s.kumbhar(a)gmail.com> > wrote: > > > > Hello All, > > > > I am testing MPI_FIle_write_all_begin/_end and it seems like > > MPI_File_write_all_begin waits for i/o completion. > > > > Could someone confirm the implementation of these routines? > > > > Thanks, > > Pramod > > _______________________________________________ > > 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] MPI I/O spilt collective implementation: MPI_File_write_all_begin blocking or non-blocking?
by Balaji, Pavan 08 Feb '16

08 Feb '16

I believe it is valid to do that in split collectives. If you want truly nonblocking nature, the standard way to do it would be to use nonblocking collective I/O, i.e., MPI_File_iwrite_all. This is guaranteed to not block during the MPI_File_iwrite_all call. -- Pavan > On Feb 8, 2016, at 5:48 PM, pramod kumbhar <pramod.s.kumbhar(a)gmail.com> wrote: > > Hello All, > > I am testing MPI_FIle_write_all_begin/_end and it seems like > MPI_File_write_all_begin waits for i/o completion. > > Could someone confirm the implementation of these routines? > > Thanks, > Pramod > _______________________________________________ > 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

MPI I/O spilt collective implementation: MPI_File_write_all_begin blocking or non-blocking?
by pramod kumbhar 08 Feb '16

08 Feb '16

Hello All, I am testing MPI_FIle_write_all_begin/_end and it seems like MPI_File_write_all_begin waits for i/o completion. Could someone confirm the implementation of these routines? Thanks, Pramod _______________________________________________ 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] MPI_File_open(...) - overwrite existing file
by Rob Latham 04 Feb '16

04 Feb '16

On 02/04/2016 11:01 AM, Thakur, Rajeev wrote: > It will not be truncated. If you need the file to be truncated, you will have to delete the file before opening. > this is a consistent theme in the standard. If you call MPI_FILE_SET_SIZE to shrink a file, it will also leave old data in an undefined state. ==rob > Rajeev > >> On Feb 4, 2016, at 10:37 AM, Florian.Willich(a)dlr.de wrote: >> >> Dear MPI Group, >> >> I'm wondering if the files created with the modes >> >> MPI_MODE_CREATE | MPI_MODE_WRONLY >> >> will be truncated to 0 if the file already exists calling MPI_File_open(...). >> >> As far as I tested it and also which is written in the standard: >> >> MPI_MODE_CREATE — create the file if it does not exist >> MPI_MODE_WRONLY — write only >> >> The existing file will be overwritten, but leaving the bytes that have not been explicitly overwritten. Thus, an existing file with the size of 8 Bytes and data to be written to of 4 Bytes will still be 8 Bytes after writing: With the 4 Bytes of the new data and 4 Bytes of the old data. >> >> As I read it, there is nothing defined what happens with the data of the file if it already exists [p 494, 1]. >> >> The POSIX / GNU lib c standard states that the file will be truncated to 0 if opened with 'w' and the file does already exists calling fopen(...) [p. 249, 2]: >> >> ‘w’ - Open the file for writing only. If the file already exists, it is truncated to zero length. Otherwise a new file is created. >> >> I really would appreciate some input if I'm wrong or not and what to do if the file needs to be truncated before writing (other then deleting the file before). >> >> Kind regards >> >> Florian Willich >> >> [1]: Message Passing Interface Forum. 2015. MPI: A Message-Passing Interface Standard Version 3.1. http://mpi-forum.org/docs/mpi-3.1/mpi31-report.pdf. [Online. Accessed 2nd December 2015]. >> >> [2]: Loosemore, Sandra, Stallman, Richard M., McGrath, Roland, Oram, Andrew, & Drepper, Ulrich. 2015. The GNU C Library Reference Manual. http://www.gnu.org/software/libc/manual/pdf/libc.pdf. [Online. Accessed 24th January 2016]. >> >> Deutsches Zentrum für Luft- und Raumfahrt e. V. (DLR) >> German Aerospace Center >> Institute of Planetary Research | Planetary Physics | Rutherfordstraße 2 | 12489 Berlin >> >> Florian Willich| Candidate for Bachelor of Science >> Software Developer (Parallel Applications) >> florian.willlich(a)dlr.de >> DLR.de >> _______________________________________________ >> 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] MPI_File_open(...) - overwrite existing file
by Thakur, Rajeev 04 Feb '16

04 Feb '16

It will not be truncated. If you need the file to be truncated, you will have to delete the file before opening. Rajeev > On Feb 4, 2016, at 10:37 AM, Florian.Willich(a)dlr.de wrote: > > Dear MPI Group, > > I'm wondering if the files created with the modes > > MPI_MODE_CREATE | MPI_MODE_WRONLY > > will be truncated to 0 if the file already exists calling MPI_File_open(...). > > As far as I tested it and also which is written in the standard: > > MPI_MODE_CREATE — create the file if it does not exist > MPI_MODE_WRONLY — write only > > The existing file will be overwritten, but leaving the bytes that have not been explicitly overwritten. Thus, an existing file with the size of 8 Bytes and data to be written to of 4 Bytes will still be 8 Bytes after writing: With the 4 Bytes of the new data and 4 Bytes of the old data. > > As I read it, there is nothing defined what happens with the data of the file if it already exists [p 494, 1]. > > The POSIX / GNU lib c standard states that the file will be truncated to 0 if opened with 'w' and the file does already exists calling fopen(...) [p. 249, 2]: > > ‘w’ - Open the file for writing only. If the file already exists, it is truncated to zero length. Otherwise a new file is created. > > I really would appreciate some input if I'm wrong or not and what to do if the file needs to be truncated before writing (other then deleting the file before). > > Kind regards > > Florian Willich > > [1]: Message Passing Interface Forum. 2015. MPI: A Message-Passing Interface Standard Version 3.1. http://mpi-forum.org/docs/mpi-3.1/mpi31-report.pdf. [Online. Accessed 2nd December 2015]. > > [2]: Loosemore, Sandra, Stallman, Richard M., McGrath, Roland, Oram, Andrew, & Drepper, Ulrich. 2015. The GNU C Library Reference Manual. http://www.gnu.org/software/libc/manual/pdf/libc.pdf. [Online. Accessed 24th January 2016]. > > Deutsches Zentrum für Luft- und Raumfahrt e. V. (DLR) > German Aerospace Center > Institute of Planetary Research | Planetary Physics | Rutherfordstraße 2 | 12489 Berlin > > Florian Willich| Candidate for Bachelor of Science > Software Developer (Parallel Applications) > florian.willlich(a)dlr.de > DLR.de > _______________________________________________ > 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

MPI_File_open(...) - overwrite existing file
by Florian.Willich＠dlr.de 04 Feb '16

04 Feb '16

Dear MPI Group, I'm wondering if the files created with the modes MPI_MODE_CREATE | MPI_MODE_WRONLY will be truncated to 0 if the file already exists calling MPI_File_open(...). As far as I tested it and also which is written in the standard: MPI_MODE_CREATE — create the file if it does not exist MPI_MODE_WRONLY — write only The existing file will be overwritten, but leaving the bytes that have not been explicitly overwritten. Thus, an existing file with the size of 8 Bytes and data to be written to of 4 Bytes will still be 8 Bytes after writing: With the 4 Bytes of the new data and 4 Bytes of the old data. As I read it, there is nothing defined what happens with the data of the file if it already exists [p 494, 1]. The POSIX / GNU lib c standard states that the file will be truncated to 0 if opened with 'w' and the file does already exists calling fopen(...) [p. 249, 2]: ‘w’ - Open the file for writing only. If the file already exists, it is truncated to zero length. Otherwise a new file is created. I really would appreciate some input if I'm wrong or not and what to do if the file needs to be truncated before writing (other then deleting the file before). Kind regards Florian Willich [1]: Message Passing Interface Forum. 2015. MPI: A Message-Passing Interface Standard Version 3.1. http://mpi-forum.org/docs/mpi-3.1/mpi31-report.pdf. [Online. Accessed 2nd December 2015]. [2]: Loosemore, Sandra, Stallman, Richard M., McGrath, Roland, Oram, Andrew, & Drepper, Ulrich. 2015. The GNU C Library Reference Manual. http://www.gnu.org/software/libc/manual/pdf/libc.pdf. [Online. Accessed 24th January 2016]. Deutsches Zentrum für Luft- und Raumfahrt e. V. (DLR) German Aerospace Center Institute of Planetary Research | Planetary Physics | Rutherfordstraße 2 | 12489 Berlin Florian Willich| Candidate for Bachelor of Science Software Developer (Parallel Applications) florian.willlich(a)dlr.de<mailto:[email protected]> DLR.de<http://www.dlr.de/> _______________________________________________ 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 while loading shared libraries: libtorque.so.2
by Kenneth Raffenetti 04 Feb '16

04 Feb '16

Can you send your configure line and also the config.log file from src/pm/hydra/config.log? Ken On 02/04/2016 07:22 AM, Xiangdong wrote: > Hello everyone, > > I have a question on installing mpich 3.2. I followed the standard > ./configure make make install to install the mpich. However, when I run > the mpiexec, it complains "mpiexec: error while loading shared > libraries: libtorque.so.2". There is no pbs installed on my system. Why > does it need pbs? How can I fix this? > > Thanks. > > Xiangdong > > > _______________________________________________ > 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

error while loading shared libraries: libtorque.so.2
by Xiangdong 04 Feb '16

04 Feb '16

Hello everyone, I have a question on installing mpich 3.2. I followed the standard ./configure make make install to install the mpich. However, when I run the mpiexec, it complains "mpiexec: error while loading shared libraries: libtorque.so.2". There is no pbs installed on my system. Why does it need pbs? How can I fix this? Thanks. Xiangdong _______________________________________________ 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 03 Feb '16

03 Feb '16

On 02/03/2016 07:12 AM, Siegmar Gross wrote: > Hi Rob, > > today I tried to build mpich-master-v3.2-169-gff06d55a59a3 and got the > same errors as before. Installing "libunwind-devel" solved the problem > for gcc-5.2.0 but not for Sun C 5.13. Do you know, when your patches > will be available in a nightly tarball? > sorry about that. it's sitting in my working copy, but I never got it reviewed and into master. I just committed it and any nightly tarball that includes commit 14f0484f will do the trick. should be a day or two. ==rob > > Kind regards > > Siegmar > > > On 01/20/16 13:18, Siegmar Gross wrote: >> 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 > _______________________________________________ > 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