- discuss - mailman3.cels.anl.gov

Unable to use --enable-fast=O3,ndebug
by William Gropp 25 Aug '20

25 Aug '20

(If there is a better way to submit these, let me know. The “bug report” link doesn’t work from mpich.org) —enable-fast in the top level configure accepts multiple, comma-separated items. The configure in modules/yaksa/configure.ac expects (without checking) an O level only. This causes the configure step to fail with an unrelated error (yaksa thinks that it can’t fine pthreads). Bill William Gropp Director and Chief Scientist, NCSA Thomas M. Siebel Chair in Computer Science University of Illinois Urbana-Champaign

1 0

Re: [mpich-discuss] Unable to build on OSX
by William Gropp 13 Aug '20

13 Aug '20

Thanks - I’m up to the runtime failure on FI_ADDR_NOTAVAIL. Is there an alternative path to build MPICH on OSX? Bill William Gropp Director and Chief Scientist, NCSA Thomas M. Siebel Chair in Computer Science University of Illinois Urbana-Champaign > On Aug 7, 2020, at 11:54 AM, Zhou, Hui via discuss <discuss(a)mpich.org> wrote: > > Follow up -- > > If you hit this runtime error: > > Assertion failed in file src/mpid/ch4/netmod/ofi/ofi_init.c at line xxxx: mapped_table[i] != FI_ADDR_NOTAVAIL > > That is due to libfabric having trouble with ipv6 addresses and it ignores our hints on addr_format. I'll work out a patch later. > > -- > Hui Zhou > > > > On 8/7/20, 10:24 AM, "Raffenetti, Kenneth J." <raffenet(a)mcs.anl.gov> wrote: > > Just updating from git is not enough to fix it, though. Since it is a submodule update, you'll need to run > > git submodule update --init > > to pull in the latest fix. > > Ken > > On 8/6/20, 10:14 PM, "Zhou, Hui via discuss" <discuss(a)mpich.org> wrote: > > The particular link error should have been fixed since this Monday. Try make sure it is the correct source tree and clean build tree? That said, there will be additional run time issues building ch4 on mac. I’ll spend some time tomorrow and follow up if I can make progress. > > -- > Hui Zhou > Principal Software Development Specialist > Mathematics and Computer Science > Argonne National Laboratory > > > > From: "Gropp, William D via discuss" <discuss(a)mpich.org> > Reply-To: "discuss(a)mpich.org" <discuss(a)mpich.org> > Date: Thursday, August 6, 2020 at 5:01 PM > To: "discuss(a)mpich.org" <discuss(a)mpich.org> > Cc: "Gropp, William D" <wgropp(a)illinois.edu> > Subject: [mpich-discuss] Unable to build on OSX > > > > Using the current as of this morning from git, hash 1d340282 , and with CC=gcc-10 (needed to work with the corresponding version of gfortran, because gcc on OSX is really clang) > > > ../../sources/mpich/configure --with-device=ch4:ofi --prefix=/Users/gropp/installs/mpich2-dbg > > > > works but make ends with > > > > /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: lib/.libs/libmpifort.a(mpi_c_interface_nobuf.o) has no symbols > > CXX src/binding/cxx/initcxx.lo > > CXXLD lib/libmpicxx.la <http://libmpicxx.la> > > CC src/env/mpichversion.o > > CCLD src/env/mpichversion > > Undefined symbols for architecture x86_64: > > "_ofi_process_vm_writev", referenced from: > > import-atom in libpmpi.dylib > > ld: symbol(s) not found for architecture x86_64 > > collect2: error: ld returned 1 exit status > > make[2]: *** [src/env/mpichversion] Error 1 > > make[1]: *** [all-recursive] Error 1 > > make: *** [all] Error 2 > > gropp@wdg-macbook hydra % > > > > > Configure and make logs attached. > > > > (Some of the instructions on the MPICH web page for submitting bug reports sent me to unreachable github web pages) > > > > > > > > William Gropp > Director and Chief Scientist, NCSA > Thomas M. Siebel Chair in Computer Science > University of Illinois Urbana-Champaign > > > > > > > > > > > > > > _______________________________________________ > 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] Unable to build on OSX
by Zhou, Hui 07 Aug '20

07 Aug '20

