September 2014 - discuss - mailman3.cels.anl.gov

Specifying a timeout for MPI_Comm_Accept
by Roy, Hirak 06 Sep '14

06 Sep '14

Hi, The thread at the end of my email, shows that there is no way we can specify a timeout in MPI_Comm_accept/connect. Since the thread is pretty old (2007), I would like to know if there is any development related to this or not? If we still can not specify a timeout, is there any provision of non-blocking accept/connect ? Thanks, Hirak https://lists.mcs.anl.gov/mailman/htdig/mpich-discuss/2007-April/002159.html

1 0

Re: [mpich-discuss] Error building mpich-3.1.2 on Solaris 10 with gcc-4.9.0
by Balaji, Pavan 06 Sep '14

06 Sep '14

Thanks, Siegmar. Are you seeing some errors with “make testing” or are all tests failing? On some platforms, some tests take longer and hence show up as “timeouts”, but they are not really hanging. But the number of such tests should be small. We’ll look into the C++ issues. We are trying to get a machine setup locally to test this configuration out. Regards, — Pavan On Sep 6, 2014, at 2:24 AM, Siegmar Gross <Siegmar.Gross(a)informatik.hs-fulda.de> wrote: > Hi, > >> Could you configure with --disable-cxx to see if you can continue? > > I can build MPICH with gcc-4.9.0 without C++ bindings on Solaris 10 > Sparc and x86_64. > > tyr small_prog 114 mpichversion > MPICH Version: 3.2a1 > MPICH Release date: Fri Sep 5 00:00:35 CDT 2014 > MPICH Device: ch3:nemesis > MPICH configure: --prefix=/usr/local/mpich-3.2_64_gcc > --libdir=/usr/local/mpich-3.2_64_gcc/lib64 > --includedir=/usr/local/mpich-3.2_64_gcc/include64 > CC=gcc CXX=g++ F77=gfortran FC=gfortran CFLAGS=-m64 CXXFLAGS=-m64 > FFLAGS=-m64 FCFLAGS=-m64 LDFLAGS=-m64 > -L/usr/lib/sparcv9 -Wl,-rpath /usr/lib/sparcv9 --enable-f77 --enable-fc > --disable-cxx --enable-romio --enable-debuginfo --enable-smpcoll > --enable-threads=runtime --with-thread-package=posix --enable-shared > MPICH CC: gcc -m64 -O2 > MPICH CXX: no -m64 > MPICH F77: gfortran -m64 -O2 > MPICH FC: gfortran -m64 -O2 > > tyr small_prog 115 mpicc init_finalize.c > tyr small_prog 116 mpiexec -np 1 a.out > Hello! > > tyr small_prog 117 mpicc thread_support.c > tyr small_prog 118 mpiexec -np 1 a.out > I have requested MPI_THREAD_MULTIPLE in "MPI_Init_thread ()" and > it provides MPI_THREAD_MULTIPLE > "MPI_Query_thread ()" returned MPI_THREAD_MULTIPLE: > Many threads are supported and any thread may call > MPI functions at any time. > "MPI_Is_thread_main ()" returned: "true". > tyr small_prog 119 > > > I have attached my config and log files for my Solaris Sparc version > (even "make check" works fine). However, I get errors with "make > testing" (APPLICATION TIMED OUT). Generally, I only use "make check", > so perhaps I have to do it in a different way (e.g., running the test > as normal user and not as root). I stopped this test. > > By the way, you can avoid the warning about X11/Xutil.h, if you include > X11/Xlib.h before this header file. > > tyr mpich-3.2-SunOS.sparc.64_gcc_disable-cxx 135 more /usr/include/X11/Xutil.h > /* $TOG: Xutil.h /main/45 1998/02/06 18:03:35 kaleb $ */ > ... > /* You must include <X11/Xlib.h> before including this file */ > ... > > > I would be grateful, if you can fix the problem for C++ bindings. > C++ bindings are available in my Sun C 5.12 version of MPICH. > > tyr fd1026 101 mpichversion > MPICH Version: 3.2a1 > MPICH Release date: Fri Sep 5 00:00:35 CDT 2014 > MPICH Device: ch3:nemesis > MPICH configure: --prefix=/usr/local/mpich-3.2_64_cc > --libdir=/usr/local/mpich-3.2_64_cc/lib64 > --includedir=/usr/local/mpich-3.2_64_cc/include64 > CC=cc CXX=CC F77=f77 FC=f95 CFLAGS=-m64 CXXFLAGS=-m64 > FFLAGS=-m64 FCFLAGS=-m64 LDFLAGS=-m64 > -L/usr/lib/sparcv9 -R/usr/lib/sparcv9 --enable-f77 --enable-fc > --enable-cxx --enable-romio --enable-debuginfo --enable-smpcoll > --enable-threads=runtime --with-thread-package=posix --enable-shared > MPICH CC: cc -m64 -O2 > MPICH CXX: CC -m64 -O2 > MPICH F77: f77 -m64 > MPICH FC: f95 -m64 -O2 > tyr fd1026 102 > > > Kind regards and thank you very much for any help in advance > > Siegmar > > >> --Junchao Zhang >> >> >> On Fri, Sep 5, 2014 at 2:26 PM, Siegmar Gross < >> Siegmar.Gross(a)informatik.hs-fulda.de> wrote: >> >>> Hi, >>> >>> thank you very much for all answers to my problems building >>> MPICH on Solaris with gcc-4.9.0. Today I tried to build >>> mpich-master-v3.2a1. Unfortunately I have had the same problems. >>> >>>> 1) For the linking errors you should provide the full build log but it >>>> could just be an issue with the order of arguments passed to Solaris ld, >>> or >>>> if you compiled gcc to use GNU ld, the same issue might occur if the >>>> configure script assumes Solaris => Solaris ld. >>> >>> I have attached the files in the archive >>> mpich-3.2-SunOS.sparc.64_gcc_only-m64.tar.gz >>> >>> >>>> 2) I keep this sticky note on my wiki: >>>> >>>> "Compiler or options invalid for pre-UNIX 03 X/Open applications and >>>> pre-2001 POSIX applications" >>>> >>>> >>> /usr/gcc/4.6/lib/gcc/i386-pc-solaris2.11/4.6.3/include-fixed/sys/feature_tests.h:362:2: >>>> error: #error "Compiler or options invalid for pre-UNIX 03 X/Open >>> applications >>>> and pre-2001 POSIX applications" >>>> >>>> Conflict of standards between _XOPEN_SOURCE and C99 extensions. >>>> >>>> #if defined(_STDC_C99) && (defined(__XOPEN_OR_POSIX) && !defined(_XPG6)) >>>> >>>> As GCC standards do not match ANSI/ISO/POSIX standards strictly you need >>> to >>>> specify the standard you want to comply with. >>>> Usually adding -D_XOPEN_SOURCE=500 (or 600) and/or -D__EXTENSIONS__ to >>> your >>>> compiler flags is a good start. >>> >>> It was a little bit more complicated to get this one as far as >>> the build with just "CFLAGS=-m64". Adding "-D__EXTENSIONS__" broke >>> the build process. Adding "-D_XOPEN_SOURCE=500" didn't solve the >>> problem, because Solaris expects "-D_XOPEN_SOURCE=600". Using this >>> flag wasn't helpful, because you redefined it to "500" in file >>> mpich-master-v3.2a1/src/mpi/romio/adio/common/ad_read.c, so that I >>> had to add "-D_STDC_C99" to keep "600". Another problem came from >>> file /usr/include/sys/statvfs.h ("FSTYPSZ" wasn't defined). Looking >>> into the file showed the following. >>> >>> ... >>> #define _FSTYPSZ 16 >>> #if !defined(_XPG4_2) || defined(__EXTENSIONS__) >>> #ifndef FSTYPSZ >>> #define FSTYPSZ _FSTYPSZ >>> #endif >>> ... >>> >>> Finally I could build MPICH with "CFLAGS=-m64 -std=c99 -D_STDC_C99 >>> -D_POSIX_C_SOURCE=200112L -D_XOPEN_SOURCE=600 -DFSTYPSZ=_FSTYPSZ" >>> to the same point as with "CFLAGS=-m64". In both cases libmpicxx.so >>> wasn't available. I have attached the files for this build process >>> in the archive mpich-3.2-SunOS.sparc.64_gcc.tar.gz. Please let me >>> know if you need anything else. >>> >>> Kind regards >>> >>> Siegmar >>> >>> _______________________________________________ >>> discuss mailing list discuss(a)mpich.org >>> To manage subscription options or unsubscribe: >>> https://lists.mpich.org/mailman/listinfo/discuss >>> > <mpich-3.2-SunOS.sparc.64_gcc_disable-cxx.tar.gz>_______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss -- Pavan Balaji ✉️ http://www.mcs.anl.gov/~balaji

