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

Re: [mpich-discuss] Adding libraries to the mpicc wrapper
by Rob Latham 15 Jan '14

15 Jan '14

On 01/15/2014 08:55 AM, Matthieu Dorier wrote: > Hello, > > I have written an ADIO backend that depends on a library. So far to make > the use of the library transparent when compiling a program, I added the > library at line 226 of the mpicc wrapper (mpilibs=" -lmpich > -lmylibrary"). I'd like to know if there is a "cleaner" way of adding > it: mpicc being generated from a template, there should be a way to > simply set a variable somewhere for that, shouldn't it? How is it done > for other ADIO backends? Hey Mattieu! for old pvfs and lustre, add to LDFLAGS and LIBS when configuring mpich (and in turn, romio) for pvfs2, ROMIO's configure looked for and used pvfs2-config to add the appropriate libraries and headers. ROMIO would then add those to 'src/mpi/romio/localdefs' so the needed libraries would propagate up to the mpicc wrapper. ==rob -- Rob Latham Mathematics and Computer Science Division Argonne National Lab, IL USA

1 0

Re: [mpich-discuss] Adding libraries to the mpicc wrapper
by Matthieu Dorier 15 Jan '14

15 Jan '14

Since the library is called by Mpich itself, I want to end up with: gcc ... -lmpich -lmylibrary otherwise mpich will complain that it doesn't find the symbols. Matthieu Dorier PhD student at ENS Rennes http://people.irisa.fr/Matthieu.Dorier ----- Mail original ----- > De: "Pavan Balaji" <balaji(a)mcs.anl.gov> > À: discuss(a)mpich.org > Envoyé: Mercredi 15 Janvier 2014 17:07:49 > Objet: Re: [mpich-discuss] Adding libraries to the mpicc wrapper > > > User libraries are prioritized over MPICH and other libraries when > passed to mpicc. > > So mpicc foo.c -lmylibrary will result in: > > gcc foo.c -lmylibrary -lmpich > > Is that what you want to do? If then, I’d recommend Jeff’s approach > of creating a wrapper mpicc.new script that internally calls mpicc. > > — Pavan > > On Jan 15, 2014, at 8:55 AM, Matthieu Dorier > <matthieu.dorier(a)irisa.fr> wrote: > > > Hello, > > > > I have written an ADIO backend that depends on a library. So far to > > make the use of the library transparent when compiling a program, > > I added the library at line 226 of the mpicc wrapper (mpilibs=" > > -lmpich -lmylibrary"). I'd like to know if there is a "cleaner" > > way of adding it: mpicc being generated from a template, there > > should be a way to simply set a variable somewhere for that, > > shouldn't it? How is it done for other ADIO backends? > > > > Thank you, > > > > Matthieu Dorier > > PhD student at ENS Rennes > > http://people.irisa.fr/Matthieu.Dorier > > _______________________________________________ > > 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] Adding libraries to the mpicc wrapper
by Balaji, Pavan 15 Jan '14

15 Jan '14

User libraries are prioritized over MPICH and other libraries when passed to mpicc. So mpicc foo.c -lmylibrary will result in: gcc foo.c -lmylibrary -lmpich Is that what you want to do? If then, I’d recommend Jeff’s approach of creating a wrapper mpicc.new script that internally calls mpicc. — Pavan On Jan 15, 2014, at 8:55 AM, Matthieu Dorier <matthieu.dorier(a)irisa.fr> wrote: > Hello, > > I have written an ADIO backend that depends on a library. So far to make the use of the library transparent when compiling a program, I added the library at line 226 of the mpicc wrapper (mpilibs=" -lmpich -lmylibrary"). I'd like to know if there is a "cleaner" way of adding it: mpicc being generated from a template, there should be a way to simply set a variable somewhere for that, shouldn't it? How is it done for other ADIO backends? > > Thank you, > > Matthieu Dorier > PhD student at ENS Rennes > http://people.irisa.fr/Matthieu.Dorier > _______________________________________________ > 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] Adding libraries to the mpicc wrapper
by Jeff Hammond 15 Jan '14

15 Jan '14

My attempts to add libraries to the right of the MPICH libs via mpicc env vars proved unsuccessful. Perhaps I am just stupid though. The good news is that you can just something like alias mympicc="`mpicc -show` -L$YOUR_LIB_DIR -lyour" and use mympicc like you would mpicc. Jeff On Wed, Jan 15, 2014 at 8:55 AM, Matthieu Dorier <matthieu.dorier(a)irisa.fr> wrote: > Hello, > > I have written an ADIO backend that depends on a library. So far to make the > use of the library transparent when compiling a program, I added the library > at line 226 of the mpicc wrapper (mpilibs=" -lmpich -lmylibrary"). I'd like > to know if there is a "cleaner" way of adding it: mpicc being generated from > a template, there should be a way to simply set a variable somewhere for > that, shouldn't it? How is it done for other ADIO backends? > > Thank you, > > Matthieu Dorier > PhD student at ENS Rennes > http://people.irisa.fr/Matthieu.Dorier > > _______________________________________________ > 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

