November 2015 - discuss - mailman3.cels.anl.gov

Re: [mpich-discuss] IBM BG/Q collectives
by Jeff Hammond 19 Nov '15

19 Nov '15

That sounds about right. Some of the names for the BGQ-specific optimized collectives are pretty elaborate. SCATTER_MPICH Is tame by comparison :-) I can't remember if the names are listed in the redbook, but you can always grep the source code. Jeff On Thu, Nov 19, 2015 at 8:24 PM, Jen B <jenbna(a)gmail.com> wrote: > Thank you for your answers and helpful suggestions, Rob and Jeff! > > I have my last question I hope someone could help me clarify. So I get > algorithm names for MPI collectives. Is there any convention for them? I > did not find this information in the redbook. For example, for some of the > algorithm names I get "SCATTER_MPICH", so I think this means that if the > algorithm name ends with "_MPICH" then this is using the algorithm from > MPICH, not the ones optimized for BG/Q. Is this correct? > > Thank you! > Jen > > > On Thu, Nov 19, 2015 at 5:49 PM, Jeff Hammond <jeff.science(a)gmail.com> > wrote: > >> As Rob said, you will find lots of info in the redbook. You can set all >> sorts of debug options to print out the algorithm(s) used on every call, or >> prescribe them explicitly (not recommended). >> >> Jeff >> >> On Thu, Nov 19, 2015 at 8:38 AM, Jen B <jenbna(a)gmail.com> wrote: >> >>> Thank you for your quick response, Jeff! >>> >>> I was wondering the values for "short" and "large" message sizes, >>> they've been used throughout the paper but not mentioned explicitly. Do you >>> happen to know if these values are explicitly mentioned somewhere? >>> >>> Also, if I get the last algorithm name used for the MPI collective >>> routine, is there a way I can for sure tell which algorithm is being used? >>> For example, is there any name formatting convention that is used. >>> >>> Sorry for so many questions. Any help with any of these questions will >>> be greatly appreciated! >>> >>> Thank you! >>> Jen >>> >>> >>> On Wed, Nov 18, 2015 at 6:06 PM, Jeff Hammond <jeff.science(a)gmail.com> >>> wrote: >>> >>>> A binary tree is the implementation of last resort. >>>> >>>> See these papers for details of the MPI collective implementations on >>>> Blue Gene: >>>> - http://dx.doi.org/10.1177/1094342014552086 >>>> - http://dx.doi.org/10.1109/HOTI.2009.12 >>>> (this is not an inclusive list) >>>> >>>> http://lists.mpich.org/pipermail/discuss/2015-March/003754.html has >>>> some related info. >>>> >>>> Jeff >>>> >>>> On Wed, Nov 18, 2015 at 12:53 PM, Jen B <jenbna(a)gmail.com> wrote: >>>> >>>>> Hello, >>>>> >>>>> I have a couple of questions about BG/Q collectives and would >>>>> appreciate any help. >>>>> I was wondering if Do IBM BG/Q MPI collectives use binomial tree? >>>>> Once I find the name of the algorithm used by the MPI collective >>>>> routine using MPIX_Get_last_algorithm_name, is there a quick reference or >>>>> guide to check how it is implemented? >>>>> >>>>> Thanks! >>>>> Jen >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>>> http://jeffhammond.github.io/ >>>> >>>> _______________________________________________ >>>> 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 >>> >> >> >> >> -- >> Jeff Hammond >> jeff.science(a)gmail.com >> http://jeffhammond.github.io/ >> >> _______________________________________________ >> 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 > -- Jeff Hammond jeff.science(a)gmail.com http://jeffhammond.github.io/ _______________________________________________ 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] IBM BG/Q collectives
by Jen B 19 Nov '15

19 Nov '15