1 0

Re: [mpich-discuss] Error building mpich-3.1.2 on Solaris 10 with gcc-4.9.0
by Siegmar Gross 06 Sep '14

06 Sep '14

Hi, > Could you configure with --disable-cxx to see if you can continue? I can build MPICH with gcc-4.9.0 without C++ bindings on Solaris 10 Sparc and x86_64. tyr small_prog 114 mpichversion MPICH Version: 3.2a1 MPICH Release date: Fri Sep 5 00:00:35 CDT 2014 MPICH Device: ch3:nemesis MPICH configure: --prefix=/usr/local/mpich-3.2_64_gcc --libdir=/usr/local/mpich-3.2_64_gcc/lib64 --includedir=/usr/local/mpich-3.2_64_gcc/include64 CC=gcc CXX=g++ F77=gfortran FC=gfortran CFLAGS=-m64 CXXFLAGS=-m64 FFLAGS=-m64 FCFLAGS=-m64 LDFLAGS=-m64 -L/usr/lib/sparcv9 -Wl,-rpath /usr/lib/sparcv9 --enable-f77 --enable-fc --disable-cxx --enable-romio --enable-debuginfo --enable-smpcoll --enable-threads=runtime --with-thread-package=posix --enable-shared MPICH CC: gcc -m64 -O2 MPICH CXX: no -m64 MPICH F77: gfortran -m64 -O2 MPICH FC: gfortran -m64 -O2 tyr small_prog 115 mpicc init_finalize.c tyr small_prog 116 mpiexec -np 1 a.out Hello! tyr small_prog 117 mpicc thread_support.c tyr small_prog 118 mpiexec -np 1 a.out I have requested MPI_THREAD_MULTIPLE in "MPI_Init_thread ()" and it provides MPI_THREAD_MULTIPLE "MPI_Query_thread ()" returned MPI_THREAD_MULTIPLE: Many threads are supported and any thread may call MPI functions at any time. "MPI_Is_thread_main ()" returned: "true". tyr small_prog 119 I have attached my config and log files for my Solaris Sparc version (even "make check" works fine). However, I get errors with "make testing" (APPLICATION TIMED OUT). Generally, I only use "make check", so perhaps I have to do it in a different way (e.g., running the test as normal user and not as root). I stopped this test. By the way, you can avoid the warning about X11/Xutil.h, if you include X11/Xlib.h before this header file. tyr mpich-3.2-SunOS.sparc.64_gcc_disable-cxx 135 more /usr/include/X11/Xutil.h /* $TOG: Xutil.h /main/45 1998/02/06 18:03:35 kaleb $ */ ... /* You must include <X11/Xlib.h> before including this file */ ... I would be grateful, if you can fix the problem for C++ bindings. C++ bindings are available in my Sun C 5.12 version of MPICH. tyr fd1026 101 mpichversion MPICH Version: 3.2a1 MPICH Release date: Fri Sep 5 00:00:35 CDT 2014 MPICH Device: ch3:nemesis MPICH configure: --prefix=/usr/local/mpich-3.2_64_cc --libdir=/usr/local/mpich-3.2_64_cc/lib64 --includedir=/usr/local/mpich-3.2_64_cc/include64 CC=cc CXX=CC F77=f77 FC=f95 CFLAGS=-m64 CXXFLAGS=-m64 FFLAGS=-m64 FCFLAGS=-m64 LDFLAGS=-m64 -L/usr/lib/sparcv9 -R/usr/lib/sparcv9 --enable-f77 --enable-fc --enable-cxx --enable-romio --enable-debuginfo --enable-smpcoll --enable-threads=runtime --with-thread-package=posix --enable-shared MPICH CC: cc -m64 -O2 MPICH CXX: CC -m64 -O2 MPICH F77: f77 -m64 MPICH FC: f95 -m64 -O2 tyr fd1026 102 Kind regards and thank you very much for any help in advance Siegmar > --Junchao Zhang > > > On Fri, Sep 5, 2014 at 2:26 PM, Siegmar Gross < > Siegmar.Gross(a)informatik.hs-fulda.de> wrote: > > > Hi, > > > > thank you very much for all answers to my problems building > > MPICH on Solaris with gcc-4.9.0. Today I tried to build > > mpich-master-v3.2a1. Unfortunately I have had the same problems. > > > > > 1) For the linking errors you should provide the full build log but it > > > could just be an issue with the order of arguments passed to Solaris ld, > > or > > > if you compiled gcc to use GNU ld, the same issue might occur if the > > > configure script assumes Solaris => Solaris ld. > > > > I have attached the files in the archive > > mpich-3.2-SunOS.sparc.64_gcc_only-m64.tar.gz > > > > > > > 2) I keep this sticky note on my wiki: > > > > > > "Compiler or options invalid for pre-UNIX 03 X/Open applications and > > > pre-2001 POSIX applications" > > > > > > > > /usr/gcc/4.6/lib/gcc/i386-pc-solaris2.11/4.6.3/include-fixed/sys/feature_tests.h:362:2: > > > error: #error "Compiler or options invalid for pre-UNIX 03 X/Open > > applications > > > and pre-2001 POSIX applications" > > > > > > Conflict of standards between _XOPEN_SOURCE and C99 extensions. > > > > > > #if defined(_STDC_C99) && (defined(__XOPEN_OR_POSIX) && !defined(_XPG6)) > > > > > > As GCC standards do not match ANSI/ISO/POSIX standards strictly you need > > to > > > specify the standard you want to comply with. > > > Usually adding -D_XOPEN_SOURCE=500 (or 600) and/or -D__EXTENSIONS__ to > > your > > > compiler flags is a good start. > > > > It was a little bit more complicated to get this one as far as > > the build with just "CFLAGS=-m64". Adding "-D__EXTENSIONS__" broke > > the build process. Adding "-D_XOPEN_SOURCE=500" didn't solve the > > problem, because Solaris expects "-D_XOPEN_SOURCE=600". Using this > > flag wasn't helpful, because you redefined it to "500" in file > > mpich-master-v3.2a1/src/mpi/romio/adio/common/ad_read.c, so that I > > had to add "-D_STDC_C99" to keep "600". Another problem came from > > file /usr/include/sys/statvfs.h ("FSTYPSZ" wasn't defined). Looking > > into the file showed the following. > > > > ... > > #define _FSTYPSZ 16 > > #if !defined(_XPG4_2) || defined(__EXTENSIONS__) > > #ifndef FSTYPSZ > > #define FSTYPSZ _FSTYPSZ > > #endif > > ... > > > > Finally I could build MPICH with "CFLAGS=-m64 -std=c99 -D_STDC_C99 > > -D_POSIX_C_SOURCE=200112L -D_XOPEN_SOURCE=600 -DFSTYPSZ=_FSTYPSZ" > > to the same point as with "CFLAGS=-m64". In both cases libmpicxx.so > > wasn't available. I have attached the files for this build process > > in the archive mpich-3.2-SunOS.sparc.64_gcc.tar.gz. Please let me > > know if you need anything else. > > > > Kind regards > > > > Siegmar > > > > _______________________________________________ > > 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 building mpich-3.1.2 on Solaris 10 with gcc-4.9.0
by Junchao Zhang 05 Sep '14

