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

Re: [mpich-discuss] Problems with running make
by Junchao Zhang 28 Feb '14

28 Feb '14

I think is a bug to have a compiler named no :) Created a ticket at http://trac.mpich.org/projects/mpich/ticket/2048 --Junchao Zhang On Fri, Feb 28, 2014 at 4:54 PM, Reuti <reuti(a)staff.uni-marburg.de> wrote: > Am 28.02.2014 um 23:19 schrieb Gus Correa: > > > Hi Ron > > > > Your config.log shows that configure is picking up Gnu > > /usr/bin/f77 as the Fortran compiler. > > See an excerpt of config.log below. > > > > The Gnu f77/g77, which cannot compile Fortran-90 and later code. > > > > You may want to install gfortran. > > Configure didn't find gfortran. > > However, you can install it easily from RPM through yum. > > > > Once you install gfortran, to avoid picking up wrong compilers, > > you can also point configure to the compilers. > > Assuming you want to use all Gnu compilers, this would do it: > > > > ./configure CC=gcc, CXX=g++, F77=gfortran, FC=gfortran, > --prefix=/wherever/you/want ... > > > > Another possibility is follow Reuti's suggestion of > > not compiling the MPICH Fortran-90 interface. > > I just found, that --disable-fc is not working. Reason seems to be, that > it tries to make a conftest with the compiler "no" when checking Fortran 90 > integer kind: > > configure:39186: no -o conftest conftest.f >&5 > ./configure: line 2896: no: command not found > configure:39186: $? = 127 > configure: program exited with status 127 > configure: failed program was: > > -- Reuti > > [siehe angehängte Datei: config.log] > > I hope this helps, > > Gus Correa > > > > ******* from your config.log ********* > > ... > > configure:17977: result: no > > configure:17947: checking for gfortran > > configure:17977: result: no > > configure:17947: checking for f77 > > configure:17963: found /usr/bin/f77 > > configure:17974: result: f77 > > configure:18000: checking for Fortran 77 compiler version > > configure:18009: f77 --version >&5 > > GNU Fortran (GCC) 3.4.6 20060404 (Red Hat 3.4.6-19.el6) > > ... > > ***************************************** > > > > On 02/28/2014 05:02 AM, Reuti wrote: > >> Hi, > >> > >> Am 28.02.2014 um 09:22 schrieb Ron Palmer: > >> > >>> I am struggling with running make on MPICH, V3.1. I believe that > ./configure went well but I do not understand what caused the errors in > make. I thought it may be associated with the fortran compile but I have > F77 installed (though somewhat confused whether fortran 90 is also > installed). The README file suggested that I send an email to this list > with nominated four text files attached. > >> > >> You can try to skip f90: > >> > >> $ ./configure --disable-fc ... > >> > >> -- Reuti > >> > >> > >>> The end of the m.txt file is included here for easy access, full > details are attached... > >>> > >>> CC src/mpi/topo/nhb_alltoallw.lo > >>> CC src/binding/f90/create_f90_int.lo > >>> CC src/binding/f90/create_f90_real.lo > >>> src/binding/f90/create_f90_real.c: In function > 'PMPI_Type_create_f90_real': > >>> src/binding/f90/create_f90_real.c:73: error: expected expression > before ',' token > >>> src/binding/f90/create_f90_real.c:74: error: expected expression > before ',' token > >>> make[2]: *** [src/binding/f90/create_f90_real.lo] Error 1 > >>> make[2]: Leaving directory `/inv/mpich-3.1' > >>> make[1]: *** [all-recursive] Error 1 > >>> make[1]: Leaving directory `/inv/mpich-3.1' > >>> make: *** [all] Error 2 > >>> > >>> I look forward to any suggestions any of you may have. > >>> Regards, Ron > >>> > >>> > >>> <mpi_logs.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 > > > > _______________________________________________ > > 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] MPID_nem_tcp_init(377)... gethostbyname failed, mac (errno 1)
by Reuti 28 Feb '14