1 0

Re: [mpich-discuss] MPICH 3.1rc2 build error on Darwin.
by Salmon, Rene 15 Jan '14

15 Jan '14

Just reporting that this is indeed fixed with the latest git or snapshot. Thank you Rene -----Original Message----- From: discuss-bounces(a)mpich.org on behalf of Pavan Balaji Sent: Mon 1/13/2014 10:28 PM To: discuss(a)mpich.org Subject: Re: [mpich-discuss] MPICH 3.1rc2 build error on Darwin. Or from a nightly snapshot: http://www.mpich.org/static/tarballs/nightly/master/mpich/ - Pavan On Jan 13, 2014, at 10:26 PM, Kenneth Raffenetti <raffenet(a)mcs.anl.gov> wrote: > There should already be a fix for this in the latest master branch in git. It will be included in rc3, but you can try building from git if you'd like. > > Ken > > On 01/13/2014 10:12 PM, Salmon, Rene wrote: >> >> Thanks for the replies. Here is a bit more info. I tried this with both mpich 3.1rc2 and mpich 3.0.4 >> >> mpich 3.1rc2 >> ============ >> This seems to compile with out any error messages using gcc. >> ./configure CC=gcc CXX=g++ F77=gfortran FC=gfortran --prefix=/opt/ilocal/ --enable-fc >> make >> >> mpich 3.1rc2 >> ========= >> This fails. I have the output of make V=1 at the end of this email. >> ./configure CC=icc CXX=icpc F77=ifort FC=ifort --prefix=/opt/ilocal/ --enable-fc >> make >> >> >> mpich 3.0.4 >> =========== >> This seems to work with mpich 3.0.4. No error messages. >> ./configure CC=icc CXX=icpc F77=ifort FC=ifort --prefix=/opt/ilocal/ --enable-fc >> make >> >> >> >> Here is the output to make V=1 for mpich 3.2rc2 using intel compilers. >> ================================ >> >> In file included from ../src/include/mpi.h(2145), >> from cpi.c(7): >> ../src/include/mpio.h(227): warning #1787: alias definitions not supported on this platform; attribute ignored >> int MPI_File_get_atomicity(MPI_File fh, int *flag) MPICH_ATTR_WEAK_ALIAS("PMPI_File_get_atomicity"); >> ^ >> >> In file included from ../src/include/mpi.h(2145), >> from cpi.c(7): >> ../src/include/mpio.h(228): warning #1787: alias definitions not supported on this platform; attribute ignored >> int MPI_File_sync(MPI_File fh) MPICH_ATTR_WEAK_ALIAS("PMPI_File_sync"); >> ^ >> >> In file included from ../src/include/mpi.h(2145), >> from cpi.c(7): >> ../src/include/mpio.h(264): warning #1787: alias definitions not supported on this platform; attribute ignored >> MPI_File MPI_File_f2c(MPI_Fint file) MPICH_ATTR_WEAK_ALIAS("PMPI_File_f2c"); >> ^ >> >> In file included from ../src/include/mpi.h(2145), >> from cpi.c(7): >> ../src/include/mpio.h(265): warning #1787: alias definitions not supported on this platform; attribute ignored >> MPI_Fint MPI_File_c2f(MPI_File file) MPICH_ATTR_WEAK_ALIAS("PMPI_File_c2f"); >> ^ >> >> /bin/sh ../libtool --tag=CC --mode=link icc -O2 -L../lib -L/opt/ilocal/src/mpich-3.1rc2/src/mpl -L/opt/ilocal/src/mpich-3.1rc2/src/openpa/src -Wl,-flat_namespace -static -Wl,-flat_namespace -o cpi cpi.o -lm -lpthread -lmpich -lmpl -lopa -lopa -lmpl -lpthread >> libtool: link: icc -O2 -Wl,-flat_namespace -Wl,-flat_namespace -o cpi cpi.o -L../lib -L/opt/ilocal/src/mpich-3.1rc2/src/mpl -L/opt/ilocal/src/mpich-3.1rc2/src/openpa/src -lm /opt/ilocal/src/mpich-3.1rc2/lib/.libs/libmpich.a /opt/ilocal/src/mpich-3.1rc2/src/openpa/src/.libs/libopa.a /opt/ilocal/src/mpich-3.1rc2/src/mpl/.libs/libmpl.a -lpthread >> Undefined symbols for architecture x86_64: >> "_MPI_Bcast", referenced from: >> _main in cpi.o >> "_MPI_Comm_rank", referenced from: >> _main in cpi.o >> "_MPI_Comm_size", referenced from: >> _main in cpi.o >> "_MPI_Finalize", referenced from: >> _main in cpi.o >> "_MPI_Get_processor_name", referenced from: >> _main in cpi.o >> "_MPI_Init", referenced from: >> _main in cpi.o >> "_MPI_Reduce", referenced from: >> _main in cpi.o >> "_MPI_Wtime", referenced from: >> _main in cpi.o >> ld: symbol(s) not found for architecture x86_64 >> make[2]: *** [cpi] Error 1 >> make[1]: *** [all-recursive] Error 1 >> make: *** [all] Error 2 >> >> >> >> >> >> >> >> -----Original Message----- >> From: discuss-bounces(a)mpich.org on behalf of Eric A. Borisch >> Sent: Mon 1/13/2014 12:39 AM >> To: discuss(a)mpich.org >> Subject: [mpich-discuss] MPICH 3.1rc2 build error on Darwin. >> >> He's building with icc/ifort, so it's not being done via MacPorts. I don't think he even needs MP or Homebrew installed to build MPICH, just Intel's tools (and Xcode). >> >> Building with 'make V=1' (or configuring with --disable-silent-rules) will provide more insight into what is going on. If you do have MP or Homebrew installed, you can rule out most interaction by removing their locations (/opt/local/bin, or /usr/local/bin, respectively) from PATH. >> >> Jeff, I'm sorry to year you were unhappy with the (MP) tools. FWIW, it's been reworked to have a standardized MPICH version (with GCC's Fortan and the system's default C compiler) that is installed for use by any (macports-built) package that needs it. >> >> Thanks, >> - Eric >> >> On Sunday, January 12, 2014, Jeff Hammond wrote: >> >> >> Might be the MacPorts garbage that bit me a while back too. If GCC fails, I suggest wiping MacPorts and installing Homebrew and the associated toolchain. >> >> Jeff >> >> Sent from my iPhone >> >> > On Jan 12, 2014, at 7:58 PM, Rajeev Thakur <thakur(a)mcs.anl.gov> wrote: >> > >> > It sounds like a 32-bit, 64-bit incompatibility between some installed compilers/linker. Are you able to build with gcc? >> > >> > >> >> On Jan 10, 2014, at 3:09 PM, "Salmon, Rene" <salmr0(a)bp.com> wrote: >> >> >> >> >> >> Hi, >> >> >> >> Just trying to build MPICH 3.1rc2 on a Mac. The build seems to work but fails while trying to compile the examples. This is using the intel compilers. >> >> >> >> ifort,icc version 14.0.0.074 >> >> >> >> Here is the config line. >> >> ./configure CC=icc CXX=icpc F77=ifort FC=ifort --enable-fc >> >> >> >> >> >> error message. >> >> >> >> make[4]: Nothing to be done for `all'. >> >> make[4]: Nothing to be done for `all-am'. >> >> Making all in . >> >> Making all in . >> >> Making all in examples >> >> CCLD cpi >> >> Undefined symbols for architecture x86_64: >> >> "_MPI_Bcast", referenced from: >> >> _main in cpi.o >> >> "_MPI_Comm_rank", referenced from: >> >> _main in cpi.o >> >> "_MPI_Comm_size", referenced from: >> >> _main in cpi.o >> >> "_MPI_Finalize", referenced from: >> >> _main in cpi.o >> >> "_MPI_Get_processor_name", referenced from: >> >> _main in cpi.o >> >> "_MPI_Init", referenced from: >> >> _main in cpi.o >> >> "_MPI_Reduce", referenced from: >> >> _main in cpi.o >> >> "_MPI_Wtime", referenced from: >> >> _main in cpi.o >> >> ld: symbol(s) not found for architecture x86_64 >> >> make[2]: *** [cpi] Error 1 >> >> make[1]: *** [all-recursive] Error 1 >> >> make: *** [all] Error 2 >> >> >> >> Thank you. >> >> >> >> Rene >> >> _______________________________________________ >> >> 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 -- Pavan Balaji http://www.mcs.anl.gov/~balaji _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Adding libraries to the mpicc wrapper
by Matthieu Dorier 15 Jan '14