05 Sep '14

Could you configure with --disable-cxx to see if you can continue? --Junchao Zhang On Fri, Sep 5, 2014 at 2:26 PM, Siegmar Gross < Siegmar.Gross(a)informatik.hs-fulda.de> wrote: > Hi, > > thank you very much for all answers to my problems building > MPICH on Solaris with gcc-4.9.0. Today I tried to build > mpich-master-v3.2a1. Unfortunately I have had the same problems. > > > 1) For the linking errors you should provide the full build log but it > > could just be an issue with the order of arguments passed to Solaris ld, > or > > if you compiled gcc to use GNU ld, the same issue might occur if the > > configure script assumes Solaris => Solaris ld. > > I have attached the files in the archive > mpich-3.2-SunOS.sparc.64_gcc_only-m64.tar.gz > > > > 2) I keep this sticky note on my wiki: > > > > "Compiler or options invalid for pre-UNIX 03 X/Open applications and > > pre-2001 POSIX applications" > > > > > /usr/gcc/4.6/lib/gcc/i386-pc-solaris2.11/4.6.3/include-fixed/sys/feature_tests.h:362:2: > > error: #error "Compiler or options invalid for pre-UNIX 03 X/Open > applications > > and pre-2001 POSIX applications" > > > > Conflict of standards between _XOPEN_SOURCE and C99 extensions. > > > > #if defined(_STDC_C99) && (defined(__XOPEN_OR_POSIX) && !defined(_XPG6)) > > > > As GCC standards do not match ANSI/ISO/POSIX standards strictly you need > to > > specify the standard you want to comply with. > > Usually adding -D_XOPEN_SOURCE=500 (or 600) and/or -D__EXTENSIONS__ to > your > > compiler flags is a good start. > > It was a little bit more complicated to get this one as far as > the build with just "CFLAGS=-m64". Adding "-D__EXTENSIONS__" broke > the build process. Adding "-D_XOPEN_SOURCE=500" didn't solve the > problem, because Solaris expects "-D_XOPEN_SOURCE=600". Using this > flag wasn't helpful, because you redefined it to "500" in file > mpich-master-v3.2a1/src/mpi/romio/adio/common/ad_read.c, so that I > had to add "-D_STDC_C99" to keep "600". Another problem came from > file /usr/include/sys/statvfs.h ("FSTYPSZ" wasn't defined). Looking > into the file showed the following. > > ... > #define _FSTYPSZ 16 > #if !defined(_XPG4_2) || defined(__EXTENSIONS__) > #ifndef FSTYPSZ > #define FSTYPSZ _FSTYPSZ > #endif > ... > > Finally I could build MPICH with "CFLAGS=-m64 -std=c99 -D_STDC_C99 > -D_POSIX_C_SOURCE=200112L -D_XOPEN_SOURCE=600 -DFSTYPSZ=_FSTYPSZ" > to the same point as with "CFLAGS=-m64". In both cases libmpicxx.so > wasn't available. I have attached the files for this build process > in the archive mpich-3.2-SunOS.sparc.64_gcc.tar.gz. Please let me > know if you need anything else. > > Kind regards > > Siegmar > > _______________________________________________ > 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 building mpich-3.1.2 on Solaris 10 with gcc-4.9.0
by Siegmar Gross 05 Sep '14