Thank you for your answers and helpful suggestions, Rob and Jeff! I have my last question I hope someone could help me clarify. So I get algorithm names for MPI collectives. Is there any convention for them? I did not find this information in the redbook. For example, for some of the algorithm names I get "SCATTER_MPICH", so I think this means that if the algorithm name ends with "_MPICH" then this is using the algorithm from MPICH, not the ones optimized for BG/Q. Is this correct? Thank you! Jen On Thu, Nov 19, 2015 at 5:49 PM, Jeff Hammond <jeff.science(a)gmail.com> wrote: > As Rob said, you will find lots of info in the redbook. You can set all > sorts of debug options to print out the algorithm(s) used on every call, or > prescribe them explicitly (not recommended). > > Jeff > > On Thu, Nov 19, 2015 at 8:38 AM, Jen B <jenbna(a)gmail.com> wrote: > >> Thank you for your quick response, Jeff! >> >> I was wondering the values for "short" and "large" message sizes, they've >> been used throughout the paper but not mentioned explicitly. Do you happen >> to know if these values are explicitly mentioned somewhere? >> >> Also, if I get the last algorithm name used for the MPI collective >> routine, is there a way I can for sure tell which algorithm is being used? >> For example, is there any name formatting convention that is used. >> >> Sorry for so many questions. Any help with any of these questions will be >> greatly appreciated! >> >> Thank you! >> Jen >> >> >> On Wed, Nov 18, 2015 at 6:06 PM, Jeff Hammond <jeff.science(a)gmail.com> >> wrote: >> >>> A binary tree is the implementation of last resort. >>> >>> See these papers for details of the MPI collective implementations on >>> Blue Gene: >>> - http://dx.doi.org/10.1177/1094342014552086 >>> - http://dx.doi.org/10.1109/HOTI.2009.12 >>> (this is not an inclusive list) >>> >>> http://lists.mpich.org/pipermail/discuss/2015-March/003754.html has >>> some related info. >>> >>> Jeff >>> >>> On Wed, Nov 18, 2015 at 12:53 PM, Jen B <jenbna(a)gmail.com> wrote: >>> >>>> Hello, >>>> >>>> I have a couple of questions about BG/Q collectives and would >>>> appreciate any help. >>>> I was wondering if Do IBM BG/Q MPI collectives use binomial tree? >>>> Once I find the name of the algorithm used by the MPI collective >>>> routine using MPIX_Get_last_algorithm_name, is there a quick reference or >>>> guide to check how it is implemented? >>>> >>>> Thanks! >>>> Jen >>>> >>>> >>>> _______________________________________________ >>>> 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 >>> http://jeffhammond.github.io/ >>> >>> _______________________________________________ >>> 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 >> > > > > -- > Jeff Hammond > jeff.science(a)gmail.com > http://jeffhammond.github.io/ > > _______________________________________________ > 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] IBM BG/Q collectives
by Jeff Hammond 19 Nov '15

19 Nov '15

As Rob said, you will find lots of info in the redbook. You can set all sorts of debug options to print out the algorithm(s) used on every call, or prescribe them explicitly (not recommended). Jeff On Thu, Nov 19, 2015 at 8:38 AM, Jen B <jenbna(a)gmail.com> wrote: > Thank you for your quick response, Jeff! > > I was wondering the values for "short" and "large" message sizes, they've > been used throughout the paper but not mentioned explicitly. Do you happen > to know if these values are explicitly mentioned somewhere? > > Also, if I get the last algorithm name used for the MPI collective > routine, is there a way I can for sure tell which algorithm is being used? > For example, is there any name formatting convention that is used. > > Sorry for so many questions. Any help with any of these questions will be > greatly appreciated! > > Thank you! > Jen > > > On Wed, Nov 18, 2015 at 6:06 PM, Jeff Hammond <jeff.science(a)gmail.com> > wrote: > >> A binary tree is the implementation of last resort. >> >> See these papers for details of the MPI collective implementations on >> Blue Gene: >> - http://dx.doi.org/10.1177/1094342014552086 >> - http://dx.doi.org/10.1109/HOTI.2009.12 >> (this is not an inclusive list) >> >> http://lists.mpich.org/pipermail/discuss/2015-March/003754.html has some >> related info. >> >> Jeff >> >> On Wed, Nov 18, 2015 at 12:53 PM, Jen B <jenbna(a)gmail.com> wrote: >> >>> Hello, >>> >>> I have a couple of questions about BG/Q collectives and would appreciate >>> any help. >>> I was wondering if Do IBM BG/Q MPI collectives use binomial tree? >>> Once I find the name of the algorithm used by the MPI collective routine >>> using MPIX_Get_last_algorithm_name, is there a quick reference or guide to >>> check how it is implemented? >>> >>> Thanks! >>> Jen >>> >>> >>> _______________________________________________ >>> 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 >> http://jeffhammond.github.io/ >> >> _______________________________________________ >> 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 > -- Jeff Hammond jeff.science(a)gmail.com http://jeffhammond.github.io/ _______________________________________________ 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] IBM BG/Q collectives
by Rob Latham 19 Nov '15