28 Feb '14

Am 28.02.2014 um 14:39 schrieb Luis Cebamanos: > Hi Pavan, > > Yes, that is the output: > > $ cat /etc/hosts > ## > # Host Database > # > # localhost is used to configure the loopback interface > # when the system is booting. Do not change this entry. > ## > 127.0.0.1 localhost > 255.255.255.255 broadcasthost > ::1 localhost > fe80::1%lo0 localhost What is the output of: $ nslookup localhost $ nslookup mac $ hostname AFAICS your machine has no domainname, otherwise it would show up in the MPICH error message after "mac". -- Reuti > On 28/02/14 13:35, Balaji, Pavan wrote: >> $ cat /etc/hosts >> >>## >> >># Host Database >> >># >> >># localhost is used to configure the loopback interface >> >># when the system is booting. Do not change this entry. >> >>## >> >>127.0.0.1 localhost >> >>255.255.255.255 broadcasthost >> >>::1 localhost >> >>fe80::1%lo0 localhost > > > -- > The University of Edinburgh is a charitable body, registered in > Scotland, with registration number SC005336. > > _______________________________________________ > 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] Problems with running make
by Rajeev Thakur 28 Feb '14

28 Feb '14

Not sure :-). But that's what I have used in the past. On Feb 28, 2014, at 5:17 PM, Reuti <reuti(a)staff.uni-marburg.de> wrote: > Am 01.03.2014 um 00:15 schrieb Rajeev Thakur: > >> Try "--disable-fc --disable-f77". > > Yes, this works. But is it intended to behave this way? > > -- Reuti > > >> Rajeev >> >> On Feb 28, 2014, at 4:54 PM, Reuti <reuti(a)staff.uni-marburg.de> >> wrote: >> >>> Am 28.02.2014 um 23:19 schrieb Gus Correa: >>> >>>> Hi Ron >>>> >>>> Your config.log shows that configure is picking up Gnu >>>> /usr/bin/f77 as the Fortran compiler. >>>> See an excerpt of config.log below. >>>> >>>> The Gnu f77/g77, which cannot compile Fortran-90 and later code. >>>> >>>> You may want to install gfortran. >>>> Configure didn't find gfortran. >>>> However, you can install it easily from RPM through yum. >>>> >>>> Once you install gfortran, to avoid picking up wrong compilers, >>>> you can also point configure to the compilers. >>>> Assuming you want to use all Gnu compilers, this would do it: >>>> >>>> ./configure CC=gcc, CXX=g++, F77=gfortran, FC=gfortran, --prefix=/wherever/you/want ... >>>> >>>> Another possibility is follow Reuti's suggestion of >>>> not compiling the MPICH Fortran-90 interface. >>> >>> I just found, that --disable-fc is not working. Reason seems to be, that it tries to make a conftest with the compiler "no" when checking Fortran 90 integer kind: >>> >>> configure:39186: no -o conftest conftest.f >&5 >>> ./configure: line 2896: no: command not found >>> configure:39186: $? = 127 >>> configure: program exited with status 127 >>> configure: failed program was: >>> >>> -- Reuti >>> >>> [siehe angehängte Datei: config.log] >>>> I hope this helps, >>>> Gus Correa >>>> >>>> ******* from your config.log ********* >>>> ... >>>> configure:17977: result: no >>>> configure:17947: checking for gfortran >>>> configure:17977: result: no >>>> configure:17947: checking for f77 >>>> configure:17963: found /usr/bin/f77 >>>> configure:17974: result: f77 >>>> configure:18000: checking for Fortran 77 compiler version >>>> configure:18009: f77 --version >&5 >>>> GNU Fortran (GCC) 3.4.6 20060404 (Red Hat 3.4.6-19.el6) >>>> ... >>>> ***************************************** >>>> >>>> On 02/28/2014 05:02 AM, Reuti wrote: >>>>> Hi, >>>>> >>>>> Am 28.02.2014 um 09:22 schrieb Ron Palmer: >>>>> >>>>>> I am struggling with running make on MPICH, V3.1. I believe that ./configure went well but I do not understand what caused the errors in make. I thought it may be associated with the fortran compile but I have F77 installed (though somewhat confused whether fortran 90 is also installed). The README file suggested that I send an email to this list with nominated four text files attached. >>>>> >>>>> You can try to skip f90: >>>>> >>>>> $ ./configure --disable-fc ... >>>>> >>>>> -- Reuti >>>>> >>>>> >>>>>> The end of the m.txt file is included here for easy access, full details are attached... >>>>>> >>>>>> CC src/mpi/topo/nhb_alltoallw.lo >>>>>> CC src/binding/f90/create_f90_int.lo >>>>>> CC src/binding/f90/create_f90_real.lo >>>>>> src/binding/f90/create_f90_real.c: In function 'PMPI_Type_create_f90_real': >>>>>> src/binding/f90/create_f90_real.c:73: error: expected expression before ',' token >>>>>> src/binding/f90/create_f90_real.c:74: error: expected expression before ',' token >>>>>> make[2]: *** [src/binding/f90/create_f90_real.lo] Error 1 >>>>>> make[2]: Leaving directory `/inv/mpich-3.1' >>>>>> make[1]: *** [all-recursive] Error 1 >>>>>> make[1]: Leaving directory `/inv/mpich-3.1' >>>>>> make: *** [all] Error 2 >>>>>> >>>>>> I look forward to any suggestions any of you may have. >>>>>> Regards, Ron >>>>>> >>>>>> >>>>>> <mpi_logs.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 >>>> >>>> _______________________________________________ >>>> 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 >>> <config.log> >> >> _______________________________________________ >> 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] Problems with running make
by Reuti 28 Feb '14

28 Feb '14

Am 01.03.2014 um 00:15 schrieb Rajeev Thakur: > Try "--disable-fc --disable-f77". Yes, this works. But is it intended to behave this way? -- Reuti > Rajeev > > On Feb 28, 2014, at 4:54 PM, Reuti <reuti(a)staff.uni-marburg.de> > wrote: > >> Am 28.02.2014 um 23:19 schrieb Gus Correa: >> >>> Hi Ron >>> >>> Your config.log shows that configure is picking up Gnu >>> /usr/bin/f77 as the Fortran compiler. >>> See an excerpt of config.log below. >>> >>> The Gnu f77/g77, which cannot compile Fortran-90 and later code. >>> >>> You may want to install gfortran. >>> Configure didn't find gfortran. >>> However, you can install it easily from RPM through yum. >>> >>> Once you install gfortran, to avoid picking up wrong compilers, >>> you can also point configure to the compilers. >>> Assuming you want to use all Gnu compilers, this would do it: >>> >>> ./configure CC=gcc, CXX=g++, F77=gfortran, FC=gfortran, --prefix=/wherever/you/want ... >>> >>> Another possibility is follow Reuti's suggestion of >>> not compiling the MPICH Fortran-90 interface. >> >> I just found, that --disable-fc is not working. Reason seems to be, that it tries to make a conftest with the compiler "no" when checking Fortran 90 integer kind: >> >> configure:39186: no -o conftest conftest.f >&5 >> ./configure: line 2896: no: command not found >> configure:39186: $? = 127 >> configure: program exited with status 127 >> configure: failed program was: >> >> -- Reuti >> >> [siehe angehängte Datei: config.log] >>> I hope this helps, >>> Gus Correa >>> >>> ******* from your config.log ********* >>> ... >>> configure:17977: result: no >>> configure:17947: checking for gfortran >>> configure:17977: result: no >>> configure:17947: checking for f77 >>> configure:17963: found /usr/bin/f77 >>> configure:17974: result: f77 >>> configure:18000: checking for Fortran 77 compiler version >>> configure:18009: f77 --version >&5 >>> GNU Fortran (GCC) 3.4.6 20060404 (Red Hat 3.4.6-19.el6) >>> ... >>> ***************************************** >>> >>> On 02/28/2014 05:02 AM, Reuti wrote: >>>> Hi, >>>> >>>> Am 28.02.2014 um 09:22 schrieb Ron Palmer: >>>> >>>>> I am struggling with running make on MPICH, V3.1. I believe that ./configure went well but I do not understand what caused the errors in make. I thought it may be associated with the fortran compile but I have F77 installed (though somewhat confused whether fortran 90 is also installed). The README file suggested that I send an email to this list with nominated four text files attached. >>>> >>>> You can try to skip f90: >>>> >>>> $ ./configure --disable-fc ... >>>> >>>> -- Reuti >>>> >>>> >>>>> The end of the m.txt file is included here for easy access, full details are attached... >>>>> >>>>> CC src/mpi/topo/nhb_alltoallw.lo >>>>> CC src/binding/f90/create_f90_int.lo >>>>> CC src/binding/f90/create_f90_real.lo >>>>> src/binding/f90/create_f90_real.c: In function 'PMPI_Type_create_f90_real': >>>>> src/binding/f90/create_f90_real.c:73: error: expected expression before ',' token >>>>> src/binding/f90/create_f90_real.c:74: error: expected expression before ',' token >>>>> make[2]: *** [src/binding/f90/create_f90_real.lo] Error 1 >>>>> make[2]: Leaving directory `/inv/mpich-3.1' >>>>> make[1]: *** [all-recursive] Error 1 >>>>> make[1]: Leaving directory `/inv/mpich-3.1' >>>>> make: *** [all] Error 2 >>>>> >>>>> I look forward to any suggestions any of you may have. >>>>> Regards, Ron >>>>> >>>>> >>>>> <mpi_logs.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 >>> >>> _______________________________________________ >>> 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 >> <config.log> > > _______________________________________________ > 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] Problems with running make
by Rajeev Thakur 28 Feb '14