05 Sep '14

Hi, thank you very much for all answers to my problems building MPICH on Solaris with gcc-4.9.0. Today I tried to build mpich-master-v3.2a1. Unfortunately I have had the same problems. > 1) For the linking errors you should provide the full build log but it > could just be an issue with the order of arguments passed to Solaris ld, or > if you compiled gcc to use GNU ld, the same issue might occur if the > configure script assumes Solaris => Solaris ld. I have attached the files in the archive mpich-3.2-SunOS.sparc.64_gcc_only-m64.tar.gz > 2) I keep this sticky note on my wiki: > > "Compiler or options invalid for pre-UNIX 03 X/Open applications and > pre-2001 POSIX applications" > > /usr/gcc/4.6/lib/gcc/i386-pc-solaris2.11/4.6.3/include-fixed/sys/feature_tests.h:362:2: > error: #error "Compiler or options invalid for pre-UNIX 03 X/Open applications > and pre-2001 POSIX applications" > > Conflict of standards between _XOPEN_SOURCE and C99 extensions. > > #if defined(_STDC_C99) && (defined(__XOPEN_OR_POSIX) && !defined(_XPG6)) > > As GCC standards do not match ANSI/ISO/POSIX standards strictly you need to > specify the standard you want to comply with. > Usually adding -D_XOPEN_SOURCE=500 (or 600) and/or -D__EXTENSIONS__ to your > compiler flags is a good start. It was a little bit more complicated to get this one as far as the build with just "CFLAGS=-m64". Adding "-D__EXTENSIONS__" broke the build process. Adding "-D_XOPEN_SOURCE=500" didn't solve the problem, because Solaris expects "-D_XOPEN_SOURCE=600". Using this flag wasn't helpful, because you redefined it to "500" in file mpich-master-v3.2a1/src/mpi/romio/adio/common/ad_read.c, so that I had to add "-D_STDC_C99" to keep "600". Another problem came from file /usr/include/sys/statvfs.h ("FSTYPSZ" wasn't defined). Looking into the file showed the following. ... #define _FSTYPSZ 16 #if !defined(_XPG4_2) || defined(__EXTENSIONS__) #ifndef FSTYPSZ #define FSTYPSZ _FSTYPSZ #endif ... Finally I could build MPICH with "CFLAGS=-m64 -std=c99 -D_STDC_C99 -D_POSIX_C_SOURCE=200112L -D_XOPEN_SOURCE=600 -DFSTYPSZ=_FSTYPSZ" to the same point as with "CFLAGS=-m64". In both cases libmpicxx.so wasn't available. I have attached the files for this build process in the archive mpich-3.2-SunOS.sparc.64_gcc.tar.gz. Please let me know if you need anything else. Kind regards Siegmar