19 Nov '15

On 11/19/2015 10:38 AM, Jen B wrote: > Thank you for your quick response, Jeff! > > I was wondering the values for "short" and "large" message sizes, > they've been used throughout the paper but not mentioned explicitly. Do > you happen to know if these values are explicitly mentioned somewhere? > > Also, if I get the last algorithm name used for the MPI collective > routine, is there a way I can for sure tell which algorithm is being > used? For example, is there any name formatting convention that is used. > > Sorry for so many questions. Any help with any of these questions will > be greatly appreciated! 'short' and 'large' refers to those messages smaller than /greater than the EAGER_THRESHOLD. https://www.alcf.anl.gov/user-guides/tuning-mpi-bgq has some resources and documentation. The "application red book" is probably what you want. Here's a relevant quote: By default, the MPI send operations use the rendezvous protocol, instead of the eager protocol, for messages larger than 2048 bytes. (there are also immediate and short messages) ==rob > > Thank you! > Jen > > > On Wed, Nov 18, 2015 at 6:06 PM, Jeff Hammond <jeff.science(a)gmail.com > <mailto:[email protected]>> wrote: > > A binary tree is the implementation of last resort. > > See these papers for details of the MPI collective implementations > on Blue Gene: > - http://dx.doi.org/10.1177/1094342014552086 > - http://dx.doi.org/10.1109/HOTI.2009.12 > (this is not an inclusive list) > > http://lists.mpich.org/pipermail/discuss/2015-March/003754.html has > some related info. > > Jeff > > On Wed, Nov 18, 2015 at 12:53 PM, Jen B <jenbna(a)gmail.com > <mailto:[email protected]>> wrote: > > Hello, > > I have a couple of questions about BG/Q collectives and would > appreciate any help. > I was wondering if Do IBM BG/Q MPI collectives use binomial tree? > Once I find the name of the algorithm used by the MPI collective > routine using MPIX_Get_last_algorithm_name, is there a quick > reference or guide to check how it is implemented? > > Thanks! > Jen > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org <mailto:[email protected]> > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > > > > > -- > Jeff Hammond > jeff.science(a)gmail.com <mailto:[email protected]> > http://jeffhammond.github.io/ > > _______________________________________________ > discuss mailing list discuss(a)mpich.org <mailto:[email protected]> > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > > > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > -- Rob Latham Mathematics and Computer Science Division Argonne National Lab, IL USA _______________________________________________ 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] IBM BG/Q collectives
by Jen B 19 Nov '15

19 Nov '15

Thank you for your quick response, Jeff! I was wondering the values for "short" and "large" message sizes, they've been used throughout the paper but not mentioned explicitly. Do you happen to know if these values are explicitly mentioned somewhere? Also, if I get the last algorithm name used for the MPI collective routine, is there a way I can for sure tell which algorithm is being used? For example, is there any name formatting convention that is used. Sorry for so many questions. Any help with any of these questions will be greatly appreciated! Thank you! Jen On Wed, Nov 18, 2015 at 6:06 PM, Jeff Hammond <jeff.science(a)gmail.com> wrote: > A binary tree is the implementation of last resort. > > See these papers for details of the MPI collective implementations on Blue > Gene: > - http://dx.doi.org/10.1177/1094342014552086 > - http://dx.doi.org/10.1109/HOTI.2009.12 > (this is not an inclusive list) > > http://lists.mpich.org/pipermail/discuss/2015-March/003754.html has some > related info. > > Jeff > > On Wed, Nov 18, 2015 at 12:53 PM, Jen B <jenbna(a)gmail.com> wrote: > >> Hello, >> >> I have a couple of questions about BG/Q collectives and would appreciate >> any help. >> I was wondering if Do IBM BG/Q MPI collectives use binomial tree? >> Once I find the name of the algorithm used by the MPI collective routine >> using MPIX_Get_last_algorithm_name, is there a quick reference or guide to >> check how it is implemented? >> >> Thanks! >> Jen >> >> >> _______________________________________________ >> 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 > http://jeffhammond.github.io/ > > _______________________________________________ > 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] IBM BG/Q collectives
by Jeff Hammond 18 Nov '15