Follow up -- If you hit this runtime error: Assertion failed in file src/mpid/ch4/netmod/ofi/ofi_init.c at line xxxx: mapped_table[i] != FI_ADDR_NOTAVAIL That is due to libfabric having trouble with ipv6 addresses and it ignores our hints on addr_format. I'll work out a patch later. -- Hui Zhou On 8/7/20, 10:24 AM, "Raffenetti, Kenneth J." <raffenet(a)mcs.anl.gov> wrote: Just updating from git is not enough to fix it, though. Since it is a submodule update, you'll need to run git submodule update --init to pull in the latest fix. Ken On 8/6/20, 10:14 PM, "Zhou, Hui via discuss" <discuss(a)mpich.org> wrote: The particular link error should have been fixed since this Monday. Try make sure it is the correct source tree and clean build tree? That said, there will be additional run time issues building ch4 on mac. I’ll spend some time tomorrow and follow up if I can make progress. -- Hui Zhou Principal Software Development Specialist Mathematics and Computer Science Argonne National Laboratory From: "Gropp, William D via discuss" <discuss(a)mpich.org> Reply-To: "discuss(a)mpich.org" <discuss(a)mpich.org> Date: Thursday, August 6, 2020 at 5:01 PM To: "discuss(a)mpich.org" <discuss(a)mpich.org> Cc: "Gropp, William D" <wgropp(a)illinois.edu> Subject: [mpich-discuss] Unable to build on OSX Using the current as of this morning from git, hash 1d340282 , and with CC=gcc-10 (needed to work with the corresponding version of gfortran, because gcc on OSX is really clang) ../../sources/mpich/configure --with-device=ch4:ofi --prefix=/Users/gropp/installs/mpich2-dbg works but make ends with /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: lib/.libs/libmpifort.a(mpi_c_interface_nobuf.o) has no symbols CXX src/binding/cxx/initcxx.lo CXXLD lib/libmpicxx.la <http://libmpicxx.la> CC src/env/mpichversion.o CCLD src/env/mpichversion Undefined symbols for architecture x86_64: "_ofi_process_vm_writev", referenced from: import-atom in libpmpi.dylib ld: symbol(s) not found for architecture x86_64 collect2: error: ld returned 1 exit status make[2]: *** [src/env/mpichversion] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 gropp@wdg-macbook hydra % Configure and make logs attached. (Some of the instructions on the MPICH web page for submitting bug reports sent me to unreachable github web pages) William Gropp Director and Chief Scientist, NCSA Thomas M. Siebel Chair in Computer Science University of Illinois Urbana-Champaign

1 0

Re: [mpich-discuss] Unable to build on OSX
by Raffenetti, Kenneth J. 07 Aug '20

07 Aug '20

Just updating from git is not enough to fix it, though. Since it is a submodule update, you'll need to run git submodule update --init to pull in the latest fix. Ken On 8/6/20, 10:14 PM, "Zhou, Hui via discuss" <discuss(a)mpich.org> wrote: The particular link error should have been fixed since this Monday. Try make sure it is the correct source tree and clean build tree? That said, there will be additional run time issues building ch4 on mac. I’ll spend some time tomorrow and follow up if I can make progress. -- Hui Zhou Principal Software Development Specialist Mathematics and Computer Science Argonne National Laboratory From: "Gropp, William D via discuss" <discuss(a)mpich.org> Reply-To: "discuss(a)mpich.org" <discuss(a)mpich.org> Date: Thursday, August 6, 2020 at 5:01 PM To: "discuss(a)mpich.org" <discuss(a)mpich.org> Cc: "Gropp, William D" <wgropp(a)illinois.edu> Subject: [mpich-discuss] Unable to build on OSX Using the current as of this morning from git, hash 1d340282 , and with CC=gcc-10 (needed to work with the corresponding version of gfortran, because gcc on OSX is really clang) ../../sources/mpich/configure --with-device=ch4:ofi --prefix=/Users/gropp/installs/mpich2-dbg works but make ends with /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: lib/.libs/libmpifort.a(mpi_c_interface_nobuf.o) has no symbols CXX src/binding/cxx/initcxx.lo CXXLD lib/libmpicxx.la <http://libmpicxx.la> CC src/env/mpichversion.o CCLD src/env/mpichversion Undefined symbols for architecture x86_64: "_ofi_process_vm_writev", referenced from: import-atom in libpmpi.dylib ld: symbol(s) not found for architecture x86_64 collect2: error: ld returned 1 exit status make[2]: *** [src/env/mpichversion] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 gropp@wdg-macbook hydra % Configure and make logs attached. (Some of the instructions on the MPICH web page for submitting bug reports sent me to unreachable github web pages) William Gropp Director and Chief Scientist, NCSA Thomas M. Siebel Chair in Computer Science University of Illinois Urbana-Champaign