1 0

Re: [mpich-discuss] Error building mpich-master-v3.1.2-131-gfa09f8e3 on Solaris 10 with gcc-4.9.0
by Kenneth Raffenetti 05 Sep '14

05 Sep '14

Hi Siegmar, Sorry for the delay in responding. I've created ticket 2168 (https://trac.mpich.org/projects/mpich/ticket/2168#ticket) to track these issues down. Unfortunately I don't have a Sparc machine to test on, but I'll do what I can on x86-64. Ken On 09/02/2014 12:17 PM, Siegmar Gross wrote: > Hi, > > yesterday I tried to install mpich-master-v3.1.2-131-gfa09f8e3 on > my machines (Solaris 10 Sparc, Solaris 10 x86_64, and openSUSE > Linux 12.1 x86_64) with Sun C 5.12 and gcc-4.9.0 and failed with > the following errors for gcc on my Solaris platforms as well. > > > I configured once more with the following command. > > tyr mpich-3.1.3-SunOS.sparc.64_gcc 254 head -8 config.log | grep mpich > $ ../mpich-master-v3.1.2-131-gfa09f8e3/configure > --prefix=/usr/local/mpich-3.1.3_64_gcc > --libdir=/usr/local/mpich-3.1.3_64_gcc/lib64 > --includedir=/usr/local/mpich-3.1.3_64_gcc/include64 > CC=gcc CXX=g++ F77=gfortran FC=gfortran CFLAGS=-m64 CXXFLAGS=-m64 > FFLAGS=-m64 FCFLAGS=-m64 LDFLAGS=-m64 -L/usr/lib/sparcv9 > -Wl,-rpath /usr/lib/sparcv9 --enable-f77 --enable-fc --enable-cxx > --enable-romio --enable-debuginfo --enable-smpcoll > --enable-threads=runtime --with-thread-package=posix --enable-shared > > > tyr mpich-3.1.3-SunOS.sparc.64_gcc 110 tail log.make.SunOS.sparc.64_gcc > CXX src/binding/cxx/initcxx.lo > CXXLD lib/libmpicxx.la > ld: fatal: file libmpicxx.so.12: open failed: No such file or directory > ld: fatal: file processing errors. No output written to lib/.libs/libmpicxx.so.12.0.2 > collect2: error: ld returned 1 exit status > make[2]: *** [lib/libmpicxx.la] Error 1 > make[2]: Leaving directory `/export2/src/mpich-3.1.3/mpich-3.1.3-SunOS.sparc.64_gcc' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/export2/src/mpich-3.1.3/mpich-3.1.3-SunOS.sparc.64_gcc' > make: *** [all] Error 2 > > > I get the same error which I reported for mpich-3.1.2, if I use > "CFLAGS=-m64 -std=c11". > > > 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 >