18 Nov '15

A binary tree is the implementation of last resort. See these papers for details of the MPI collective implementations on Blue Gene: - http://dx.doi.org/10.1177/1094342014552086 - http://dx.doi.org/10.1109/HOTI.2009.12 (this is not an inclusive list) http://lists.mpich.org/pipermail/discuss/2015-March/003754.html has some related info. Jeff On Wed, Nov 18, 2015 at 12:53 PM, Jen B <jenbna(a)gmail.com> wrote: > Hello, > > I have a couple of questions about BG/Q collectives and would appreciate > any help. > I was wondering if Do IBM BG/Q MPI collectives use binomial tree? > Once I find the name of the algorithm used by the MPI collective routine > using MPIX_Get_last_algorithm_name, is there a quick reference or guide to > check how it is implemented? > > Thanks! > Jen > > > _______________________________________________ > 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 http://jeffhammond.github.io/ _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

IBM BG/Q collectives
by Jen B 18 Nov '15

18 Nov '15

Hello, I have a couple of questions about BG/Q collectives and would appreciate any help. I was wondering if Do IBM BG/Q MPI collectives use binomial tree? Once I find the name of the algorithm used by the MPI collective routine using MPIX_Get_last_algorithm_name, is there a quick reference or guide to check how it is implemented? Thanks! Jen _______________________________________________ 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] building 3.2 fails
by Zbigniew Jędrzejewski-Szmek 16 Nov '15

16 Nov '15

On Mon, Nov 16, 2015 at 11:02:20AM -0600, Kenneth Raffenetti wrote: > There is a bug in the build system that prevents building both the > hydra and gforker process managers at the same time. You'll need to > drop one from your configure line in order to proceed. > > There is a ticket to track this issue, which will be fixed in the > next release. https://trac.mpich.org/projects/mpich/ticket/2299 Thanks for the quick reply! The build still fails for me with the patch. I'll just wait for the next release then. Zbyszek _______________________________________________ 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] building 3.2 fails
by Kenneth Raffenetti 16 Nov '15

16 Nov '15