1 0

Re: [mpich-discuss] Unable to build on OSX
by Zhou, Hui 06 Aug '20

06 Aug '20

The particular link error should have been fixed since this Monday. Try make sure it is the correct source tree and clean build tree? That said, there will be additional run time issues building ch4 on mac. I’ll spend some time tomorrow and follow up if I can make progress. -- Hui Zhou Principal Software Development Specialist Mathematics and Computer Science Argonne National Laboratory From: "Gropp, William D via discuss" <discuss(a)mpich.org> Reply-To: "discuss(a)mpich.org" <discuss(a)mpich.org> Date: Thursday, August 6, 2020 at 5:01 PM To: "discuss(a)mpich.org" <discuss(a)mpich.org> Cc: "Gropp, William D" <wgropp(a)illinois.edu> Subject: [mpich-discuss] Unable to build on OSX Using the current as of this morning from git, hash 1d340282 , and with CC=gcc-10 (needed to work with the corresponding version of gfortran, because gcc on OSX is really clang) ../../sources/mpich/configure --with-device=ch4:ofi --prefix=/Users/gropp/installs/mpich2-dbg works but make ends with /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: lib/.libs/libmpifort.a(mpi_c_interface_nobuf.o) has no symbols CXX src/binding/cxx/initcxx.lo CXXLD lib/libmpicxx.la<http://libmpicxx.la> CC src/env/mpichversion.o CCLD src/env/mpichversion Undefined symbols for architecture x86_64: "_ofi_process_vm_writev", referenced from: import-atom in libpmpi.dylib ld: symbol(s) not found for architecture x86_64 collect2: error: ld returned 1 exit status make[2]: *** [src/env/mpichversion] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 gropp@wdg-macbook hydra % Configure and make logs attached. (Some of the instructions on the MPICH web page for submitting bug reports sent me to unreachable github web pages) William Gropp Director and Chief Scientist, NCSA Thomas M. Siebel Chair in Computer Science University of Illinois Urbana-Champaign

1 0

Unable to build on OSX
by Gropp, William D 06 Aug '20

06 Aug '20

Using the current as of this morning from git, hash 1d340282 , and with CC=gcc-10 (needed to work with the corresponding version of gfortran, because gcc on OSX is really clang) ../../sources/mpich/configure --with-device=ch4:ofi --prefix=/Users/gropp/installs/mpich2-dbg works but make ends with /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: lib/.libs/libmpifort.a(mpi_c_interface_nobuf.o) has no symbols CXX src/binding/cxx/initcxx.lo CXXLD lib/libmpicxx.la<http://libmpicxx.la> CC src/env/mpichversion.o CCLD src/env/mpichversion Undefined symbols for architecture x86_64: "_ofi_process_vm_writev", referenced from: import-atom in libpmpi.dylib ld: symbol(s) not found for architecture x86_64 collect2: error: ld returned 1 exit status make[2]: *** [src/env/mpichversion] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 gropp@wdg-macbook hydra % Configure and make logs attached. (Some of the instructions on the MPICH web page for submitting bug reports sent me to unreachable github web pages) William Gropp Director and Chief Scientist, NCSA Thomas M. Siebel Chair in Computer Science University of Illinois Urbana-Champaign

1 0

Re: [mpich-discuss] IB network module is unknown
by Balaji, Pavan 11 Jul '20

11 Jul '20

The ch3:nemesis:ib device is not supported anymore. Please use ch4:ucx for Mellanox IB networks. Sent from my iPhone On Jul 11, 2020, at 10:22 AM, Sabu Best via discuss <discuss(a)mpich.org> wrote: Good morning, While trying to configure MPICH for inifiniband we got the following error /configure --prefix=$DIR/mpich --with-device=ch3:nemesis:ib . . . . checking for signal.h... yes checking for signal... yes configure: error: Network module ib is unknown "./src/mpid/ch3/channels/nemesis/netmod/ib" Any suggestions anyone? _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

