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

Re: [mpich-discuss] Is there any easy way to determine what version of MPICH2 is installed in Windows? (EOM)
by Lu, Huiwei 26 Jun '14

26 Jun '14

The usual way is typing mpichversion in command line for Linux. I don’t know if that works for Windows too. BTW, due to lack of developer resources, MPICH no longer supports the Windows platform. Please refer to our FAQ for more information: http://wiki.mpich.org/mpich/index.php/Frequently_Asked_Questions#Q:_Why_can… — Huiwei On Jun 26, 2014, at 1:20 PM, Qiguo Jing <qjing(a)trinityconsultants.com> wrote: > > _________________________________________________________________________ > > The information transmitted is intended only for the person or entity to > which it is addressed and may contain confidential and/or privileged > material. Any review, retransmission, dissemination or other use of, or > taking of any action in reliance upon, this information by persons or > entities other than the intended recipient is prohibited. If you received > this in error, please contact the sender and delete the material from any > computer. > _________________________________________________________________________ > > _______________________________________________ > > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss

1 0

Is there any easy way to determine what version of MPICH2 is installed in Windows? (EOM)
by Qiguo Jing 26 Jun '14

26 Jun '14

_________________________________________________________________________ The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. _________________________________________________________________________

1 0

MPICH 3.1.1 and MPI_*_c2f
by Chris January 26 Jun '14

26 Jun '14

Hello all, I noticed that MPICH 3.1.1 changed which libraries symbols go in. The MPI_*_c2f functions are no longer available to source files compiled with mpicc and mpicxx (unless you explicitly add -lmpifort). In our opinion the MPI_*_c2f and MPI_* symbols should be available from all compiler drivers (mpicc, mpicxx, mpif77, mpif90, etc.) without the need to explicitly add -lmpifort. Since they are used to convert values between C and Fortran and vice versa it is natural that one would want to use them from both languages. Existing code which assumes, I believe quite reasonably, that MPI_*_c2f, etc. can be used from mpicc with no extra effort fails to compile with MPICH 3.1.1. I think this is a regression which should be fixed. Yours, Chris January - VP Engineering - Allinea Software Ltd.

1 0

Re: [mpich-discuss] couldn't build mpich-3.1.1 on Solaris 10withgcc-4.9.0
by Siegmar Gross 26 Jun '14

26 Jun '14