28 Feb '14

Try "--disable-fc --disable-f77". Rajeev On Feb 28, 2014, at 4:54 PM, Reuti <reuti(a)staff.uni-marburg.de> wrote: > Am 28.02.2014 um 23:19 schrieb Gus Correa: > > > Hi Ron > > > > Your config.log shows that configure is picking up Gnu > > /usr/bin/f77 as the Fortran compiler. > > See an excerpt of config.log below. > > > > The Gnu f77/g77, which cannot compile Fortran-90 and later code. > > > > You may want to install gfortran. > > Configure didn't find gfortran. > > However, you can install it easily from RPM through yum. > > > > Once you install gfortran, to avoid picking up wrong compilers, > > you can also point configure to the compilers. > > Assuming you want to use all Gnu compilers, this would do it: > > > > ./configure CC=gcc, CXX=g++, F77=gfortran, FC=gfortran, --prefix=/wherever/you/want ... > > > > Another possibility is follow Reuti's suggestion of > > not compiling the MPICH Fortran-90 interface. > > I just found, that --disable-fc is not working. Reason seems to be, that it tries to make a conftest with the compiler "no" when checking Fortran 90 integer kind: > > configure:39186: no -o conftest conftest.f >&5 > ./configure: line 2896: no: command not found > configure:39186: $? = 127 > configure: program exited with status 127 > configure: failed program was: > > -- Reuti > > [siehe angehängte Datei: config.log] > > I hope this helps, > > Gus Correa > > > > ******* from your config.log ********* > > ... > > configure:17977: result: no > > configure:17947: checking for gfortran > > configure:17977: result: no > > configure:17947: checking for f77 > > configure:17963: found /usr/bin/f77 > > configure:17974: result: f77 > > configure:18000: checking for Fortran 77 compiler version > > configure:18009: f77 --version >&5 > > GNU Fortran (GCC) 3.4.6 20060404 (Red Hat 3.4.6-19.el6) > > ... > > ***************************************** > > > > On 02/28/2014 05:02 AM, Reuti wrote: > >> Hi, > >> > >> Am 28.02.2014 um 09:22 schrieb Ron Palmer: > >> > >>> I am struggling with running make on MPICH, V3.1. I believe that ./configure went well but I do not understand what caused the errors in make. I thought it may be associated with the fortran compile but I have F77 installed (though somewhat confused whether fortran 90 is also installed). The README file suggested that I send an email to this list with nominated four text files attached. > >> > >> You can try to skip f90: > >> > >> $ ./configure --disable-fc ... > >> > >> -- Reuti > >> > >> > >>> The end of the m.txt file is included here for easy access, full details are attached... > >>> > >>> CC src/mpi/topo/nhb_alltoallw.lo > >>> CC src/binding/f90/create_f90_int.lo > >>> CC src/binding/f90/create_f90_real.lo > >>> src/binding/f90/create_f90_real.c: In function 'PMPI_Type_create_f90_real': > >>> src/binding/f90/create_f90_real.c:73: error: expected expression before ',' token > >>> src/binding/f90/create_f90_real.c:74: error: expected expression before ',' token > >>> make[2]: *** [src/binding/f90/create_f90_real.lo] Error 1 > >>> make[2]: Leaving directory `/inv/mpich-3.1' > >>> make[1]: *** [all-recursive] Error 1 > >>> make[1]: Leaving directory `/inv/mpich-3.1' > >>> make: *** [all] Error 2 > >>> > >>> I look forward to any suggestions any of you may have. > >>> Regards, Ron > >>> > >>> > >>> <mpi_logs.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 > > > > _______________________________________________ > > 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 > <config.log>