IB network module is unknown
by Sabu Best 11 Jul '20

11 Jul '20

Good morning, While trying to configure MPICH for inifiniband we got the following error /configure --prefix=$DIR/mpich --with-device=ch3:nemesis:ib . . . . checking for signal.h... yes checking for signal... yes configure: error: Network module ib is unknown "./src/mpid/ch3/channels/nemesis/netmod/ib" Any suggestions anyone?

1 0

Re: [mpich-discuss] Receiving fortran-related errors when compiling MPICH 3.3.2
by Arham Amouei 08 Jul '20

08 Jul '20

Fortunately, I was able to compile it by restricting PATH and LD_LIBRARY_PATH variables. Arham ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Wednesday, July 8, 2020 9:25 PM, Arham Amouei via discuss <discuss(a)mpich.org> wrote: >> That's right. There already exist some MPI installations on this system. >> >> I receive this error when making MPICH 3.3.2 itself, not when compiling some code with mpicc. So It's not clear what you mean about using the correct mpicc. >> >> Thanks. >> Arham > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > On Wednesday, July 8, 2020 8:30 PM, Zhou, Hui <zhouh(a)anl.gov> wrote: > >> Hi Arham, >> >> I think you have multiple MPI installations mixing up. Please double check that you are using the correct `mpicc` and check the results with `ldd`. >> >> -- >> Hui Zhou >> >> From: Arham Amouei via discuss <discuss(a)mpich.org> >> Reply-To: Arham Amouei <arham.amouei(a)protonmail.com>, "discuss(a)mpich.org" <discuss(a)mpich.org> >> Date: Wednesday, July 8, 2020 at 10:48 AM >> To: "discuss(a)mpich.org" <discuss(a)mpich.org> >> Cc: Arham Amouei <arham.amouei(a)protonmail.com> >> Subject: [mpich-discuss] Receiving fortran-related errors when compiling MPICH 3.3.2 >> >> Hello. >> >> Despite I have disabled fortran by --disable-fortran, I receive errors related to fortran when compiling MPICH 3.3.2. >> >> Example: >> >> .../linux/mpi/intel64/lib/libmpifort.so.12: undefined reference to `PMPI_Type_create_f90_complex' >> >> How can I get rid of those errors without changing other installed softwares? >> >> Please find attached m.txt and c.txt files. >> >> Kind regards, >> >> Arham

1 0

Re: [mpich-discuss] Receiving fortran-related errors when compiling MPICH 3.3.2
by Arham Amouei 08 Jul '20

08 Jul '20

> That's right. There already exist some MPI installations on this system. > > I receive this error when making MPICH 3.3.2 itself, not when compiling some code with mpicc. So It's not clear what you mean about using the correct mpicc. > > Thanks. > Arham ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Wednesday, July 8, 2020 8:30 PM, Zhou, Hui <zhouh(a)anl.gov> wrote: > Hi Arham, > > I think you have multiple MPI installations mixing up. Please double check that you are using the correct `mpicc` and check the results with `ldd`. > > -- > Hui Zhou > > From: Arham Amouei via discuss <discuss(a)mpich.org> > Reply-To: Arham Amouei <arham.amouei(a)protonmail.com>, "discuss(a)mpich.org" <discuss(a)mpich.org> > Date: Wednesday, July 8, 2020 at 10:48 AM > To: "discuss(a)mpich.org" <discuss(a)mpich.org> > Cc: Arham Amouei <arham.amouei(a)protonmail.com> > Subject: [mpich-discuss] Receiving fortran-related errors when compiling MPICH 3.3.2 > > Hello. > > Despite I have disabled fortran by --disable-fortran, I receive errors related to fortran when compiling MPICH 3.3.2. > > Example: > > .../linux/mpi/intel64/lib/libmpifort.so.12: undefined reference to `PMPI_Type_create_f90_complex' > > How can I get rid of those errors without changing other installed softwares? > > Please find attached m.txt and c.txt files. > > Kind regards, > > Arham

1 0