15 Jan '14

Hello, I have written an ADIO backend that depends on a library. So far to make the use of the library transparent when compiling a program, I added the library at line 226 of the mpicc wrapper (mpilibs=" -lmpich -lmylibrary"). I'd like to know if there is a "cleaner" way of adding it: mpicc being generated from a template, there should be a way to simply set a variable somewhere for that, shouldn't it? How is it done for other ADIO backends? Thank you, Matthieu Dorier PhD student at ENS Rennes http://people.irisa.fr/Matthieu.Dorier

1 0

Re: [mpich-discuss] MPICH 3.1rc2 build error on Darwin.
by Pavan Balaji 13 Jan '14

13 Jan '14

Or from a nightly snapshot: http://www.mpich.org/static/tarballs/nightly/master/mpich/ — Pavan On Jan 13, 2014, at 10:26 PM, Kenneth Raffenetti <raffenet(a)mcs.anl.gov> wrote: > There should already be a fix for this in the latest master branch in git. It will be included in rc3, but you can try building from git if you'd like. > > Ken > > On 01/13/2014 10:12 PM, Salmon, Rene wrote: >> >> Thanks for the replies. Here is a bit more info. I tried this with both mpich 3.1rc2 and mpich 3.0.4 >> >> mpich 3.1rc2 >> ============ >> This seems to compile with out any error messages using gcc. >> ./configure CC=gcc CXX=g++ F77=gfortran FC=gfortran --prefix=/opt/ilocal/ --enable-fc >> make >> >> mpich 3.1rc2 >> ========= >> This fails. I have the output of make V=1 at the end of this email. >> ./configure CC=icc CXX=icpc F77=ifort FC=ifort --prefix=/opt/ilocal/ --enable-fc >> make >> >> >> mpich 3.0.4 >> =========== >> This seems to work with mpich 3.0.4. No error messages. >> ./configure CC=icc CXX=icpc F77=ifort FC=ifort --prefix=/opt/ilocal/ --enable-fc >> make >> >> >> >> Here is the output to make V=1 for mpich 3.2rc2 using intel compilers. >> ================================ >> >> In file included from ../src/include/mpi.h(2145), >> from cpi.c(7): >> ../src/include/mpio.h(227): warning #1787: alias definitions not supported on this platform; attribute ignored >> int MPI_File_get_atomicity(MPI_File fh, int *flag) MPICH_ATTR_WEAK_ALIAS("PMPI_File_get_atomicity"); >> ^ >> >> In file included from ../src/include/mpi.h(2145), >> from cpi.c(7): >> ../src/include/mpio.h(228): warning #1787: alias definitions not supported on this platform; attribute ignored >> int MPI_File_sync(MPI_File fh) MPICH_ATTR_WEAK_ALIAS("PMPI_File_sync"); >> ^ >> >> In file included from ../src/include/mpi.h(2145), >> from cpi.c(7): >> ../src/include/mpio.h(264): warning #1787: alias definitions not supported on this platform; attribute ignored >> MPI_File MPI_File_f2c(MPI_Fint file) MPICH_ATTR_WEAK_ALIAS("PMPI_File_f2c"); >> ^ >> >> In file included from ../src/include/mpi.h(2145), >> from cpi.c(7): >> ../src/include/mpio.h(265): warning #1787: alias definitions not supported on this platform; attribute ignored >> MPI_Fint MPI_File_c2f(MPI_File file) MPICH_ATTR_WEAK_ALIAS("PMPI_File_c2f"); >> ^ >> >> /bin/sh ../libtool --tag=CC --mode=link icc -O2 -L../lib -L/opt/ilocal/src/mpich-3.1rc2/src/mpl -L/opt/ilocal/src/mpich-3.1rc2/src/openpa/src -Wl,-flat_namespace -static -Wl,-flat_namespace -o cpi cpi.o -lm -lpthread -lmpich -lmpl -lopa -lopa -lmpl -lpthread >> libtool: link: icc -O2 -Wl,-flat_namespace -Wl,-flat_namespace -o cpi cpi.o -L../lib -L/opt/ilocal/src/mpich-3.1rc2/src/mpl -L/opt/ilocal/src/mpich-3.1rc2/src/openpa/src -lm /opt/ilocal/src/mpich-3.1rc2/lib/.libs/libmpich.a /opt/ilocal/src/mpich-3.1rc2/src/openpa/src/.libs/libopa.a /opt/ilocal/src/mpich-3.1rc2/src/mpl/.libs/libmpl.a -lpthread >> Undefined symbols for architecture x86_64: >> "_MPI_Bcast", referenced from: >> _main in cpi.o >> "_MPI_Comm_rank", referenced from: >> _main in cpi.o >> "_MPI_Comm_size", referenced from: >> _main in cpi.o >> "_MPI_Finalize", referenced from: >> _main in cpi.o >> "_MPI_Get_processor_name", referenced from: >> _main in cpi.o >> "_MPI_Init", referenced from: >> _main in cpi.o >> "_MPI_Reduce", referenced from: >> _main in cpi.o >> "_MPI_Wtime", referenced from: >> _main in cpi.o >> ld: symbol(s) not found for architecture x86_64 >> make[2]: *** [cpi] Error 1 >> make[1]: *** [all-recursive] Error 1 >> make: *** [all] Error 2 >> >> >> >> >> >> >> >> -----Original Message----- >> From: discuss-bounces(a)mpich.org on behalf of Eric A. Borisch >> Sent: Mon 1/13/2014 12:39 AM >> To: discuss(a)mpich.org >> Subject: [mpich-discuss] MPICH 3.1rc2 build error on Darwin. >> >> He's building with icc/ifort, so it's not being done via MacPorts. I don't think he even needs MP or Homebrew installed to build MPICH, just Intel's tools (and Xcode). >> >> Building with 'make V=1' (or configuring with --disable-silent-rules) will provide more insight into what is going on. If you do have MP or Homebrew installed, you can rule out most interaction by removing their locations (/opt/local/bin, or /usr/local/bin, respectively) from PATH. >> >> Jeff, I'm sorry to year you were unhappy with the (MP) tools. FWIW, it's been reworked to have a standardized MPICH version (with GCC's Fortan and the system's default C compiler) that is installed for use by any (macports-built) package that needs it. >> >> Thanks, >> - Eric >> >> On Sunday, January 12, 2014, Jeff Hammond wrote: >> >> >> Might be the MacPorts garbage that bit me a while back too. If GCC fails, I suggest wiping MacPorts and installing Homebrew and the associated toolchain. >> >> Jeff >> >> Sent from my iPhone >> >> > On Jan 12, 2014, at 7:58 PM, Rajeev Thakur <thakur(a)mcs.anl.gov> wrote: >> > >> > It sounds like a 32-bit, 64-bit incompatibility between some installed compilers/linker. Are you able to build with gcc? >> > >> > >> >> On Jan 10, 2014, at 3:09 PM, "Salmon, Rene" <salmr0(a)bp.com> wrote: >> >> >> >> >> >> Hi, >> >> >> >> Just trying to build MPICH 3.1rc2 on a Mac. The build seems to work but fails while trying to compile the examples. This is using the intel compilers. >> >> >> >> ifort,icc version 14.0.0.074 >> >> >> >> Here is the config line. >> >> ./configure CC=icc CXX=icpc F77=ifort FC=ifort --enable-fc >> >> >> >> >> >> error message. >> >> >> >> make[4]: Nothing to be done for `all'. >> >> make[4]: Nothing to be done for `all-am'. >> >> Making all in . >> >> Making all in . >> >> Making all in examples >> >> CCLD cpi >> >> Undefined symbols for architecture x86_64: >> >> "_MPI_Bcast", referenced from: >> >> _main in cpi.o >> >> "_MPI_Comm_rank", referenced from: >> >> _main in cpi.o >> >> "_MPI_Comm_size", referenced from: >> >> _main in cpi.o >> >> "_MPI_Finalize", referenced from: >> >> _main in cpi.o >> >> "_MPI_Get_processor_name", referenced from: >> >> _main in cpi.o >> >> "_MPI_Init", referenced from: >> >> _main in cpi.o >> >> "_MPI_Reduce", referenced from: >> >> _main in cpi.o >> >> "_MPI_Wtime", referenced from: >> >> _main in cpi.o >> >> ld: symbol(s) not found for architecture x86_64 >> >> make[2]: *** [cpi] Error 1 >> >> make[1]: *** [all-recursive] Error 1 >> >> make: *** [all] Error 2 >> >> >> >> Thank you. >> >> >> >> Rene >> >> _______________________________________________ >> >> 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 -- Pavan Balaji http://www.mcs.anl.gov/~balaji