1 0

Re: [mpich-discuss] MPICH 3.1.2 update for OpenIndiana.
by Balaji, Pavan 04 Sep '14

04 Sep '14

Thanks! I’ve added the below link to our downloads page. http://www.mpich.org/downloads/ Regards, — Pavan On Sep 4, 2014, at 10:25 AM, Aurélien Larcher <aurelien.larcher(a)gmail.com> wrote: > Hi, > just a quick note to inform that I updated mpich from 3.0.4 to 3.1.2, compiled with GCC 4.8.3. > x86 32 and 64 bits versions are available together with modulefiles to allow switching between them. > > larcher@na75:> module avail mpich > > ------------------------ /usr/share/Modules/modulefiles ------------------------ > mpich/gcc/32/3.1.2 mpich/gcc/64/3.1.2 > mpich/gcc/32/latest mpich/gcc/64/latest > > Packages are available from the current repository: > > http://pkg.openindiana.org/hipster-2014.1/en/search.shtml?token=mpich%2Fgcc… > > Best regards, > > Aurelien > > -- > ------------------------------------------------------------------------------- > LARCHER Aurélien | KTH, School of Computer Science and Communication > Work: +46 (0) 8 790 71 42 | Lindstedtsvägen 5, Plan 4, 100 44 Stockholm, SWEDEN > ------------------------------------------------------------------------------- > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss -- Pavan Balaji ✉️ http://www.mcs.anl.gov/~balaji