1 0

Re: [mpich-discuss] Problems with running make
by Reuti 28 Feb '14

28 Feb '14

Am 28.02.2014 um 23:19 schrieb Gus Correa: > Hi Ron > > Your config.log shows that configure is picking up Gnu > /usr/bin/f77 as the Fortran compiler. > See an excerpt of config.log below. > > The Gnu f77/g77, which cannot compile Fortran-90 and later code. > > You may want to install gfortran. > Configure didn't find gfortran. > However, you can install it easily from RPM through yum. > > Once you install gfortran, to avoid picking up wrong compilers, > you can also point configure to the compilers. > Assuming you want to use all Gnu compilers, this would do it: > > ./configure CC=gcc, CXX=g++, F77=gfortran, FC=gfortran, --prefix=/wherever/you/want ... > > Another possibility is follow Reuti's suggestion of > not compiling the MPICH Fortran-90 interface. I just found, that --disable-fc is not working. Reason seems to be, that it tries to make a conftest with the compiler "no" when checking Fortran 90 integer kind: configure:39186: no -o conftest conftest.f >&5 ./configure: line 2896: no: command not found configure:39186: $? = 127 configure: program exited with status 127 configure: failed program was: -- Reuti [siehe angehängte Datei: config.log] > I hope this helps, > Gus Correa > > ******* from your config.log ********* > ... > configure:17977: result: no > configure:17947: checking for gfortran > configure:17977: result: no > configure:17947: checking for f77 > configure:17963: found /usr/bin/f77 > configure:17974: result: f77 > configure:18000: checking for Fortran 77 compiler version > configure:18009: f77 --version >&5 > GNU Fortran (GCC) 3.4.6 20060404 (Red Hat 3.4.6-19.el6) > ... > ***************************************** > > On 02/28/2014 05:02 AM, Reuti wrote: >> Hi, >> >> Am 28.02.2014 um 09:22 schrieb Ron Palmer: >> >>> I am struggling with running make on MPICH, V3.1. I believe that ./configure went well but I do not understand what caused the errors in make. I thought it may be associated with the fortran compile but I have F77 installed (though somewhat confused whether fortran 90 is also installed). The README file suggested that I send an email to this list with nominated four text files attached. >> >> You can try to skip f90: >> >> $ ./configure --disable-fc ... >> >> -- Reuti >> >> >>> The end of the m.txt file is included here for easy access, full details are attached... >>> >>> CC src/mpi/topo/nhb_alltoallw.lo >>> CC src/binding/f90/create_f90_int.lo >>> CC src/binding/f90/create_f90_real.lo >>> src/binding/f90/create_f90_real.c: In function 'PMPI_Type_create_f90_real': >>> src/binding/f90/create_f90_real.c:73: error: expected expression before ',' token >>> src/binding/f90/create_f90_real.c:74: error: expected expression before ',' token >>> make[2]: *** [src/binding/f90/create_f90_real.lo] Error 1 >>> make[2]: Leaving directory `/inv/mpich-3.1' >>> make[1]: *** [all-recursive] Error 1 >>> make[1]: Leaving directory `/inv/mpich-3.1' >>> make: *** [all] Error 2 >>> >>> I look forward to any suggestions any of you may have. >>> Regards, Ron >>> >>> >>> <mpi_logs.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 > > _______________________________________________ > 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] Problems with running make
by Gus Correa 28 Feb '14