1 0

Re: [mpich-discuss] MPICH 3.1rc2 build error on Darwin.
by Kenneth Raffenetti 13 Jan '14

13 Jan '14

There should already be a fix for this in the latest master branch in git. It will be included in rc3, but you can try building from git if you'd like. Ken On 01/13/2014 10:12 PM, Salmon, Rene wrote: > > Thanks for the replies. Here is a bit more info. I tried this with both mpich 3.1rc2 and mpich 3.0.4 > > mpich 3.1rc2 > ============ > This seems to compile with out any error messages using gcc. > ./configure CC=gcc CXX=g++ F77=gfortran FC=gfortran --prefix=/opt/ilocal/ --enable-fc > make > > mpich 3.1rc2 > ========= > This fails. I have the output of make V=1 at the end of this email. > ./configure CC=icc CXX=icpc F77=ifort FC=ifort --prefix=/opt/ilocal/ --enable-fc > make > > > mpich 3.0.4 > =========== > This seems to work with mpich 3.0.4. No error messages. > ./configure CC=icc CXX=icpc F77=ifort FC=ifort --prefix=/opt/ilocal/ --enable-fc > make > > > > Here is the output to make V=1 for mpich 3.2rc2 using intel compilers. > ================================ > > In file included from ../src/include/mpi.h(2145), > from cpi.c(7): > ../src/include/mpio.h(227): warning #1787: alias definitions not supported on this platform; attribute ignored > int MPI_File_get_atomicity(MPI_File fh, int *flag) MPICH_ATTR_WEAK_ALIAS("PMPI_File_get_atomicity"); > ^ > > In file included from ../src/include/mpi.h(2145), > from cpi.c(7): > ../src/include/mpio.h(228): warning #1787: alias definitions not supported on this platform; attribute ignored > int MPI_File_sync(MPI_File fh) MPICH_ATTR_WEAK_ALIAS("PMPI_File_sync"); > ^ > > In file included from ../src/include/mpi.h(2145), > from cpi.c(7): > ../src/include/mpio.h(264): warning #1787: alias definitions not supported on this platform; attribute ignored > MPI_File MPI_File_f2c(MPI_Fint file) MPICH_ATTR_WEAK_ALIAS("PMPI_File_f2c"); > ^ > > In file included from ../src/include/mpi.h(2145), > from cpi.c(7): > ../src/include/mpio.h(265): warning #1787: alias definitions not supported on this platform; attribute ignored > MPI_Fint MPI_File_c2f(MPI_File file) MPICH_ATTR_WEAK_ALIAS("PMPI_File_c2f"); > ^ > > /bin/sh ../libtool --tag=CC --mode=link icc -O2 -L../lib -L/opt/ilocal/src/mpich-3.1rc2/src/mpl -L/opt/ilocal/src/mpich-3.1rc2/src/openpa/src -Wl,-flat_namespace -static -Wl,-flat_namespace -o cpi cpi.o -lm -lpthread -lmpich -lmpl -lopa -lopa -lmpl -lpthread > libtool: link: icc -O2 -Wl,-flat_namespace -Wl,-flat_namespace -o cpi cpi.o -L../lib -L/opt/ilocal/src/mpich-3.1rc2/src/mpl -L/opt/ilocal/src/mpich-3.1rc2/src/openpa/src -lm /opt/ilocal/src/mpich-3.1rc2/lib/.libs/libmpich.a /opt/ilocal/src/mpich-3.1rc2/src/openpa/src/.libs/libopa.a /opt/ilocal/src/mpich-3.1rc2/src/mpl/.libs/libmpl.a -lpthread > Undefined symbols for architecture x86_64: > "_MPI_Bcast", referenced from: > _main in cpi.o > "_MPI_Comm_rank", referenced from: > _main in cpi.o > "_MPI_Comm_size", referenced from: > _main in cpi.o > "_MPI_Finalize", referenced from: > _main in cpi.o > "_MPI_Get_processor_name", referenced from: > _main in cpi.o > "_MPI_Init", referenced from: > _main in cpi.o > "_MPI_Reduce", referenced from: > _main in cpi.o > "_MPI_Wtime", referenced from: > _main in cpi.o > ld: symbol(s) not found for architecture x86_64 > make[2]: *** [cpi] Error 1 > make[1]: *** [all-recursive] Error 1 > make: *** [all] Error 2 > > > > > > > > -----Original Message----- > From: discuss-bounces(a)mpich.org on behalf of Eric A. Borisch > Sent: Mon 1/13/2014 12:39 AM > To: discuss(a)mpich.org > Subject: [mpich-discuss] MPICH 3.1rc2 build error on Darwin. > > He's building with icc/ifort, so it's not being done via MacPorts. I don't think he even needs MP or Homebrew installed to build MPICH, just Intel's tools (and Xcode). > > Building with 'make V=1' (or configuring with --disable-silent-rules) will provide more insight into what is going on. If you do have MP or Homebrew installed, you can rule out most interaction by removing their locations (/opt/local/bin, or /usr/local/bin, respectively) from PATH. > > Jeff, I'm sorry to year you were unhappy with the (MP) tools. FWIW, it's been reworked to have a standardized MPICH version (with GCC's Fortan and the system's default C compiler) that is installed for use by any (macports-built) package that needs it. > > Thanks, > - Eric > > On Sunday, January 12, 2014, Jeff Hammond wrote: > > > Might be the MacPorts garbage that bit me a while back too. If GCC fails, I suggest wiping MacPorts and installing Homebrew and the associated toolchain. > > Jeff > > Sent from my iPhone > > > On Jan 12, 2014, at 7:58 PM, Rajeev Thakur <thakur(a)mcs.anl.gov> wrote: > > > > It sounds like a 32-bit, 64-bit incompatibility between some installed compilers/linker. Are you able to build with gcc? > > > > > >> On Jan 10, 2014, at 3:09 PM, "Salmon, Rene" <salmr0(a)bp.com> wrote: > >> > >> > >> Hi, > >> > >> Just trying to build MPICH 3.1rc2 on a Mac. The build seems to work but fails while trying to compile the examples. This is using the intel compilers. > >> > >> ifort,icc version 14.0.0.074 > >> > >> Here is the config line. > >> ./configure CC=icc CXX=icpc F77=ifort FC=ifort --enable-fc > >> > >> > >> error message. > >> > >> make[4]: Nothing to be done for `all'. > >> make[4]: Nothing to be done for `all-am'. > >> Making all in . > >> Making all in . > >> Making all in examples > >> CCLD cpi > >> Undefined symbols for architecture x86_64: > >> "_MPI_Bcast", referenced from: > >> _main in cpi.o > >> "_MPI_Comm_rank", referenced from: > >> _main in cpi.o > >> "_MPI_Comm_size", referenced from: > >> _main in cpi.o > >> "_MPI_Finalize", referenced from: > >> _main in cpi.o > >> "_MPI_Get_processor_name", referenced from: > >> _main in cpi.o > >> "_MPI_Init", referenced from: > >> _main in cpi.o > >> "_MPI_Reduce", referenced from: > >> _main in cpi.o > >> "_MPI_Wtime", referenced from: > >> _main in cpi.o > >> ld: symbol(s) not found for architecture x86_64 > >> make[2]: *** [cpi] Error 1 > >> make[1]: *** [all-recursive] Error 1 > >> make: *** [all] Error 2 > >> > >> Thank you. > >> > >> Rene > >> _______________________________________________ > >> 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] MPICH 3.1rc2 build error on Darwin.
by Salmon, Rene 13 Jan '14

13 Jan '14

Thanks for the replies. Here is a bit more info. I tried this with both mpich 3.1rc2 and mpich 3.0.4 mpich 3.1rc2 ============ This seems to compile with out any error messages using gcc. ./configure CC=gcc CXX=g++ F77=gfortran FC=gfortran --prefix=/opt/ilocal/ --enable-fc make mpich 3.1rc2 ========= This fails. I have the output of make V=1 at the end of this email. ./configure CC=icc CXX=icpc F77=ifort FC=ifort --prefix=/opt/ilocal/ --enable-fc make mpich 3.0.4 =========== This seems to work with mpich 3.0.4. No error messages. ./configure CC=icc CXX=icpc F77=ifort FC=ifort --prefix=/opt/ilocal/ --enable-fc make Here is the output to make V=1 for mpich 3.2rc2 using intel compilers. ================================ In file included from ../src/include/mpi.h(2145), from cpi.c(7): ../src/include/mpio.h(227): warning #1787: alias definitions not supported on this platform; attribute ignored int MPI_File_get_atomicity(MPI_File fh, int *flag) MPICH_ATTR_WEAK_ALIAS("PMPI_File_get_atomicity"); ^ In file included from ../src/include/mpi.h(2145), from cpi.c(7): ../src/include/mpio.h(228): warning #1787: alias definitions not supported on this platform; attribute ignored int MPI_File_sync(MPI_File fh) MPICH_ATTR_WEAK_ALIAS("PMPI_File_sync"); ^ In file included from ../src/include/mpi.h(2145), from cpi.c(7): ../src/include/mpio.h(264): warning #1787: alias definitions not supported on this platform; attribute ignored MPI_File MPI_File_f2c(MPI_Fint file) MPICH_ATTR_WEAK_ALIAS("PMPI_File_f2c"); ^ In file included from ../src/include/mpi.h(2145), from cpi.c(7): ../src/include/mpio.h(265): warning #1787: alias definitions not supported on this platform; attribute ignored MPI_Fint MPI_File_c2f(MPI_File file) MPICH_ATTR_WEAK_ALIAS("PMPI_File_c2f"); ^ /bin/sh ../libtool --tag=CC --mode=link icc -O2 -L../lib -L/opt/ilocal/src/mpich-3.1rc2/src/mpl -L/opt/ilocal/src/mpich-3.1rc2/src/openpa/src -Wl,-flat_namespace -static -Wl,-flat_namespace -o cpi cpi.o -lm -lpthread -lmpich -lmpl -lopa -lopa -lmpl -lpthread libtool: link: icc -O2 -Wl,-flat_namespace -Wl,-flat_namespace -o cpi cpi.o -L../lib -L/opt/ilocal/src/mpich-3.1rc2/src/mpl -L/opt/ilocal/src/mpich-3.1rc2/src/openpa/src -lm /opt/ilocal/src/mpich-3.1rc2/lib/.libs/libmpich.a /opt/ilocal/src/mpich-3.1rc2/src/openpa/src/.libs/libopa.a /opt/ilocal/src/mpich-3.1rc2/src/mpl/.libs/libmpl.a -lpthread Undefined symbols for architecture x86_64: "_MPI_Bcast", referenced from: _main in cpi.o "_MPI_Comm_rank", referenced from: _main in cpi.o "_MPI_Comm_size", referenced from: _main in cpi.o "_MPI_Finalize", referenced from: _main in cpi.o "_MPI_Get_processor_name", referenced from: _main in cpi.o "_MPI_Init", referenced from: _main in cpi.o "_MPI_Reduce", referenced from: _main in cpi.o "_MPI_Wtime", referenced from: _main in cpi.o ld: symbol(s) not found for architecture x86_64 make[2]: *** [cpi] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 -----Original Message----- From: discuss-bounces(a)mpich.org on behalf of Eric A. Borisch Sent: Mon 1/13/2014 12:39 AM To: discuss(a)mpich.org Subject: [mpich-discuss] MPICH 3.1rc2 build error on Darwin. He's building with icc/ifort, so it's not being done via MacPorts. I don't think he even needs MP or Homebrew installed to build MPICH, just Intel's tools (and Xcode). Building with 'make V=1' (or configuring with --disable-silent-rules) will provide more insight into what is going on. If you do have MP or Homebrew installed, you can rule out most interaction by removing their locations (/opt/local/bin, or /usr/local/bin, respectively) from PATH. Jeff, I'm sorry to year you were unhappy with the (MP) tools. FWIW, it's been reworked to have a standardized MPICH version (with GCC's Fortan and the system's default C compiler) that is installed for use by any (macports-built) package that needs it. Thanks, - Eric On Sunday, January 12, 2014, Jeff Hammond wrote: Might be the MacPorts garbage that bit me a while back too. If GCC fails, I suggest wiping MacPorts and installing Homebrew and the associated toolchain. Jeff Sent from my iPhone > On Jan 12, 2014, at 7:58 PM, Rajeev Thakur <thakur(a)mcs.anl.gov> wrote: > > It sounds like a 32-bit, 64-bit incompatibility between some installed compilers/linker. Are you able to build with gcc? > > >> On Jan 10, 2014, at 3:09 PM, "Salmon, Rene" <salmr0(a)bp.com> wrote: >> >> >> Hi, >> >> Just trying to build MPICH 3.1rc2 on a Mac. The build seems to work but fails while trying to compile the examples. This is using the intel compilers. >> >> ifort,icc version 14.0.0.074 >> >> Here is the config line. >> ./configure CC=icc CXX=icpc F77=ifort FC=ifort --enable-fc >> >> >> error message. >> >> make[4]: Nothing to be done for `all'. >> make[4]: Nothing to be done for `all-am'. >> Making all in . >> Making all in . >> Making all in examples >> CCLD cpi >> Undefined symbols for architecture x86_64: >> "_MPI_Bcast", referenced from: >> _main in cpi.o >> "_MPI_Comm_rank", referenced from: >> _main in cpi.o >> "_MPI_Comm_size", referenced from: >> _main in cpi.o >> "_MPI_Finalize", referenced from: >> _main in cpi.o >> "_MPI_Get_processor_name", referenced from: >> _main in cpi.o >> "_MPI_Init", referenced from: >> _main in cpi.o >> "_MPI_Reduce", referenced from: >> _main in cpi.o >> "_MPI_Wtime", referenced from: >> _main in cpi.o >> ld: symbol(s) not found for architecture x86_64 >> make[2]: *** [cpi] Error 1 >> make[1]: *** [all-recursive] Error 1 >> make: *** [all] Error 2 >> >> Thank you. >> >> Rene >> _______________________________________________ >> 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] halo update performance comparison
by Rajeev Thakur 13 Jan '14