1 0

MPICH 3.1.2 update for OpenIndiana.
by Aurélien Larcher 04 Sep '14

04 Sep '14

Hi, just a quick note to inform that I updated mpich from 3.0.4 to 3.1.2, compiled with GCC 4.8.3. x86 32 and 64 bits versions are available together with modulefiles to allow switching between them. larcher@na75:> module avail mpich ------------------------ /usr/share/Modules/modulefiles ------------------------ mpich/gcc/32/3.1.2 mpich/gcc/64/3.1.2 mpich/gcc/32/latest mpich/gcc/64/latest Packages are available from the current repository: http://pkg.openindiana.org/hipster-2014.1/en/search.shtml?token=mpich%2Fgcc… Best regards, Aurelien -- ------------------------------------------------------------------------------- LARCHER Aurélien | KTH, School of Computer Science and Communication Work: +46 (0) 8 790 71 42 | Lindstedtsvägen 5, Plan 4, 100 44 Stockholm, SWEDEN -------------------------------------------------------------------------------

1 0

Re: [mpich-discuss] Error building mpich-3.1.2 on Solaris 10 with gcc-4.9.0
by Aurélien Larcher 04 Sep '14

04 Sep '14

Hi Siegmar, 1) For the linking errors you should provide the full build log but it could just be an issue with the order of arguments passed to Solaris ld, or if you compiled gcc to use GNU ld, the same issue might occur if the configure script assumes Solaris => Solaris ld. 2) I keep this sticky note on my wiki: "Compiler or options invalid for pre-UNIX 03 X/Open applications and pre-2001 POSIX applications" /usr/gcc/4.6/lib/gcc/i386-pc-solaris2.11/4.6.3/include-fixed/sys/feature_tests.h:362:2: error: #error "Compiler or options invalid for pre-UNIX 03 X/Open applications and pre-2001 POSIX applications" Conflict of standards between _XOPEN_SOURCE and C99 extensions. #if defined(_STDC_C99) && (defined(__XOPEN_OR_POSIX) && !defined(_XPG6)) As GCC standards do not match ANSI/ISO/POSIX standards strictly you need to specify the standard you want to comply with. Usually adding -D_XOPEN_SOURCE=500 (or 600) and/or -D__EXTENSIONS__ to your compiler flags is a good start. Read the 'standards' manpage for further explanations, it is well documented. Best regards Aurelien -- ------------------------------------------------------------------------------- LARCHER Aurélien | KTH, School of Computer Science and Communication Work: +46 (0) 8 790 71 42 | Lindstedtsvägen 5, Plan 4, 100 44 Stockholm, SWEDEN -------------------------------------------------------------------------------

1 0

Announcing the availability of mpich-3.2a1
by Balaji, Pavan 04 Sep '14

04 Sep '14

The MPICH team is pleased to announce the availability of a new preview release (mpich-3.2a1). This preview release is the first in a new major version series in mpich (3.2.x), and adds several capabilities including full Fortran 2008 support (enabled by default), support for the Mellanox MXM interface for InfiniBand, and support for OFED InfiniBand for Xeon and Xeon Phi architectures. These features represent a subset of those planned for the 3.2.x release series (complete list: https://trac.mpich.org/projects/mpich/roadmap) http://www.mpich.org Please note that this is a preview release primarily aimed at receiving feedback from users on the new features. This release is not meant for production systems at this time. A list of changes in this release is included at the end of this email. Regards, The MPICH Team =============================================================================== Changes in 3.2a1 =============================================================================== # Fortran 2008 bindings are enabled by default and fully supported. # Added support for the Mellanox MXM InfiniBand interface. (thanks to Mellanox for the code contribution). # Added support for OFED IB on Xeon and Xeon Phi. (thanks to RIKEN and University of Tokyo for the contribution). # Several other minor bug fixes, memory leak fixes, and code cleanup. A full list of changes is available at the following link: http://git.mpich.org/mpich.git/shortlog/v3.1.2..v3.2a1 A full list of bugs that have been fixed is available at the following link: https://trac.mpich.org/projects/mpich/query?status=closed&group=resolution&… -- Pavan Balaji ✉️ http://www.mcs.anl.gov/~balaji

1 0