Hi, > I would suggest build a 64-bit libxml2 instead of using -m64 for MPICH. The library is available. tyr mpich-3.1.1 431 file /usr/lib/sparcv9/libxml2.so /usr/lib/sparcv9/libxml2.so: ELF 64-bit MSB dynamic lib SPARCV9 Version 1, dynamically linked, not stripped, no debugging information available I get also an error if I try to build a 32-bit version with gcc-4.9.0. ../mpich-3.1.1/configure --prefix=/usr/local/mpich-3.1.1_32_gcc \ CC="gcc" CXX="g++" F77="gfortran" FC="gfortran" \ CFLAGS="" CXXFLAGS="" FFLAGS="" FCFLAGS="" \ LDFLAGS="-L/usr/lib -Wl,-rpath /usr/lib -lxml2" \ --enable-f77 --enable-fc --enable-cxx --enable-romio \ --enable-debuginfo --enable-smpcoll \ --enable-threads=runtime --with-thread-package=posix \ --enable-shared \ |& tee log.configure.$SYSTEM_ENV.$MACHINE_ENV.32_gcc tyr mpich-3.1.1-SunOS.sparc.32_gcc 419 tail -25 log.make.SunOS.sparc.32_gcc CC src/binding/fortran/mpif_h/lib_libmpifort_la-statusc2f.lo CC src/binding/fortran/use_mpi/lib_libmpifort_la-typef90cmplxf.lo CC src/binding/fortran/use_mpi/lib_libmpifort_la-typef90realf.lo CC src/binding/fortran/use_mpi/lib_libmpifort_la-typef90intf.lo rm -f src/binding/fortran/use_mpi/mpifnoext.h sed -e 's/^C/\!/g' -e '/EXTERNAL/d' \ -e '/REAL\*8/d' \ -e '/DOUBLE PRECISION/d' \ -e '/MPI_WTICK/d' src/binding/fortran/mpif_h/mpif.h > src/binding/fortran/use_mpi/mpifnoext.h MOD src/binding/fortran/use_mpi/mpi_constants.mod-stamp MOD src/binding/fortran/use_mpi/mpi_sizeofs.mod-stamp MOD src/binding/fortran/use_mpi/mpi_base.mod-stamp MOD src/binding/fortran/use_mpi/mpi.mod-stamp GEN lib/libmpifort.la ld: warning: file /export2/prog/SunOS_sparc/gcc-4.9.0/bin/../lib/gcc/sparc-sun-solaris2.10/4.9.0/../../../libgfortran.so: linked to /usr/local/gcc-4.9.0/lib/libgfortran.so: attempted multiple inclusion of file 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.1 collect2: error: ld returned 1 exit status make[2]: *** [lib/libmpicxx.la] Error 1 make[2]: Leaving directory `/export2/src/mpich-3.1.1/mpich-3.1.1-SunOS.sparc.32_gcc' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/export2/src/mpich-3.1.1/mpich-3.1.1-SunOS.sparc.32_gcc' make: *** [all] Error 2 tyr mpich-3.1.1-SunOS.sparc.32_gcc 420 I've had no problems building mpich with "Sun C 5.12" as I already mentioned in a previous email. tyr fd1026 102 mpiexec -info HYDRA build details: Version: 3.1.1 Release Date: Wed Jun 4 15:02:25 CDT 2014 CC: cc -DSunOS -Dsparc -m64 -m64 -L/usr/lib/sparcv9 -R/usr/lib/sparcv9 CXX: CC -DSunOS -Dsparc -m64 -m64 -L/usr/lib/sparcv9 -R/usr/lib/sparcv9 F77: f77 -m64 -m64 -L/usr/lib/sparcv9 -R/usr/lib/sparcv9 F90: f95 -m64 -m64 -L/usr/lib/sparcv9 -R/usr/lib/sparcv9 Configure options: '--disable-option-checking' '--prefix=/usr/local/mpich-3.1.1_64_cc' '--libdir=/usr/local/mpich-3.1.1_64_cc/lib64' '--includedir=/usr/local/mpich-3.1.1_64_cc/include64' 'CC=cc' 'CXX=CC' 'F77=f77' 'FC=f95' 'CFLAGS=-m64 -O2' 'CXXFLAGS=-m64 -O2' 'FFLAGS=-m64 ' 'FCFLAGS=-m64 -O2' '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' 'CPPFLAGS=-DSunOS -Dsparc -I/export2/src/mpich-3.1.1/mpich-3.1.1-SunOS.sparc.64_cc/src/mpl/include -I/export2/src/mpich-3.1.1/mpich-3.1.1/src/mpl/include -I/export2/src/mpich-3.1.1/mpich-3.1.1/src/openpa/src -I/export2/src/mpich-3.1.1/mpich-3.1.1-SunOS.sparc.64_cc/src/openpa/src -I/export2/src/mpich-3.1.1/mpich-3.1.1-SunOS.sparc.64_cc/src/mpi/romio/include' '--cache-file=/dev/null' '--srcdir=../../../../mpich-3.1.1/src/pm/hydra' 'LIBS=-lrt -lnsl -lsocket -lpthread ' Process Manager: pmi Launchers available: ssh rsh fork slurm ll lsf sge manual persist Topology libraries available: hwloc Resource management kernels available: user slurm ll lsf sge pbs cobalt Checkpointing libraries available: Demux engines available: poll select tyr fd1026 103 Kind regards Siegmar > On Jun 25, 2014, at 1:26 AM, Siegmar Gross <Siegmar.Gross(a)informatik.hs-fulda.de> wrote: > > > Solaris uses LD_LIBRARY_PATH for 32-bit libraries/executables and > > LD_LIBRARY_PATH_64 for 64-bit ones. When I build "mpich" as 64-bit > > version, the 32-bit library for "libxml2.so" will be used without > > rpath. I don't know if that is a problem of our gcc-installation > > or your Makefile, but I could solve the problem with rpath.

1 0

Re: [mpich-discuss] couldn't build mpich-3.1.1 on Solaris 10 withgcc-4.9.0
by Lu, Huiwei 25 Jun '14

25 Jun '14

I would suggest build a 64-bit libxml2 instead of using ‘-m64’ for MPICH. — Huiwei On Jun 25, 2014, at 1:26 AM, Siegmar Gross <Siegmar.Gross(a)informatik.hs-fulda.de> wrote: > Solaris uses LD_LIBRARY_PATH for 32-bit libraries/executables and > LD_LIBRARY_PATH_64 for 64-bit ones. When I build "mpich" as 64-bit > version, the 32-bit library for "libxml2.so" will be used without > rpath. I don't know if that is a problem of our gcc-installation > or your Makefile, but I could solve the problem with rpath.

1 0

Re: [mpich-discuss] couldn't build mpich-3.1.1 on Solaris 10 withgcc-4.9.0
by Balaji, Pavan 25 Jun '14

25 Jun '14

Can you try with a simple configure and just CC, CXX, and FC set, and nothing else? If that works, we can try adding back the remaining flags one-by-one to figure out what’s causing a problem. Once we know what’s causing the problem, we can try to reproduce it here. We test on solaris regularly and it seems to work fine for us, so I’m surprised by your error. Regards, — Pavan On Jun 25, 2014, at 1:26 AM, Siegmar Gross <Siegmar.Gross(a)informatik.hs-fulda.de> wrote: > Hi, > >> Before we go digging down this path, did you try simplifying your > > No, because I could built mpich-3.1.1 with "Sun C 5.12" on all > platforms and with "gcc" on Linux with the same options. "make > check" didn't report any failures for mpich, although "make testing" > reported some problems. > > mpich-3.1.1-SunOS.sparc.64_cc: > 60 tests failed out of 825 > mpich-3.1.1-SunOS.x86_64.64_cc: > 32 tests failed out of 825 > mpich-3.1.1-Linux.x86_64.64_cc: > 62 tests failed out of 825 > mpich-3.1.1-Linux.x86_64.64_gcc: > 35 tests failed out of 825 > > Which options shall I use/remove for/from "configure"? > >> ../mpich-3.1.1/configure --prefix=/usr/local/mpich-3.1.1_64_gcc \ >> --libdir=/usr/local/mpich-3.1.1_64_gcc/lib64 \ >> --includedir=/usr/local/mpich-3.1.1_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 \ >> |& tee log.configure.$SYSTEM_ENV.$MACHINE_ENV.64_gcc > > >> Why do you need the rpath settings? > > Solaris uses LD_LIBRARY_PATH for 32-bit libraries/executables and > LD_LIBRARY_PATH_64 for 64-bit ones. When I build "mpich" as 64-bit > version, the 32-bit library for "libxml2.so" will be used without > rpath. I don't know if that is a problem of our gcc-installation > or your Makefile, but I could solve the problem with rpath. > > >> Why is -m64 needed? Are you trying to use a 32-bit compiler on >> a 64-bit machine? > > Yes, and it works as you can see below. I create 32-bit executables > with "-m32" and 64-bit ones with "-m64". > > tyr mpich-3.1.1-SunOS.sparc.64_gcc 33 which gcc > /usr/local/gcc-4.9.0/bin/gcc > tyr mpich-3.1.1-SunOS.sparc.64_gcc 34 file /usr/local/gcc-4.9.0/bin/gcc > /usr/local/gcc-4.9.0/bin/gcc: ELF 32-bit MSB executable SPARC32PLUS > Version 1, V8+ Required, dynamically linked, not stripped > tyr mpich-3.1.1-SunOS.sparc.64_gcc 35 gcc -m32 -o hello_32 hello.c > tyr mpich-3.1.1-SunOS.sparc.64_gcc 36 gcc -m64 -o hello_64 hello.c > tyr mpich-3.1.1-SunOS.sparc.64_gcc 37 file hello_* > hello_32: ELF 32-bit MSB executable SPARC32PLUS Version 1, > V8+ Required, dynamically linked, not stripped, no debugging > information available > hello_64: ELF 64-bit MSB executable SPARCV9 Version 1, > dynamically linked, not stripped, no debugging information > available > tyr mpich-3.1.1-SunOS.sparc.64_gcc 38 hello_32 > Alles klar. > tyr mpich-3.1.1-SunOS.sparc.64_gcc 39 hello_64 > Alles klar. > tyr mpich-3.1.1-SunOS.sparc.64_gcc 40 > > > Thank you very much for your help in advance. > > > Kind regards > > Siegmar > > > >> On Jun 20, 2014, at 8:37 AM, Siegmar Gross > <Siegmar.Gross(a)informatik.hs-fulda.de> wrote: >> >>> Hi, >>> >>> today I tried to install mpich-3.1.1 on my platforms (Solaris 10 >>> sparc, Solaris 10 x86_64, and openSUSE Linux 12.1) with gcc-4.9.0 >>> and Sun C 5.12. Unfortunately I couldn't build it with gcc-4.9.0 on >>> my Solaris platforms (everything else succeeded). >>> >>> tyr mpich-3.1.1 110 grep Error mpich-3.1.1-SunOS.x86_64.64_cc/log.make.* >>> tyr mpich-3.1.1 111 grep Error mpich-3.1.1-SunOS.x86_64.64_gcc/log.make.* >>> make[2]: *** [lib/libmpicxx.la] Error 1 >>> make[1]: *** [all-recursive] Error 1 >>> make: *** [all] Error 2 >>> tyr mpich-3.1.1 112 >>> tyr mpich-3.1.1 112 grep Error mpich-3.1.1-SunOS.sparc.64_cc/log.make.* >>> tyr mpich-3.1.1 113 grep Error mpich-3.1.1-SunOS.sparc.64_gcc/log.make.* >>> make[2]: *** [lib/libmpicxx.la] Error 1 >>> make[1]: *** [all-recursive] Error 1 >>> make: *** [all] Error 2 >>> tyr mpich-3.1.1 114 >>> >>> tyr mpich-3.1.1 123 tail mpich-3.1.1-SunOS.x86_64.64_gcc/log.make.* >>> 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.1 >>> collect2: error: ld returned 1 exit status >>> make[2]: *** [lib/libmpicxx.la] Error 1 >>> make[2]: Leaving directory >>> `/export2/src/mpich-3.1.1/mpich-3.1.1-SunOS.x86_64.64_gcc' >>> make[1]: *** [all-recursive] Error 1 >>> make[1]: Leaving directory >>> `/export2/src/mpich-3.1.1/mpich-3.1.1-SunOS.x86_64.64_gcc' >>> make: *** [all] Error 2 >>> tyr mpich-3.1.1 124 >>> >>> >>> I used the following command to configure the system. "ld" reports >>> an error for "libxml2.so" without "/usr/lib/sparcv9" in LDFLAGS >>> (wrong ELF class). The command is similar for Solaris 10 x86_64. >>> Solaris uses LD_LIBRARY_PATH_64 to find 64-bit libraries and >>> LD_LIBRARY_PATH for 32-bit ones. Perhaps that's the reason why I >>> had to add the directories to LDFLAGS. >>> >>> ../mpich-3.1.1/configure --prefix=/usr/local/mpich-3.1.1_64_gcc \ >>> --libdir=/usr/local/mpich-3.1.1_64_gcc/lib64 \ >>> --includedir=/usr/local/mpich-3.1.1_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 \ >>> |& tee log.configure.$SYSTEM_ENV.$MACHINE_ENV.64_gcc >>> >>> >>> I would be grateful if somebody can provide a solution for my >>> problem. I have attached some config.log files. Do you need >>> anything else? >>> >>> >>> Kind regards >>> >>> Siegmar >>> > <mpich-3.1.1-SunOS.sparc.64_gcc.tar.gz>_________________________________________ > ______ >>> 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] couldn't build mpich-3.1.1 on Solaris 10 withgcc-4.9.0
by Siegmar Gross 25 Jun '14