28 Feb '14

Hi Ron Your config.log shows that configure is picking up Gnu /usr/bin/f77 as the Fortran compiler. See an excerpt of config.log below. The Gnu f77/g77, which cannot compile Fortran-90 and later code. You may want to install gfortran. Configure didn't find gfortran. However, you can install it easily from RPM through yum. Once you install gfortran, to avoid picking up wrong compilers, you can also point configure to the compilers. Assuming you want to use all Gnu compilers, this would do it: ./configure CC=gcc, CXX=g++, F77=gfortran, FC=gfortran, --prefix=/wherever/you/want ... Another possibility is follow Reuti's suggestion of not compiling the MPICH Fortran-90 interface. I hope this helps, Gus Correa ******* from your config.log ********* ... configure:17977: result: no configure:17947: checking for gfortran configure:17977: result: no configure:17947: checking for f77 configure:17963: found /usr/bin/f77 configure:17974: result: f77 configure:18000: checking for Fortran 77 compiler version configure:18009: f77 --version >&5 GNU Fortran (GCC) 3.4.6 20060404 (Red Hat 3.4.6-19.el6) ... ***************************************** On 02/28/2014 05:02 AM, Reuti wrote: > Hi, > > Am 28.02.2014 um 09:22 schrieb Ron Palmer: > >> I am struggling with running make on MPICH, V3.1. I believe that ./configure went well but I do not understand what caused the errors in make. I thought it may be associated with the fortran compile but I have F77 installed (though somewhat confused whether fortran 90 is also installed). The README file suggested that I send an email to this list with nominated four text files attached. > > You can try to skip f90: > > $ ./configure --disable-fc ... > > -- Reuti > > >> The end of the m.txt file is included here for easy access, full details are attached... >> >> CC src/mpi/topo/nhb_alltoallw.lo >> CC src/binding/f90/create_f90_int.lo >> CC src/binding/f90/create_f90_real.lo >> src/binding/f90/create_f90_real.c: In function 'PMPI_Type_create_f90_real': >> src/binding/f90/create_f90_real.c:73: error: expected expression before ',' token >> src/binding/f90/create_f90_real.c:74: error: expected expression before ',' token >> make[2]: *** [src/binding/f90/create_f90_real.lo] Error 1 >> make[2]: Leaving directory `/inv/mpich-3.1' >> make[1]: *** [all-recursive] Error 1 >> make[1]: Leaving directory `/inv/mpich-3.1' >> make: *** [all] Error 2 >> >> I look forward to any suggestions any of you may have. >> Regards, Ron >> >> >> <mpi_logs.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