There is a bug in the build system that prevents building both the hydra and gforker process managers at the same time. You'll need to drop one from your configure line in order to proceed. There is a ticket to track this issue, which will be fixed in the next release. https://trac.mpich.org/projects/mpich/ticket/2299 Ken On 11/16/2015 10:56 AM, Zbigniew Jędrzejewski-Szmek wrote: > Hi, > > I'm trying to compile mpich-3.2 on Fedora rawhide and it fails with the > following: > > /bin/sh ./libtool --tag=FC --mode=compile gfortran -Isrc/binding/fortran/use_mpi -m64 -O2 -fPIC -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic -O2 -Jsrc/binding/fortran/use_mpi -c src/binding/fortran/use_mpi/mpi.f90 -o src/binding/fortran/use_mpi/mpi.lo > libtool: link: gcc -m64 -O2 -fPIC -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic -O2 -Wl,-z -Wl,noexecstack -o src/pm/gforker/mpiexec.gforker src/pm/gforker/src_pm_gforker_mpiexec_gforker-mpiexec.o src/pm/util/libmpiexec.a -lpthread > src/pm/gforker/src_pm_gforker_mpiexec_gforker-mpiexec.o: In function `mpiexec_usage': > /builddir/build/BUILD/mpich-3.2/src/pm/gforker/mpiexec.c:283: undefined reference to `MPL_usage_printf' > src/pm/util/libmpiexec.a(src_pm_util_libmpiexec_a-process.o): In function `MPIE_ExecProgram': > /builddir/build/BUILD/mpich-3.2/src/pm/util/process.c:362: undefined reference to `MPL_internal_sys_error_printf' > src/pm/util/libmpiexec.a(src_pm_util_libmpiexec_a-process.o): In function `MPIE_ForkProcesses': > /builddir/build/BUILD/mpich-3.2/src/pm/util/process.c:173: undefined reference to `MPL_internal_error_printf' > /builddir/build/BUILD/mpich-3.2/src/pm/util/process.c:155: undefined reference to `MPL_internal_error_printf' > src/pm/util/libmpiexec.a(src_pm_util_libmpiexec_a-ioloop.o): In function `MPIE_IOLoop': > /builddir/build/BUILD/mpich-3.2/src/pm/util/ioloop.c:191: undefined reference to `MPL_internal_sys_error_printf' > src/pm/util/libmpiexec.a(src_pm_util_libmpiexec_a-pmiserv.o): In function `fPMIKVSAllocate': > /builddir/build/BUILD/mpich-3.2/src/pm/util/pmiserv.c:461: undefined reference to `MPL_internal_error_printf' > src/pm/util/libmpiexec.a(src_pm_util_libmpiexec_a-pmiserv.o): In function `PMISetupInClient': > /builddir/build/BUILD/mpich-3.2/src/pm/util/pmiserv.c:175: undefined reference to `MPL_internal_error_printf' > /builddir/build/BUILD/mpich-3.2/src/pm/util/pmiserv.c:185: undefined reference to `MPL_internal_error_printf' > /builddir/build/BUILD/mpich-3.2/src/pm/util/pmiserv.c:191: undefined reference to `MPL_internal_error_printf' > src/pm/util/libmpiexec.a(src_pm_util_libmpiexec_a-pmiserv.o): In function `fPMI_Handle_get_my_kvsname': > /builddir/build/BUILD/mpich-3.2/src/pm/util/pmiserv.c:770: undefined reference to `MPL_internal_error_printf' > src/pm/util/libmpiexec.a(src_pm_util_libmpiexec_a-pmiserv.o):/builddir/build/BUILD/mpich-3.2/src/pm/util/pmiserv.c:618: more undefined references to `MPL_internal_error_printf' follow > src/pm/util/libmpiexec.a(src_pm_util_libmpiexec_a-pmiport.o): In function `PMIServGetPort': > /builddir/build/BUILD/mpich-3.2/src/pm/util/pmiport.c:142: undefined reference to `MPL_internal_sys_error_printf' > src/pm/util/libmpiexec.a(src_pm_util_libmpiexec_a-pmiport.o): In function `PMIServSetupPort': > /builddir/build/BUILD/mpich-3.2/src/pm/util/pmiport.c:323: undefined reference to `MPL_internal_error_printf' > src/pm/util/libmpiexec.a(src_pm_util_libmpiexec_a-simple_pmiutil2.o): In function `PMIU_readline': > /builddir/build/BUILD/mpich-3.2/src/pm/util/simple_pmiutil2.c:124: undefined reference to `MPL_internal_error_printf' > collect2: error: ld returned 1 exit status > Makefile:19692: recipe for target 'src/pm/gforker/mpiexec.gforker' failed > > Any ideas? Full log is at http://in.waw.pl/~zbyszek/fedora/mpich-3.2-build.log . > > Zbyszek > _______________________________________________ > 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

building 3.2 fails
by Zbigniew Jędrzejewski-Szmek 16 Nov '15

16 Nov '15