25 Jun '14

Hi, > Before we go digging down this path, did you try simplifying your No, because I could built mpich-3.1.1 with "Sun C 5.12" on all platforms and with "gcc" on Linux with the same options. "make check" didn't report any failures for mpich, although "make testing" reported some problems. mpich-3.1.1-SunOS.sparc.64_cc: 60 tests failed out of 825 mpich-3.1.1-SunOS.x86_64.64_cc: 32 tests failed out of 825 mpich-3.1.1-Linux.x86_64.64_cc: 62 tests failed out of 825 mpich-3.1.1-Linux.x86_64.64_gcc: 35 tests failed out of 825 Which options shall I use/remove for/from "configure"? > ../mpich-3.1.1/configure --prefix=/usr/local/mpich-3.1.1_64_gcc \ > --libdir=/usr/local/mpich-3.1.1_64_gcc/lib64 \ > --includedir=/usr/local/mpich-3.1.1_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 \ > |& tee log.configure.$SYSTEM_ENV.$MACHINE_ENV.64_gcc > Why do you need the rpath settings? Solaris uses LD_LIBRARY_PATH for 32-bit libraries/executables and LD_LIBRARY_PATH_64 for 64-bit ones. When I build "mpich" as 64-bit version, the 32-bit library for "libxml2.so" will be used without rpath. I don't know if that is a problem of our gcc-installation or your Makefile, but I could solve the problem with rpath. > Why is -m64 needed? Are you trying to use a 32-bit compiler on > a 64-bit machine? Yes, and it works as you can see below. I create 32-bit executables with "-m32" and 64-bit ones with "-m64". tyr mpich-3.1.1-SunOS.sparc.64_gcc 33 which gcc /usr/local/gcc-4.9.0/bin/gcc tyr mpich-3.1.1-SunOS.sparc.64_gcc 34 file /usr/local/gcc-4.9.0/bin/gcc /usr/local/gcc-4.9.0/bin/gcc: ELF 32-bit MSB executable SPARC32PLUS Version 1, V8+ Required, dynamically linked, not stripped tyr mpich-3.1.1-SunOS.sparc.64_gcc 35 gcc -m32 -o hello_32 hello.c tyr mpich-3.1.1-SunOS.sparc.64_gcc 36 gcc -m64 -o hello_64 hello.c tyr mpich-3.1.1-SunOS.sparc.64_gcc 37 file hello_* hello_32: ELF 32-bit MSB executable SPARC32PLUS Version 1, V8+ Required, dynamically linked, not stripped, no debugging information available hello_64: ELF 64-bit MSB executable SPARCV9 Version 1, dynamically linked, not stripped, no debugging information available tyr mpich-3.1.1-SunOS.sparc.64_gcc 38 hello_32 Alles klar. tyr mpich-3.1.1-SunOS.sparc.64_gcc 39 hello_64 Alles klar. tyr mpich-3.1.1-SunOS.sparc.64_gcc 40 Thank you very much for your help in advance. Kind regards Siegmar > On Jun 20, 2014, at 8:37 AM, Siegmar Gross <Siegmar.Gross(a)informatik.hs-fulda.de> wrote: > > > Hi, > > > > today I tried to install mpich-3.1.1 on my platforms (Solaris 10 > > sparc, Solaris 10 x86_64, and openSUSE Linux 12.1) with gcc-4.9.0 > > and Sun C 5.12. Unfortunately I couldn't build it with gcc-4.9.0 on > > my Solaris platforms (everything else succeeded). > > > > tyr mpich-3.1.1 110 grep Error mpich-3.1.1-SunOS.x86_64.64_cc/log.make.* > > tyr mpich-3.1.1 111 grep Error mpich-3.1.1-SunOS.x86_64.64_gcc/log.make.* > > make[2]: *** [lib/libmpicxx.la] Error 1 > > make[1]: *** [all-recursive] Error 1 > > make: *** [all] Error 2 > > tyr mpich-3.1.1 112 > > tyr mpich-3.1.1 112 grep Error mpich-3.1.1-SunOS.sparc.64_cc/log.make.* > > tyr mpich-3.1.1 113 grep Error mpich-3.1.1-SunOS.sparc.64_gcc/log.make.* > > make[2]: *** [lib/libmpicxx.la] Error 1 > > make[1]: *** [all-recursive] Error 1 > > make: *** [all] Error 2 > > tyr mpich-3.1.1 114 > > > > tyr mpich-3.1.1 123 tail mpich-3.1.1-SunOS.x86_64.64_gcc/log.make.* > > 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.1 > > collect2: error: ld returned 1 exit status > > make[2]: *** [lib/libmpicxx.la] Error 1 > > make[2]: Leaving directory > > `/export2/src/mpich-3.1.1/mpich-3.1.1-SunOS.x86_64.64_gcc' > > make[1]: *** [all-recursive] Error 1 > > make[1]: Leaving directory > > `/export2/src/mpich-3.1.1/mpich-3.1.1-SunOS.x86_64.64_gcc' > > make: *** [all] Error 2 > > tyr mpich-3.1.1 124 > > > > > > I used the following command to configure the system. "ld" reports > > an error for "libxml2.so" without "/usr/lib/sparcv9" in LDFLAGS > > (wrong ELF class). The command is similar for Solaris 10 x86_64. > > Solaris uses LD_LIBRARY_PATH_64 to find 64-bit libraries and > > LD_LIBRARY_PATH for 32-bit ones. Perhaps that's the reason why I > > had to add the directories to LDFLAGS. > > > > ../mpich-3.1.1/configure --prefix=/usr/local/mpich-3.1.1_64_gcc \ > > --libdir=/usr/local/mpich-3.1.1_64_gcc/lib64 \ > > --includedir=/usr/local/mpich-3.1.1_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 \ > > |& tee log.configure.$SYSTEM_ENV.$MACHINE_ENV.64_gcc > > > > > > I would be grateful if somebody can provide a solution for my > > problem. I have attached some config.log files. Do you need > > anything else? > > > > > > Kind regards > > > > Siegmar > > <mpich-3.1.1-SunOS.sparc.64_gcc.tar.gz>_________________________________________ ______ > > 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.1 building error when enabling per-object critical sections
by Balaji, Pavan 24 Jun '14

24 Jun '14

Correct. The per-object code was experimental and for research purposes (we only implemented it in ch3:sock and never fully ported it to ch3:nemesis). Later IBM picked it up for their pamid device, where it is well supported. — Pavan On Jun 24, 2014, at 11:31 PM, Lu, Huiwei <huiweilu(a)mcs.anl.gov> wrote: > I can reproduce your bug on my Linux desktop with GCC, too. > I guess the ‘per-object’ option is not well supported. We may need to create a new ticket for this issue. > > — > Huiwei > > On Jun 24, 2014, at 11:21 PM, Halim <halim.amer(a)gmail.com> wrote: > >> Hi, >> >> I am facing an error when building MPICH 3.1.1 release with per-object critical sections enabled. >> >> I am getting the following errors related to multiple definition of "MPIU_Thread_CS_enter_lockname_impl_" : >> >> ..... >> GEN lib/libmpi.la >> src/mpi/attr/.libs/lib_libmpi_la-comm_delete_attr.o: In function `MPIU_Thread_CS_enter_lockname_impl_': >> src/mpi/attr/comm_delete_attr.c:(.text+0x530): multiple definition of `MPIU_Thread_CS_enter_lockname_impl_' >> src/mpi/attr/.libs/lib_libmpi_la-comm_create_keyval.o:src/mpi/attr/comm_create_keyval.c:(.text+0x290): first defined here >> src/mpi/attr/.libs/lib_libmpi_la-comm_delete_attr.o: In function `MPIU_Thread_CS_exit_lockname_impl_': >> src/mpi/attr/comm_delete_attr.c:(.text+0x570): multiple definition of `MPIU_Thread_CS_exit_lockname_impl_' >> src/mpi/attr/.libs/lib_libmpi_la-comm_create_keyval.o:src/mpi/attr/comm_create_keyval.c:(.text+0x2d0): first defined here >> ..... >> >> This is the configure line: >> ./configure --disable-fortran --disable-cxx --enable-thread-cs=per-object >> >> I am testing on x86_64 linux desktop with Intel compilers and device/channel: ch3/nemesis. >> >> Is there a quick fix to this issue? >> >> Regards, >> Halim >> >> >> _______________________________________________ >> 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] MPICH 3.1.1 building error when enabling per-object critical sections
by Lu, Huiwei 24 Jun '14