Checks for buffer aliasing in coll ops?
by Carsten Clauss 28 Feb '14

28 Feb '14

Constantly, our users step into the common trap of aliasing send and receive buffers e.g. in (All)Gather(v) instead of using MPI_IN_PLACE. Although these cases are frequently caught by lower-level memcpy() checks within MPICH, I wonder if it would be feasible to do so already in the upper MPI layer, e.g. by using MPIR_ERRTEST_ALIAS_COLL() in a more comprehensive manner. IMHO it would be nice to extend the check e.g. in MPI_(All)Gather() from /* catch common aliasing cases */ if (recvbuf != MPI_IN_PLACE && sendtype == recvtype && sendcount == recvcount && sendcount != 0) MPIR_ERRTEST_ALIAS_COLL(sendbuf,recvbuf,mpi_errno); -- that would only take effect for root=0 -- to let's say: /* catch common aliasing cases */ MPID_Datatype_get_size_macro(recvtype, recvtype_size); if (recvbuf != MPI_IN_PLACE && sendtype == recvtype && sendcount == recvcount && sendcount != 0) MPIR_ERRTEST_ALIAS_COLL(sendbuf, (char*)recvbuf + comm_ptr->rank*recvcount*recvtype_size, mpi_errno); And the same for MPI_(All)Gatherv() (which currently do not check for aliasing at all): /* catch common aliasing cases */ MPID_Datatype_get_size_macro(recvtype, recvtype_size); if (sendbuf != MPI_IN_PLACE && sendtype == recvtype && recvcounts[comm_ptr->rank] != 0 && sendcount != 0) MPIR_ERRTEST_ALIAS_COLL(sendbuf, (char*)recvbuf + displs[comm_ptr->rank]*recvtype_size, mpi_errno); I think this would lead to much more understandable error messages ("PMPI_Gatherv(363): Buffers must not be aliased" vs. "memcpy argument memory ranges overlap") -- or is there something that speaks against this kind of checks? With kind regards, C. Clauss -- Carsten Clauss Possartstrasse 20 D-81679 Muenchen www.par-tec.com _____________________________________ ParTec Cluster Competence Center GmbH Geschï¿½ftsfï¿½hrer RA. Dipl.-Ing. Bernhard Frohwitter Eingetragen beim Amtsgericht Mï¿½nchen HRB 151545 Steuer-Nr. 08/32305, Ust-ID DE235527064