13 Jan '14

If you could send us your test case, that would be great. Rajeev On Jan 13, 2014, at 3:58 PM, "Kokron, Daniel S. (GSFC-606.2)[Computer Sciences Corporation]" <daniel.s.kokron(a)nasa.gov> wrote: > II should be able to package up my test case. > Please let me know if I can help > > Daniel Kokron > NASA Ames (ARC-TN) > SciCon group > 301-286-3959 > > ________________________________________ > From: discuss-bounces(a)mpich.org [discuss-bounces(a)mpich.org] on behalf of Rajeev Thakur [thakur(a)mcs.anl.gov] > Sent: Monday, January 13, 2014 4:45 PM > To: discuss(a)mpich.org > Subject: Re: [mpich-discuss] halo update performance comparison > >> Is there room for improvement? > > Yes, we are looking into it. > > Rajeev > > On Dec 13, 2013, at 2:31 PM, "Kokron, Daniel S. (GSFC-610.1)[Computer Sciences Corporation]" <daniel.s.kokron(a)nasa.gov> wrote: > >> All, >> >> I have been interested in MPI datatypes since reading about them and playing with the benchmark found at http://unixer.de/research/datatypes/ddtbench/ >> >> I am working with a weather model that spends considerable time doing halo (aka ghost cell) updates. The existing code uses irecv/isend. Since most of the time spent doing halo updates is actually spent packing and unpacking the MPI buffers, I was hoping the use of datatypes would improve performance. Unfortunately, the datatype version is actually quite a bit slower than the standard non-blocking pt2pt code. I found this to be that case for both mpich-3.1rc1 and a recent version of a vendor MPI implementation (not MPICH based). I have not run this comparison using OpenMPI. >> >> Is data type performance an active area of development? Is there room for improvement? >> >> Daniel Kokron >> NASA Ames (ARC-TN) >> SciCon group >> 301-286-3959 >> _______________________________________________ >> 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