Hi, I'm trying to compile mpich-3.2 on Fedora rawhide and it fails with the following: /bin/sh ./libtool --tag=FC --mode=compile gfortran -Isrc/binding/fortran/use_mpi -m64 -O2 -fPIC -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic -O2 -Jsrc/binding/fortran/use_mpi -c src/binding/fortran/use_mpi/mpi.f90 -o src/binding/fortran/use_mpi/mpi.lo libtool: link: gcc -m64 -O2 -fPIC -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic -O2 -Wl,-z -Wl,noexecstack -o src/pm/gforker/mpiexec.gforker src/pm/gforker/src_pm_gforker_mpiexec_gforker-mpiexec.o src/pm/util/libmpiexec.a -lpthread src/pm/gforker/src_pm_gforker_mpiexec_gforker-mpiexec.o: In function `mpiexec_usage': /builddir/build/BUILD/mpich-3.2/src/pm/gforker/mpiexec.c:283: undefined reference to `MPL_usage_printf' src/pm/util/libmpiexec.a(src_pm_util_libmpiexec_a-process.o): In function `MPIE_ExecProgram': /builddir/build/BUILD/mpich-3.2/src/pm/util/process.c:362: undefined reference to `MPL_internal_sys_error_printf' src/pm/util/libmpiexec.a(src_pm_util_libmpiexec_a-process.o): In function `MPIE_ForkProcesses': /builddir/build/BUILD/mpich-3.2/src/pm/util/process.c:173: undefined reference to `MPL_internal_error_printf' /builddir/build/BUILD/mpich-3.2/src/pm/util/process.c:155: undefined reference to `MPL_internal_error_printf' src/pm/util/libmpiexec.a(src_pm_util_libmpiexec_a-ioloop.o): In function `MPIE_IOLoop': /builddir/build/BUILD/mpich-3.2/src/pm/util/ioloop.c:191: undefined reference to `MPL_internal_sys_error_printf' src/pm/util/libmpiexec.a(src_pm_util_libmpiexec_a-pmiserv.o): In function `fPMIKVSAllocate': /builddir/build/BUILD/mpich-3.2/src/pm/util/pmiserv.c:461: undefined reference to `MPL_internal_error_printf' src/pm/util/libmpiexec.a(src_pm_util_libmpiexec_a-pmiserv.o): In function `PMISetupInClient': /builddir/build/BUILD/mpich-3.2/src/pm/util/pmiserv.c:175: undefined reference to `MPL_internal_error_printf' /builddir/build/BUILD/mpich-3.2/src/pm/util/pmiserv.c:185: undefined reference to `MPL_internal_error_printf' /builddir/build/BUILD/mpich-3.2/src/pm/util/pmiserv.c:191: undefined reference to `MPL_internal_error_printf' src/pm/util/libmpiexec.a(src_pm_util_libmpiexec_a-pmiserv.o): In function `fPMI_Handle_get_my_kvsname': /builddir/build/BUILD/mpich-3.2/src/pm/util/pmiserv.c:770: undefined reference to `MPL_internal_error_printf' src/pm/util/libmpiexec.a(src_pm_util_libmpiexec_a-pmiserv.o):/builddir/build/BUILD/mpich-3.2/src/pm/util/pmiserv.c:618: more undefined references to `MPL_internal_error_printf' follow src/pm/util/libmpiexec.a(src_pm_util_libmpiexec_a-pmiport.o): In function `PMIServGetPort': /builddir/build/BUILD/mpich-3.2/src/pm/util/pmiport.c:142: undefined reference to `MPL_internal_sys_error_printf' src/pm/util/libmpiexec.a(src_pm_util_libmpiexec_a-pmiport.o): In function `PMIServSetupPort': /builddir/build/BUILD/mpich-3.2/src/pm/util/pmiport.c:323: undefined reference to `MPL_internal_error_printf' src/pm/util/libmpiexec.a(src_pm_util_libmpiexec_a-simple_pmiutil2.o): In function `PMIU_readline': /builddir/build/BUILD/mpich-3.2/src/pm/util/simple_pmiutil2.c:124: undefined reference to `MPL_internal_error_printf' collect2: error: ld returned 1 exit status Makefile:19692: recipe for target 'src/pm/gforker/mpiexec.gforker' failed Any ideas? Full log is at http://in.waw.pl/~zbyszek/fedora/mpich-3.2-build.log . Zbyszek _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0