1 0

Re: [mpich-discuss] MPID_nem_tcp_init(377)... gethostbyname failed, mac (errno 1)
by Luis Cebamanos 28 Feb '14

28 Feb '14

Hi Pavan, Yes, that is the output: $ cat /etc/hosts ## # Host Database # # localhost is used to configure the loopback interface # when the system is booting. Do not change this entry. ## 127.0.0.1 localhost 255.255.255.255 broadcasthost ::1 localhost fe80::1%lo0 localhost On 28/02/14 13:35, Balaji, Pavan wrote: > $ cat /etc/hosts > >>## > >># Host Database > >># > >># localhost is used to configure the loopback interface > >># when the system is booting. Do not change this entry. > >>## > >>127.0.0.1 localhost > >>255.255.255.255 broadcasthost > >>::1 localhost > >>fe80::1%lo0 localhost -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.

1 0

Re: [mpich-discuss] MPID_nem_tcp_init(377)... gethostbyname failed, mac (errno 1)
by Balaji, Pavan 28 Feb '14

28 Feb '14

Your mac doesn’t seem to know “localhost”. Did you check if your /etc/hosts file? — Pavan On Feb 28, 2014, at 6:50 AM, Luis Cebamanos <l.cebamanos(a)epcc.ed.ac.uk> wrote: > Hi, > > I have also tried the following, with similar result: > > > $ mpiexec -n 1 -host localhost ./hello > [mpiexec@mac] HYDU_sock_is_local (utils/sock/sock.c:532): gethostbyname error on mac: Unknown host > [mpiexec@mac] main (ui/mpich/mpiexec.c:291): unable to check if localhost is local > > thought it could add some more info. > > Cheers, > Luis > > > > On 28 Feb 2014, at 12:25, Luis Cebamanos <l.cebamanos(a)epcc.ed.ac.uk> wrote: > >> Hi all, >> >> I have installed MPICH2 in a Mac 10.9.2 using homebrew. The installation process went OK, no problems were reported. Then I created a small hello world example just to test the MPI: >> >> #include <stdio.h> >> #include "mpi.h" >> >> int main (argc, argv) >> int argc; >> char *argv[]; >> { >> int rank, size; >> >> MPI_Init (&argc, &argv);/* starts MPI */ >> MPI_Comm_rank (MPI_COMM_WORLD, &rank);/* get current process id */ >> MPI_Comm_size (MPI_COMM_WORLD, &size);/* get number of processes */ >> >> printf( "Hello world from process %d of %d\n", rank, size ); >> >> MPI_Finalize(); >> return 0; >> } >> >> compile it ($mpicc -o hello hello.c), all went fine too; and finally run it ($mpiexec -n 2 ./hello). However, that is the problem reported by mpiexec: >> >> $ mpiexec -n 2 ./hello >> Fatal error in MPI_Init: Other MPI error, error stack: >> MPIR_Init_thread(467)..............: >> MPID_Init(177).....................: channel initialization failed >> MPIDI_CH3_Init(70).................: >> MPID_nem_init(319).................: >> MPID_nem_tcp_init(171).............: >> MPID_nem_tcp_get_business_card(418): >> MPID_nem_tcp_init(377).............: gethostbyname failed, mac (errno 1) >> Fatal error in MPI_Init: Other MPI error, error stack: >> MPIR_Init_thread(467)..............: >> MPID_Init(177).....................: channel initialization failed >> MPIDI_CH3_Init(70).................: >> MPID_nem_init(319).................: >> MPID_nem_tcp_init(171).............: >> MPID_nem_tcp_get_business_card(418): >> MPID_nem_tcp_init(377).............: gethostbyname failed, mac (errno 1) >> >> =================================================================================== >> = BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES >> = PID 653 RUNNING AT mac >> = EXIT CODE: 1 >> = CLEANING UP REMAINING PROCESSES >> = YOU CAN IGNORE THE BELOW CLEANUP MESSAGES >> =================================================================================== >> >> The version installed: >> $ mpichversion >> MPICH Version: 3.1 >> MPICH Release date: Thu Feb 20 11:41:13 CST 2014 >> MPICH Device: ch3:nemesis >> MPICH configure: --disable-dependency-tracking --disable-silent-rules --prefix=/usr/local/Cellar/mpich2/3.1 --mandir=/usr/local/Cellar/mpich2/3.1/share/man >> MPICH CC: clang -O2 >> MPICH CXX: clang++ >> MPICH F77: /usr/local/bin/gfortran -O2 >> MPICH FC: /usr/local/bin/gfortran >> >> Does anyone have any idea of why I am getting this error? The hostname command is also working fine, so I do NOT understand this problem. Furthermore, the idea is to run MPICH2 on my mac, not in a cluster so it should be straightforward to pick the hostname. My /etc/hosts shows the following: >> $ cat /etc/hosts >> ## >> # Host Database >> # >> # localhost is used to configure the loopback interface >> # when the system is booting. Do not change this entry. >> ## >> 127.0.0.1 localhost >> 255.255.255.255 broadcasthost >> ::1 localhost >> fe80::1%lo0 localhost >> >> Any ideas? Any help, suggestions or workarounds would be much appreciated. >> >> Best regards, >> LuisThe University of Edinburgh is a charitable body, registered in >> Scotland, with registration number SC005336. >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss > > The University of Edinburgh is a charitable body, registered in > Scotland, with registration number SC005336. > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss

1 0