24 Jun '14

I can reproduce your bug on my Linux desktop with GCC, too. I guess the ‘per-object’ option is not well supported. We may need to create a new ticket for this issue. — Huiwei On Jun 24, 2014, at 11:21 PM, Halim <halim.amer(a)gmail.com> wrote: > Hi, > > I am facing an error when building MPICH 3.1.1 release with per-object critical sections enabled. > > I am getting the following errors related to multiple definition of "MPIU_Thread_CS_enter_lockname_impl_" : > > ..... > GEN lib/libmpi.la > src/mpi/attr/.libs/lib_libmpi_la-comm_delete_attr.o: In function `MPIU_Thread_CS_enter_lockname_impl_': > src/mpi/attr/comm_delete_attr.c:(.text+0x530): multiple definition of `MPIU_Thread_CS_enter_lockname_impl_' > src/mpi/attr/.libs/lib_libmpi_la-comm_create_keyval.o:src/mpi/attr/comm_create_keyval.c:(.text+0x290): first defined here > src/mpi/attr/.libs/lib_libmpi_la-comm_delete_attr.o: In function `MPIU_Thread_CS_exit_lockname_impl_': > src/mpi/attr/comm_delete_attr.c:(.text+0x570): multiple definition of `MPIU_Thread_CS_exit_lockname_impl_' > src/mpi/attr/.libs/lib_libmpi_la-comm_create_keyval.o:src/mpi/attr/comm_create_keyval.c:(.text+0x2d0): first defined here > ..... > > This is the configure line: > ./configure --disable-fortran --disable-cxx --enable-thread-cs=per-object > > I am testing on x86_64 linux desktop with Intel compilers and device/channel: ch3/nemesis. > > Is there a quick fix to this issue? > > Regards, > Halim > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss

1 0

MPICH 3.1.1 building error when enabling per-object critical sections
by Halim 24 Jun '14

24 Jun '14

Hi, I am facing an error when building MPICH 3.1.1 release with per-object critical sections enabled. I am getting the following errors related to multiple definition of "MPIU_Thread_CS_enter_lockname_impl_" : ..... GEN lib/libmpi.la src/mpi/attr/.libs/lib_libmpi_la-comm_delete_attr.o: In function `MPIU_Thread_CS_enter_lockname_impl_': src/mpi/attr/comm_delete_attr.c:(.text+0x530): multiple definition of `MPIU_Thread_CS_enter_lockname_impl_' src/mpi/attr/.libs/lib_libmpi_la-comm_create_keyval.o:src/mpi/attr/comm_create_keyval.c:(.text+0x290): first defined here src/mpi/attr/.libs/lib_libmpi_la-comm_delete_attr.o: In function `MPIU_Thread_CS_exit_lockname_impl_': src/mpi/attr/comm_delete_attr.c:(.text+0x570): multiple definition of `MPIU_Thread_CS_exit_lockname_impl_' src/mpi/attr/.libs/lib_libmpi_la-comm_create_keyval.o:src/mpi/attr/comm_create_keyval.c:(.text+0x2d0): first defined here ..... This is the configure line: ./configure --disable-fortran --disable-cxx --enable-thread-cs=per-object I am testing on x86_64 linux desktop with Intel compilers and device/channel: ch3/nemesis. Is there a quick fix to this issue? Regards, Halim

1 0