July 2018 - discuss - mailman3.cels.anl.gov

Re: [mpich-discuss] Building MPICH 3.2.1 with Sun Studio 12.5
by Min Si 31 Jul '18

31 Jul '18

Hi Mike, Could you please try a newer release (e.g., mpich-3.3b3) ? This looks like a cherry-picking mistake when we made the 3.2.1 release. The alignment fix commit (c3bb71e) was made after the commit that introduces MPIR_Memcpy, but only the alignment commit was picked into 3.2.1. Best regards, Min On 2018/07/31 9:01, Michael Pulverenti wrote: > Hi, > I did some more digging at it appears the call to the unresolved function MPIR_Memcpy was introduced in 2016 by Changeset https://trac.mpich.org/projects/mpich/changeset/c3bb71e72f88034ce7ebcc68144…. > > Can anyone confirm they have built MPICH 3.2.1 on SPARC with Sun Studio, and if so, if/how they resolved the call to MPIR_Memcpy that appears in src/mpid/ch3/channels/nemesis/src/ch3_progress.c? > > Thanks for any help. > --Mike > > > -----Original Message----- > From: discuss-request(a)mpich.org <discuss-request(a)mpich.org> > Sent: Tuesday, July 24, 2018 12:00 PM > To: discuss(a)mpich.org > Subject: discuss Digest, Vol 69, Issue 13 > > Send discuss mailing list submissions to > discuss(a)mpich.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.mpich.org/mailman/listinfo/discuss > or, via email, send a message with subject or body 'help' to > discuss-request(a)mpich.org > > You can reach the person managing the list at > discuss-owner(a)mpich.org > > When replying, please edit your Subject line so it is more specific than "Re: Contents of discuss digest..." > > > Today's Topics: > > 1. Building MPICH 3.2.1 with Sun Studio 12.5 (Michael Pulverenti) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 24 Jul 2018 13:30:11 +0000 > From: Michael Pulverenti <Michael.Pulverenti(a)roguewave.com> > To: "discuss(a)mpich.org" <discuss(a)mpich.org> > Subject: [mpich-discuss] Building MPICH 3.2.1 with Sun Studio 12.5 > Message-ID: > <SN6PR02MB417551F2DB6679E20440811C8D550(a)SN6PR02MB4175.namprd02.prod.outlook.com> > > Content-Type: text/plain; charset="us-ascii" > > Hi, > I'm having trouble building MPICH 3.2.1 and I'm hoping for some help resolving the problem(s). Perhaps someone has seen this before. > > The environment is: > % uname -a > SunOS spc64sol113ci 5.11 11.3 sun4v sparc sun4v % f95 -V > f90: Studio 12.5 Fortran 95 8.8 SunOS_sparc 2016/05/31 > > The config command I used is: > % ./configure --prefix=/export/home4/erhome/jenkins/michaelp/ports/fnl/sol113/mpi/build_area/Mikes_build CC=cc CXX=CC F77=f77 FC=f95 CFLAGS=-m64 CXXFLAGS=-m64 FFLAGS=-m64 FCFLAGS=-m64 LDFLAGS=-m64 > > Looking at the output from running mpich-3.2.1/make, it appears the problem is an unresolved symbol MPIR_Memcpy: > CCLD src/env/mpichversion > Undefined first referenced > symbol in file > MPIR_Memcpy lib/.libs/libmpi.a(lib_libmpi_la-ch3_progress.o) > ld: fatal: symbol referencing errors > *** Error code 2 > The following command caused the error: > echo " CCLD " src/env/mpichversion;/bin/sh ./libtool --silent --tag=CC --mode=link cc -m64 -O2 -static -m64 -o src/env/mpichversion src/env/mpichversion.o lib/libmpi.la -lnsl -lsocket -lpthread > make: Fatal error: Command failed for target `src/env/mpichversion' > > > I can provide the full output from my config and make commands if that helps, but I didn't want to overload my first email to this mail group. > > Thanks for any help you are able to provide, --Mike >

1 0

Re: [mpich-discuss] Building MPICH 3.2.1 with Sun Studio 12.5
by Michael Pulverenti 31 Jul '18

31 Jul '18

Hi, I did some more digging at it appears the call to the unresolved function MPIR_Memcpy was introduced in 2016 by Changeset https://trac.mpich.org/projects/mpich/changeset/c3bb71e72f88034ce7ebcc68144…. Can anyone confirm they have built MPICH 3.2.1 on SPARC with Sun Studio, and if so, if/how they resolved the call to MPIR_Memcpy that appears in src/mpid/ch3/channels/nemesis/src/ch3_progress.c? Thanks for any help. --Mike -----Original Message----- From: discuss-request(a)mpich.org <discuss-request(a)mpich.org> Sent: Tuesday, July 24, 2018 12:00 PM To: discuss(a)mpich.org Subject: discuss Digest, Vol 69, Issue 13 Send discuss mailing list submissions to discuss(a)mpich.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.mpich.org/mailman/listinfo/discuss or, via email, send a message with subject or body 'help' to discuss-request(a)mpich.org You can reach the person managing the list at discuss-owner(a)mpich.org When replying, please edit your Subject line so it is more specific than "Re: Contents of discuss digest..." Today's Topics: 1. Building MPICH 3.2.1 with Sun Studio 12.5 (Michael Pulverenti) ---------------------------------------------------------------------- Message: 1 Date: Tue, 24 Jul 2018 13:30:11 +0000 From: Michael Pulverenti <Michael.Pulverenti(a)roguewave.com> To: "discuss(a)mpich.org" <discuss(a)mpich.org> Subject: [mpich-discuss] Building MPICH 3.2.1 with Sun Studio 12.5 Message-ID: <SN6PR02MB417551F2DB6679E20440811C8D550(a)SN6PR02MB4175.namprd02.prod.outlook.com> Content-Type: text/plain; charset="us-ascii" Hi, I'm having trouble building MPICH 3.2.1 and I'm hoping for some help resolving the problem(s). Perhaps someone has seen this before. The environment is: % uname -a SunOS spc64sol113ci 5.11 11.3 sun4v sparc sun4v % f95 -V f90: Studio 12.5 Fortran 95 8.8 SunOS_sparc 2016/05/31 The config command I used is: % ./configure --prefix=/export/home4/erhome/jenkins/michaelp/ports/fnl/sol113/mpi/build_area/Mikes_build CC=cc CXX=CC F77=f77 FC=f95 CFLAGS=-m64 CXXFLAGS=-m64 FFLAGS=-m64 FCFLAGS=-m64 LDFLAGS=-m64 Looking at the output from running mpich-3.2.1/make, it appears the problem is an unresolved symbol MPIR_Memcpy: CCLD src/env/mpichversion Undefined first referenced symbol in file MPIR_Memcpy lib/.libs/libmpi.a(lib_libmpi_la-ch3_progress.o) ld: fatal: symbol referencing errors *** Error code 2 The following command caused the error: echo " CCLD " src/env/mpichversion;/bin/sh ./libtool --silent --tag=CC --mode=link cc -m64 -O2 -static -m64 -o src/env/mpichversion src/env/mpichversion.o lib/libmpi.la -lnsl -lsocket -lpthread make: Fatal error: Command failed for target `src/env/mpichversion' I can provide the full output from my config and make commands if that helps, but I didn't want to overload my first email to this mail group. Thanks for any help you are able to provide, --Mike

1 0

Re: [mpich-discuss] Problems building mpich-3.2.1 with PGI 18.4 Community Edition
by Jeff Layton 27 Jul '18

27 Jul '18

Apologies for a very late reply (too much travel). I will talk to PGI about this and see what they have to say. I'll report back if I learn anything. Thanks! Jeff > The problem exists in PGI 18 but not PGI 17. This seems like a PGI > bug rather than an MPICH one. > > Jeff > > On Fri, Jul 20, 2018 at 8:24 AM, Jeff Layton <laytonjb(a)att.net > <mailto:[email protected]>> wrote: > > I fixed this problem and I get the exact same error. Again, I > grepped config.log and found the following. > > > $ grep -i error config.log > pgcc-Error-Unknown switch: -qversion > PGC/x86-64 Linux 18.4-0: compilation completed with severe errors > PGC-S-0035-Syntax error: Recovery attempted by replacing > identifier error by ';' (conftest.c: 14) > PGC/x86-64 Linux 18.4-0: compilation completed with severe errors > | Syntax error > PGC-S-0035-Syntax error: Recovery attempted by replacing > identifier error by ';' (conftest.c: 14) > PGC/x86-64 Linux 18.4-0: compilation completed with severe errors > | Syntax error > configure:5951: error: in `/home/laytonjb/src/mpich-3.2.1': > configure:5953: error: C preprocessor > "/opt/pgi/linux86-64/18.4/bin/pgcc" fails sanity check > HAVE_ERROR_CHECKING='' > MPI_MAX_ERROR_STRING='' > > > > I'm not an expert but it looks like configure sends an unknown > option to pgcc (-qversion). Then there appear to be some problems > in mpich when built with pgcc. > > Any comments or thoughts? > > Thanks! > > Jeff > > >> Dooh. Thanks - I'll try this and see what happens. >> >> Thanks! >> >> Jeff >> >>>> Am 19.07.2018 um 01:19 schrieb Jeff Layton <laytonjb(a)att.net> >>>> <mailto:[email protected]>: >>>> >>>> Hello, >>>> >>>> I'm trying to build mpich-3.2.1 with the PGI 18.4 Community >>>> Edition compilers. However, I get an error when running >>>> configure. The configure line is, >>>> >>>> ./configure --prefix=/home/laytonjb/bin/pgi-18.4-mpich-3.2.1 >>>> >>>> The error I get is, >>>> >>>> [laytonjb@laytonjb-Lenovo-G50-45 mpich-3.2.1]$ ./conf.jeff >>>> Configuring MPICH version 3.2.1 with >>>> '--prefix=/home/laytonjb/bin/pgi-18.4-mpich-3.2.1' >>>> 'CC=/opt/pgi/linux86-64/18.4/bin/pgcc' >>>> 'CPP=/opt/pgi/linux86-64/18.4/bin/pgcc' >>>> 'CXX=/opt/pgi/linux86-64/18.4/bin/pgg++' >>>> 'FC=/opt/pgi/linux86-64/18.4/bin/pgfortran' >>> pgg++ seems to be typo, duno whether this is related. >>> >>> -- Reuti >>> >>> >>>> 'F77=/opt/pgi/linux86-64/18.4/bin/pgf77' >>>> Running on system: Linux laytonjb-Lenovo-G50-45 >>>> 3.10.0-693.17.1.el7.x86_64 #1 SMP Thu Jan 25 20:13:58 UTC 2018 >>>> x86_64 x86_64 x86_64 GNU/Linux >>>> checking whether the C compiler works... yes >>>> checking for C compiler default output file name... a.out >>>> checking for suffix of executables... >>>> checking whether we are cross compiling... no >>>> checking for suffix of object files... o >>>> checking whether we are using the GNU C compiler... no >>>> checking whether /opt/pgi/linux86-64/18.4/bin/pgcc accepts >>>> -g... yes >>>> checking for /opt/pgi/linux86-64/18.4/bin/pgcc option to accept >>>> ISO C89... none needed >>>> checking whether /opt/pgi/linux86-64/18.4/bin/pgcc understands >>>> -c and -o together... yes >>>> checking how to run the C preprocessor... >>>> /opt/pgi/linux86-64/18.4/bin/pgcc >>>> configure: error: in `/home/laytonjb/src/mpich-3.2.1': >>>> configure: error: C preprocessor >>>> "/opt/pgi/linux86-64/18.4/bin/pgcc" fails sanity check >>>> See `config.log' for more details >>>> >>>> I've briefly looked through the config.log and this is all that >>>> stands out: >>>> >>>> >>>> $ grep -i error config.log >>>> pgcc-Error-Unknown switch: -qversion >>>> PGC/x86-64 Linux 18.4-0: compilation completed with severe errors >>>> PGC-S-0035-Syntax error: Recovery attempted by replacing >>>> identifier error by ';' (conftest.c: 14) >>>> PGC/x86-64 Linux 18.4-0: compilation completed with severe errors >>>> | Syntax error >>>> PGC-S-0035-Syntax error: Recovery attempted by replacing >>>> identifier error by ';' (conftest.c: 14) >>>> PGC/x86-64 Linux 18.4-0: compilation completed with severe errors >>>> | Syntax error >>>> configure:5951: error: in `/home/laytonjb/src/mpich-3.2.1': >>>> configure:5953: error: C preprocessor >>>> "/opt/pgi/linux86-64/18.4/bin/pgcc" fails sanity check >>>> HAVE_ERROR_CHECKING='' >>>> MPI_MAX_ERROR_STRING='' >>>> >>>> I'm not sure how to fix this error. I've attached the >>>> config.log file in case this helps. >>>> >>>> Thanks for any and all help. >>>> >>>> Jeff >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> <config.log>_______________________________________________ >>>> discuss mailing list discuss(a)mpich.org <mailto:[email protected]> >>>> To manage subscription options or unsubscribe: >>>> https://lists.mpich.org/mailman/listinfo/discuss >>>> <https://lists.mpich.org/mailman/listinfo/discuss> >>> >> >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org <mailto:[email protected]> >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss >> <https://lists.mpich.org/mailman/listinfo/discuss> >> > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org <mailto:[email protected]> > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > <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 > 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

Unexplainable stall with MPI ports
by Florian Lindner 26 Jul '18

26 Jul '18

Hello, I have a unexplainable behavior with an application that uses MPI ports. The entire test application is available at https://github.com/floli/MPI_Ports (dependencies: cmake, boost). MPICH is 3.2.1 and Arch Linux Everything is about mpiports.cpp, launched with /mpirun -n 4 ./mpiports -p A --peers 2 --commType many resp. -p B unfortunately, the issue does not occur with less ranks an it always does not appear every time... :-/ if (options.participant == A) { // receives connections if (options.commType == many) { portName = lookupPort(options, rank); // gets the port address, always the same for one rank for (auto r : comRanks) { // the ranks that connect to me MPI_Comm icomm; INFO << "Accepting connection on " << portName; DEBUG << "SIZE = " << portName.size(); MPI_Comm_accept(portName.c_str(), MPI_INFO_NULL, 0, MPI_COMM_SELF, &icomm); // <- Rank 1, participant A stops here DEBUG << "Accepted connection on " << portName; DEBUG << "icomm size = " << getRemoteCommSize(icomm); int connectedRank = -1; MPI_Recv(&connectedRank, 1, MPI_INT, 0, MPI_ANY_TAG, icomm, MPI_STATUS_IGNORE); MPI_Send(&rank, 1, MPI_INT, 0, 0, icomm); DEBUG << "Received rank number " << connectedRank; comms[connectedRank] = icomm; } } } if (options.participant == B) { // connects to the intercomms sleep(1000); if (options.commType == many) { for (auto r : comRanks) { // the ranks I connect to MPI_Comm icomm; portName = lookupPort(options, r); // reads ports for connecting to rank r INFO << "Connecting to rank " << r << " on " << portName; MPI_Comm_connect(portName.c_str(), MPI_INFO_NULL, 0, MPI_COMM_SELF, &icomm); DEBUG << "icomm size = " << getRemoteCommSize(icomm); DEBUG << "Connected to rank " << r << " on " << portName; MPI_Send(&rank, 1, MPI_INT, 0, 0, icomm); int connectedRank = -1; MPI_Recv(&connectedRank, 1, MPI_INT, 0, MPI_ANY_TAG, icomm, MPI_STATUS_IGNORE); // <- Rank 0,1 participant B stop here comms[connectedRank] = icomm; } } } I wrote down my observations on where the ranks stop: | Particpant | Rank | Where | comRanks | Port | comms | |------------+------+--------------------+----------+-------+-------| | A | 0 | Start dataExchange | [0,1] | 39741 | [0,1] | | A | 1 | Accept | [0,1,2] | 48187 | [2] | | A | 2 | Start dataExchange | [2,3] | 35863 | [2,3] | | A | 3 | Start dataExchange | [3] | 39791 | [3] | | | | | | | | | B | 0 | Recv connectedRank | [0,1] | 39741 | [] | | B | 1 | Recv connectedRank | [0,1] | 39741 | [] | | B | 2 | Start dataExchange | [1,2] | 35863 | [1,2] | | B | 3 | Start dataExchange | [2,3] | 39791 | [2,3] | comRanks on A means: Ranks (on the other participant) that connect to be comRanks on B means: Rank I connect to Start dataexchange is an MPI_Barrier, it's located below the code I have pasted here. It seems that Rank A,0 successfully received the connectRank = 0, 1 from B,0 and B,1 and also the Send operations returned. However, B,0 and B,1 both connected to rank 0 (as seen by the identical port number). Also, A,1 waits for incoming connections, only B,2 has connected so far. Of course, since B,0 and B,1 wait to receiving connectedRank from A,0. I know, that's a lot to ask, but I would be very grateful, if you would have a look and could provide hints on what is going wrong here... Thanks! Florian _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Building MPICH 3.2.1 with Sun Studio 12.5
by Michael Pulverenti 24 Jul '18

24 Jul '18

Hi, I'm having trouble building MPICH 3.2.1 and I'm hoping for some help resolving the problem(s). Perhaps someone has seen this before. The environment is: % uname -a SunOS spc64sol113ci 5.11 11.3 sun4v sparc sun4v % f95 -V f90: Studio 12.5 Fortran 95 8.8 SunOS_sparc 2016/05/31 The config command I used is: % ./configure --prefix=/export/home4/erhome/jenkins/michaelp/ports/fnl/sol113/mpi/build_area/Mikes_build CC=cc CXX=CC F77=f77 FC=f95 CFLAGS=-m64 CXXFLAGS=-m64 FFLAGS=-m64 FCFLAGS=-m64 LDFLAGS=-m64 Looking at the output from running mpich-3.2.1/make, it appears the problem is an unresolved symbol MPIR_Memcpy: CCLD src/env/mpichversion Undefined first referenced symbol in file MPIR_Memcpy lib/.libs/libmpi.a(lib_libmpi_la-ch3_progress.o) ld: fatal: symbol referencing errors *** Error code 2 The following command caused the error: echo " CCLD " src/env/mpichversion;/bin/sh ./libtool --silent --tag=CC --mode=link cc -m64 -O2 -static -m64 -o src/env/mpichversion src/env/mpichversion.o lib/libmpi.la -lnsl -lsocket -lpthread make: Fatal error: Command failed for target `src/env/mpichversion' I can provide the full output from my config and make commands if that helps, but I didn't want to overload my first email to this mail group. Thanks for any help you are able to provide, --Mike _______________________________________________ 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 building mpich-3.2.1 with PGI 18.4 Community Edition
by Reuti 20 Jul '18

20 Jul '18

> Am 21.07.2018 um 00:25 schrieb Gus Correa <gus(a)ldeo.columbia.edu>: > > Hi Reuti > > I haven't used PGI in a long while, never PGI 18, > so forgive my wild guess. > Older versions didn't have the --version flag, it was -V. > > The -noswitcherror was a blanket to avoid errors > with any unknown switch, which were simply ignored. > A dirty trick, but sometimes it worked. > I don't even know if it still exists in PGI 18, does it? Yes. -- Reuti > Whether using it is a wise choice in this case, I really don't know, > it depends on whether the compiler version (that the > Intel-ish '-qversion' in the configure script tries to catch) > is or is not critical to the Mpich building process. > > Gus Correa > > On 07/20/2018 06:11 PM, Reuti wrote: >> Hi, >>> Am 20.07.2018 um 23:50 schrieb Gus Correa <gus(a)ldeo.columbia.edu>: >>> >>> A long while ago, adding the -noswitcherror switch to pgcc >>> was a quick and dirty workaround to the PGI constant change of >>> the switches' names, and missing switches. >>> Why don't they use --version as gcc? >> I get this output: >> $ pgf77 --version >> pgf77 18.4-0 64-bit target on x86-64 Linux -tp nehalem >> PGI Compilers and Tools >> Copyright (c) 2018, NVIDIA CORPORATION. All rights reserved. >> So the switch seems to be available. With -q… I think more about the Intel compilers. >> -- Reuti >>> E.g.: ./configure CC='pgcc -noswitcherror' --prefix=/bla/bla >>> >>> But here, since capturing the actual compiler >>> version may be critical for the Mpich building process, >>> that may not help. >>> >>> My two cents, >>> Gus Correa >>> >>> >>> On 07/20/2018 05:14 PM, Jeff Hammond wrote: >>>> The problem exists in PGI 18 but not PGI 17. This seems like a PGI bug rather than an MPICH one. >>>> Jeff >>>> On Fri, Jul 20, 2018 at 8:24 AM, Jeff Layton <laytonjb(a)att.net <mailto:[email protected]>> wrote: >>>> I fixed this problem and I get the exact same error. Again, I >>>> grepped config.log and found the following. >>>> $ grep -i error config.log >>>> pgcc-Error-Unknown switch: -qversion >>>> PGC/x86-64 Linux 18.4-0: compilation completed with severe errors >>>> PGC-S-0035-Syntax error: Recovery attempted by replacing identifier >>>> error by ';' (conftest.c: 14) >>>> PGC/x86-64 Linux 18.4-0: compilation completed with severe errors >>>> | Syntax error >>>> PGC-S-0035-Syntax error: Recovery attempted by replacing identifier >>>> error by ';' (conftest.c: 14) >>>> PGC/x86-64 Linux 18.4-0: compilation completed with severe errors >>>> | Syntax error >>>> configure:5951: error: in `/home/laytonjb/src/mpich-3.2.1': >>>> configure:5953: error: C preprocessor >>>> "/opt/pgi/linux86-64/18.4/bin/pgcc" fails sanity check >>>> HAVE_ERROR_CHECKING='' >>>> MPI_MAX_ERROR_STRING='' >>>> I'm not an expert but it looks like configure sends an unknown >>>> option to pgcc (-qversion). Then there appear to be some problems in >>>> mpich when built with pgcc. >>>> Any comments or thoughts? >>>> Thanks! >>>> Jeff >>>>> Dooh. Thanks - I'll try this and see what happens. >>>>> >>>>> Thanks! >>>>> >>>>> Jeff >>>>> >>>>>>> Am 19.07.2018 um 01:19 schrieb Jeff Layton <laytonjb(a)att.net> >>>>>>> <mailto:[email protected]>: >>>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> I'm trying to build mpich-3.2.1 with the PGI 18.4 Community >>>>>>> Edition compilers. However, I get an error when running >>>>>>> configure. The configure line is, >>>>>>> >>>>>>> ./configure --prefix=/home/laytonjb/bin/pgi-18.4-mpich-3.2.1 >>>>>>> >>>>>>> The error I get is, >>>>>>> >>>>>>> [laytonjb@laytonjb-Lenovo-G50-45 mpich-3.2.1]$ ./conf.jeff >>>>>>> Configuring MPICH version 3.2.1 with >>>>>>> '--prefix=/home/laytonjb/bin/pgi-18.4-mpich-3.2.1' >>>>>>> 'CC=/opt/pgi/linux86-64/18.4/bin/pgcc' >>>>>>> 'CPP=/opt/pgi/linux86-64/18.4/bin/pgcc' >>>>>>> 'CXX=/opt/pgi/linux86-64/18.4/bin/pgg++' >>>>>>> 'FC=/opt/pgi/linux86-64/18.4/bin/pgfortran' >>>>>> pgg++ seems to be typo, duno whether this is related. >>>>>> >>>>>> -- Reuti >>>>>> >>>>>> >>>>>>> 'F77=/opt/pgi/linux86-64/18.4/bin/pgf77' >>>>>>> Running on system: Linux laytonjb-Lenovo-G50-45 >>>>>>> 3.10.0-693.17.1.el7.x86_64 #1 SMP Thu Jan 25 20:13:58 UTC 2018 >>>>>>> x86_64 x86_64 x86_64 GNU/Linux >>>>>>> checking whether the C compiler works... yes >>>>>>> checking for C compiler default output file name... a.out >>>>>>> checking for suffix of executables... >>>>>>> checking whether we are cross compiling... no >>>>>>> checking for suffix of object files... o >>>>>>> checking whether we are using the GNU C compiler... no >>>>>>> checking whether /opt/pgi/linux86-64/18.4/bin/pgcc accepts -g... >>>>>>> yes >>>>>>> checking for /opt/pgi/linux86-64/18.4/bin/pgcc option to accept >>>>>>> ISO C89... none needed >>>>>>> checking whether /opt/pgi/linux86-64/18.4/bin/pgcc understands >>>>>>> -c and -o together... yes >>>>>>> checking how to run the C preprocessor... >>>>>>> /opt/pgi/linux86-64/18.4/bin/pgcc >>>>>>> configure: error: in `/home/laytonjb/src/mpich-3.2.1': >>>>>>> configure: error: C preprocessor >>>>>>> "/opt/pgi/linux86-64/18.4/bin/pgcc" fails sanity check >>>>>>> See `config.log' for more details >>>>>>> >>>>>>> I've briefly looked through the config.log and this is all that >>>>>>> stands out: >>>>>>> >>>>>>> >>>>>>> $ grep -i error config.log >>>>>>> pgcc-Error-Unknown switch: -qversion >>>>>>> PGC/x86-64 Linux 18.4-0: compilation completed with severe errors >>>>>>> PGC-S-0035-Syntax error: Recovery attempted by replacing >>>>>>> identifier error by ';' (conftest.c: 14) >>>>>>> PGC/x86-64 Linux 18.4-0: compilation completed with severe errors >>>>>>> | Syntax error >>>>>>> PGC-S-0035-Syntax error: Recovery attempted by replacing >>>>>>> identifier error by ';' (conftest.c: 14) >>>>>>> PGC/x86-64 Linux 18.4-0: compilation completed with severe errors >>>>>>> | Syntax error >>>>>>> configure:5951: error: in `/home/laytonjb/src/mpich-3.2.1': >>>>>>> configure:5953: error: C preprocessor >>>>>>> "/opt/pgi/linux86-64/18.4/bin/pgcc" fails sanity check >>>>>>> HAVE_ERROR_CHECKING='' >>>>>>> MPI_MAX_ERROR_STRING='' >>>>>>> >>>>>>> I'm not sure how to fix this error. I've attached the config.log >>>>>>> file in case this helps. >>>>>>> >>>>>>> Thanks for any and all help. >>>>>>> >>>>>>> Jeff >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> <config.log>_______________________________________________ >>>>>>> discuss mailing list discuss(a)mpich.org <mailto:[email protected]> >>>>>>> To manage subscription options or unsubscribe: >>>>>>> https://lists.mpich.org/mailman/listinfo/discuss >>>>>>> <https://lists.mpich.org/mailman/listinfo/discuss> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> discuss mailing list discuss(a)mpich.org <mailto:[email protected]> >>>>> To manage subscription options or unsubscribe: >>>>> https://lists.mpich.org/mailman/listinfo/discuss >>>>> <https://lists.mpich.org/mailman/listinfo/discuss> >>>>> >>>> _______________________________________________ >>>> discuss mailing list discuss(a)mpich.org <mailto:[email protected]> >>>> To manage subscription options or unsubscribe: >>>> https://lists.mpich.org/mailman/listinfo/discuss >>>> <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 >>>> 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 > _______________________________________________ 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 building mpich-3.2.1 with PGI 18.4 Community Edition
by Gus Correa 20 Jul '18

20 Jul '18

Hi Reuti I haven't used PGI in a long while, never PGI 18, so forgive my wild guess. Older versions didn't have the --version flag, it was -V. The -noswitcherror was a blanket to avoid errors with any unknown switch, which were simply ignored. A dirty trick, but sometimes it worked. I don't even know if it still exists in PGI 18, does it? Whether using it is a wise choice in this case, I really don't know, it depends on whether the compiler version (that the Intel-ish '-qversion' in the configure script tries to catch) is or is not critical to the Mpich building process. Gus Correa On 07/20/2018 06:11 PM, Reuti wrote: > Hi, > >> Am 20.07.2018 um 23:50 schrieb Gus Correa <gus(a)ldeo.columbia.edu>: >> >> A long while ago, adding the -noswitcherror switch to pgcc >> was a quick and dirty workaround to the PGI constant change of >> the switches' names, and missing switches. >> Why don't they use --version as gcc? > > I get this output: > > $ pgf77 --version > > pgf77 18.4-0 64-bit target on x86-64 Linux -tp nehalem > PGI Compilers and Tools > Copyright (c) 2018, NVIDIA CORPORATION. All rights reserved. > > So the switch seems to be available. With -q… I think more about the Intel compilers. > > -- Reuti > > >> E.g.: ./configure CC='pgcc -noswitcherror' --prefix=/bla/bla >> >> But here, since capturing the actual compiler >> version may be critical for the Mpich building process, >> that may not help. >> >> My two cents, >> Gus Correa >> >> >> On 07/20/2018 05:14 PM, Jeff Hammond wrote: >>> The problem exists in PGI 18 but not PGI 17. This seems like a PGI bug rather than an MPICH one. >>> Jeff >>> On Fri, Jul 20, 2018 at 8:24 AM, Jeff Layton <laytonjb(a)att.net <mailto:[email protected]>> wrote: >>> I fixed this problem and I get the exact same error. Again, I >>> grepped config.log and found the following. >>> $ grep -i error config.log >>> pgcc-Error-Unknown switch: -qversion >>> PGC/x86-64 Linux 18.4-0: compilation completed with severe errors >>> PGC-S-0035-Syntax error: Recovery attempted by replacing identifier >>> error by ';' (conftest.c: 14) >>> PGC/x86-64 Linux 18.4-0: compilation completed with severe errors >>> | Syntax error >>> PGC-S-0035-Syntax error: Recovery attempted by replacing identifier >>> error by ';' (conftest.c: 14) >>> PGC/x86-64 Linux 18.4-0: compilation completed with severe errors >>> | Syntax error >>> configure:5951: error: in `/home/laytonjb/src/mpich-3.2.1': >>> configure:5953: error: C preprocessor >>> "/opt/pgi/linux86-64/18.4/bin/pgcc" fails sanity check >>> HAVE_ERROR_CHECKING='' >>> MPI_MAX_ERROR_STRING='' >>> I'm not an expert but it looks like configure sends an unknown >>> option to pgcc (-qversion). Then there appear to be some problems in >>> mpich when built with pgcc. >>> Any comments or thoughts? >>> Thanks! >>> Jeff >>>> Dooh. Thanks - I'll try this and see what happens. >>>> >>>> Thanks! >>>> >>>> Jeff >>>> >>>>>> Am 19.07.2018 um 01:19 schrieb Jeff Layton <laytonjb(a)att.net> >>>>>> <mailto:[email protected]>: >>>>>> >>>>>> Hello, >>>>>> >>>>>> I'm trying to build mpich-3.2.1 with the PGI 18.4 Community >>>>>> Edition compilers. However, I get an error when running >>>>>> configure. The configure line is, >>>>>> >>>>>> ./configure --prefix=/home/laytonjb/bin/pgi-18.4-mpich-3.2.1 >>>>>> >>>>>> The error I get is, >>>>>> >>>>>> [laytonjb@laytonjb-Lenovo-G50-45 mpich-3.2.1]$ ./conf.jeff >>>>>> Configuring MPICH version 3.2.1 with >>>>>> '--prefix=/home/laytonjb/bin/pgi-18.4-mpich-3.2.1' >>>>>> 'CC=/opt/pgi/linux86-64/18.4/bin/pgcc' >>>>>> 'CPP=/opt/pgi/linux86-64/18.4/bin/pgcc' >>>>>> 'CXX=/opt/pgi/linux86-64/18.4/bin/pgg++' >>>>>> 'FC=/opt/pgi/linux86-64/18.4/bin/pgfortran' >>>>> pgg++ seems to be typo, duno whether this is related. >>>>> >>>>> -- Reuti >>>>> >>>>> >>>>>> 'F77=/opt/pgi/linux86-64/18.4/bin/pgf77' >>>>>> Running on system: Linux laytonjb-Lenovo-G50-45 >>>>>> 3.10.0-693.17.1.el7.x86_64 #1 SMP Thu Jan 25 20:13:58 UTC 2018 >>>>>> x86_64 x86_64 x86_64 GNU/Linux >>>>>> checking whether the C compiler works... yes >>>>>> checking for C compiler default output file name... a.out >>>>>> checking for suffix of executables... >>>>>> checking whether we are cross compiling... no >>>>>> checking for suffix of object files... o >>>>>> checking whether we are using the GNU C compiler... no >>>>>> checking whether /opt/pgi/linux86-64/18.4/bin/pgcc accepts -g... >>>>>> yes >>>>>> checking for /opt/pgi/linux86-64/18.4/bin/pgcc option to accept >>>>>> ISO C89... none needed >>>>>> checking whether /opt/pgi/linux86-64/18.4/bin/pgcc understands >>>>>> -c and -o together... yes >>>>>> checking how to run the C preprocessor... >>>>>> /opt/pgi/linux86-64/18.4/bin/pgcc >>>>>> configure: error: in `/home/laytonjb/src/mpich-3.2.1': >>>>>> configure: error: C preprocessor >>>>>> "/opt/pgi/linux86-64/18.4/bin/pgcc" fails sanity check >>>>>> See `config.log' for more details >>>>>> >>>>>> I've briefly looked through the config.log and this is all that >>>>>> stands out: >>>>>> >>>>>> >>>>>> $ grep -i error config.log >>>>>> pgcc-Error-Unknown switch: -qversion >>>>>> PGC/x86-64 Linux 18.4-0: compilation completed with severe errors >>>>>> PGC-S-0035-Syntax error: Recovery attempted by replacing >>>>>> identifier error by ';' (conftest.c: 14) >>>>>> PGC/x86-64 Linux 18.4-0: compilation completed with severe errors >>>>>> | Syntax error >>>>>> PGC-S-0035-Syntax error: Recovery attempted by replacing >>>>>> identifier error by ';' (conftest.c: 14) >>>>>> PGC/x86-64 Linux 18.4-0: compilation completed with severe errors >>>>>> | Syntax error >>>>>> configure:5951: error: in `/home/laytonjb/src/mpich-3.2.1': >>>>>> configure:5953: error: C preprocessor >>>>>> "/opt/pgi/linux86-64/18.4/bin/pgcc" fails sanity check >>>>>> HAVE_ERROR_CHECKING='' >>>>>> MPI_MAX_ERROR_STRING='' >>>>>> >>>>>> I'm not sure how to fix this error. I've attached the config.log >>>>>> file in case this helps. >>>>>> >>>>>> Thanks for any and all help. >>>>>> >>>>>> Jeff >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> <config.log>_______________________________________________ >>>>>> discuss mailing list discuss(a)mpich.org <mailto:[email protected]> >>>>>> To manage subscription options or unsubscribe: >>>>>> https://lists.mpich.org/mailman/listinfo/discuss >>>>>> <https://lists.mpich.org/mailman/listinfo/discuss> >>>>> >>>> >>>> _______________________________________________ >>>> discuss mailing list discuss(a)mpich.org <mailto:[email protected]> >>>> To manage subscription options or unsubscribe: >>>> https://lists.mpich.org/mailman/listinfo/discuss >>>> <https://lists.mpich.org/mailman/listinfo/discuss> >>>> >>> _______________________________________________ >>> discuss mailing list discuss(a)mpich.org <mailto:[email protected]> >>> To manage subscription options or unsubscribe: >>> https://lists.mpich.org/mailman/listinfo/discuss >>> <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 >>> 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] Problems building mpich-3.2.1 with PGI 18.4 Community Edition
by Reuti 20 Jul '18

20 Jul '18

Hi, > Am 20.07.2018 um 23:50 schrieb Gus Correa <gus(a)ldeo.columbia.edu>: > > A long while ago, adding the -noswitcherror switch to pgcc > was a quick and dirty workaround to the PGI constant change of > the switches' names, and missing switches. > Why don't they use --version as gcc? I get this output: $ pgf77 --version pgf77 18.4-0 64-bit target on x86-64 Linux -tp nehalem PGI Compilers and Tools Copyright (c) 2018, NVIDIA CORPORATION. All rights reserved. So the switch seems to be available. With -q… I think more about the Intel compilers. -- Reuti > E.g.: ./configure CC='pgcc -noswitcherror' --prefix=/bla/bla > > But here, since capturing the actual compiler > version may be critical for the Mpich building process, > that may not help. > > My two cents, > Gus Correa > > > On 07/20/2018 05:14 PM, Jeff Hammond wrote: >> The problem exists in PGI 18 but not PGI 17. This seems like a PGI bug rather than an MPICH one. >> Jeff >> On Fri, Jul 20, 2018 at 8:24 AM, Jeff Layton <laytonjb(a)att.net <mailto:[email protected]>> wrote: >> I fixed this problem and I get the exact same error. Again, I >> grepped config.log and found the following. >> $ grep -i error config.log >> pgcc-Error-Unknown switch: -qversion >> PGC/x86-64 Linux 18.4-0: compilation completed with severe errors >> PGC-S-0035-Syntax error: Recovery attempted by replacing identifier >> error by ';' (conftest.c: 14) >> PGC/x86-64 Linux 18.4-0: compilation completed with severe errors >> | Syntax error >> PGC-S-0035-Syntax error: Recovery attempted by replacing identifier >> error by ';' (conftest.c: 14) >> PGC/x86-64 Linux 18.4-0: compilation completed with severe errors >> | Syntax error >> configure:5951: error: in `/home/laytonjb/src/mpich-3.2.1': >> configure:5953: error: C preprocessor >> "/opt/pgi/linux86-64/18.4/bin/pgcc" fails sanity check >> HAVE_ERROR_CHECKING='' >> MPI_MAX_ERROR_STRING='' >> I'm not an expert but it looks like configure sends an unknown >> option to pgcc (-qversion). Then there appear to be some problems in >> mpich when built with pgcc. >> Any comments or thoughts? >> Thanks! >> Jeff >>> Dooh. Thanks - I'll try this and see what happens. >>> >>> Thanks! >>> >>> Jeff >>> >>>>> Am 19.07.2018 um 01:19 schrieb Jeff Layton <laytonjb(a)att.net> >>>>> <mailto:[email protected]>: >>>>> >>>>> Hello, >>>>> >>>>> I'm trying to build mpich-3.2.1 with the PGI 18.4 Community >>>>> Edition compilers. However, I get an error when running >>>>> configure. The configure line is, >>>>> >>>>> ./configure --prefix=/home/laytonjb/bin/pgi-18.4-mpich-3.2.1 >>>>> >>>>> The error I get is, >>>>> >>>>> [laytonjb@laytonjb-Lenovo-G50-45 mpich-3.2.1]$ ./conf.jeff >>>>> Configuring MPICH version 3.2.1 with >>>>> '--prefix=/home/laytonjb/bin/pgi-18.4-mpich-3.2.1' >>>>> 'CC=/opt/pgi/linux86-64/18.4/bin/pgcc' >>>>> 'CPP=/opt/pgi/linux86-64/18.4/bin/pgcc' >>>>> 'CXX=/opt/pgi/linux86-64/18.4/bin/pgg++' >>>>> 'FC=/opt/pgi/linux86-64/18.4/bin/pgfortran' >>>> pgg++ seems to be typo, duno whether this is related. >>>> >>>> -- Reuti >>>> >>>> >>>>> 'F77=/opt/pgi/linux86-64/18.4/bin/pgf77' >>>>> Running on system: Linux laytonjb-Lenovo-G50-45 >>>>> 3.10.0-693.17.1.el7.x86_64 #1 SMP Thu Jan 25 20:13:58 UTC 2018 >>>>> x86_64 x86_64 x86_64 GNU/Linux >>>>> checking whether the C compiler works... yes >>>>> checking for C compiler default output file name... a.out >>>>> checking for suffix of executables... >>>>> checking whether we are cross compiling... no >>>>> checking for suffix of object files... o >>>>> checking whether we are using the GNU C compiler... no >>>>> checking whether /opt/pgi/linux86-64/18.4/bin/pgcc accepts -g... >>>>> yes >>>>> checking for /opt/pgi/linux86-64/18.4/bin/pgcc option to accept >>>>> ISO C89... none needed >>>>> checking whether /opt/pgi/linux86-64/18.4/bin/pgcc understands >>>>> -c and -o together... yes >>>>> checking how to run the C preprocessor... >>>>> /opt/pgi/linux86-64/18.4/bin/pgcc >>>>> configure: error: in `/home/laytonjb/src/mpich-3.2.1': >>>>> configure: error: C preprocessor >>>>> "/opt/pgi/linux86-64/18.4/bin/pgcc" fails sanity check >>>>> See `config.log' for more details >>>>> >>>>> I've briefly looked through the config.log and this is all that >>>>> stands out: >>>>> >>>>> >>>>> $ grep -i error config.log >>>>> pgcc-Error-Unknown switch: -qversion >>>>> PGC/x86-64 Linux 18.4-0: compilation completed with severe errors >>>>> PGC-S-0035-Syntax error: Recovery attempted by replacing >>>>> identifier error by ';' (conftest.c: 14) >>>>> PGC/x86-64 Linux 18.4-0: compilation completed with severe errors >>>>> | Syntax error >>>>> PGC-S-0035-Syntax error: Recovery attempted by replacing >>>>> identifier error by ';' (conftest.c: 14) >>>>> PGC/x86-64 Linux 18.4-0: compilation completed with severe errors >>>>> | Syntax error >>>>> configure:5951: error: in `/home/laytonjb/src/mpich-3.2.1': >>>>> configure:5953: error: C preprocessor >>>>> "/opt/pgi/linux86-64/18.4/bin/pgcc" fails sanity check >>>>> HAVE_ERROR_CHECKING='' >>>>> MPI_MAX_ERROR_STRING='' >>>>> >>>>> I'm not sure how to fix this error. I've attached the config.log >>>>> file in case this helps. >>>>> >>>>> Thanks for any and all help. >>>>> >>>>> Jeff >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> <config.log>_______________________________________________ >>>>> discuss mailing list discuss(a)mpich.org <mailto:[email protected]> >>>>> To manage subscription options or unsubscribe: >>>>> https://lists.mpich.org/mailman/listinfo/discuss >>>>> <https://lists.mpich.org/mailman/listinfo/discuss> >>>> >>> >>> _______________________________________________ >>> discuss mailing list discuss(a)mpich.org <mailto:[email protected]> >>> To manage subscription options or unsubscribe: >>> https://lists.mpich.org/mailman/listinfo/discuss >>> <https://lists.mpich.org/mailman/listinfo/discuss> >>> >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org <mailto:[email protected]> >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss >> <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 >> 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 building mpich-3.2.1 with PGI 18.4 Community Edition
by Reuti 20 Jul '18

20 Jul '18

In the configure statement you posted in your original post you set CPP (see below in this post) which results in exactly this error when set to the plain C compiler. Please double check that it’s no longer there. >> error: C preprocessor "/opt/pgi/linux86-64/18.4/bin/pgcc" fails sanity check -- Reuti > Am 20.07.2018 um 23:14 schrieb Jeff Hammond <jeff.science(a)gmail.com>: > > The problem exists in PGI 18 but not PGI 17. This seems like a PGI bug rather than an MPICH one. > > Jeff > >> On Fri, Jul 20, 2018 at 8:24 AM, Jeff Layton <laytonjb(a)att.net> wrote: >> I fixed this problem and I get the exact same error. Again, I grepped config.log and found the following. >> >> >> $ grep -i error config.log >> pgcc-Error-Unknown switch: -qversion >> PGC/x86-64 Linux 18.4-0: compilation completed with severe errors >> PGC-S-0035-Syntax error: Recovery attempted by replacing identifier error by ';' (conftest.c: 14) >> PGC/x86-64 Linux 18.4-0: compilation completed with severe errors >> | Syntax error >> PGC-S-0035-Syntax error: Recovery attempted by replacing identifier error by ';' (conftest.c: 14) >> PGC/x86-64 Linux 18.4-0: compilation completed with severe errors >> | Syntax error >> configure:5951: error: in `/home/laytonjb/src/mpich-3.2.1': >> configure:5953: error: C preprocessor "/opt/pgi/linux86-64/18.4/bin/pgcc" fails sanity check >> HAVE_ERROR_CHECKING='' >> MPI_MAX_ERROR_STRING='' >> >> >> >> I'm not an expert but it looks like configure sends an unknown option to pgcc (-qversion). Then there appear to be some problems in mpich when built with pgcc. >> >> Any comments or thoughts? >> >> Thanks! >> >> Jeff >> >> >>> Dooh. Thanks - I'll try this and see what happens. >>> >>> Thanks! >>> >>> Jeff >>> >>>>> Am 19.07.2018 um 01:19 schrieb Jeff Layton <laytonjb(a)att.net>: >>>>> >>>>> Hello, >>>>> >>>>> I'm trying to build mpich-3.2.1 with the PGI 18.4 Community Edition compilers. However, I get an error when running configure. The configure line is, >>>>> >>>>> ./configure --prefix=/home/laytonjb/bin/pgi-18.4-mpich-3.2.1 >>>>> >>>>> The error I get is, >>>>> >>>>> [laytonjb@laytonjb-Lenovo-G50-45 mpich-3.2.1]$ ./conf.jeff >>>>> Configuring MPICH version 3.2.1 with '--prefix=/home/laytonjb/bin/pgi-18.4-mpich-3.2.1' 'CC=/opt/pgi/linux86-64/18.4/bin/pgcc' 'CPP=/opt/pgi/linux86-64/18.4/bin/pgcc' 'CXX=/opt/pgi/linux86-64/18.4/bin/pgg++' 'FC=/opt/pgi/linux86-64/18.4/bin/pgfortran' >>>> pgg++ seems to be typo, duno whether this is related. >>>> >>>> -- Reuti >>>> >>>> >>>>> 'F77=/opt/pgi/linux86-64/18.4/bin/pgf77' >>>>> Running on system: Linux laytonjb-Lenovo-G50-45 3.10.0-693.17.1.el7.x86_64 #1 SMP Thu Jan 25 20:13:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux >>>>> checking whether the C compiler works... yes >>>>> checking for C compiler default output file name... a.out >>>>> checking for suffix of executables... >>>>> checking whether we are cross compiling... no >>>>> checking for suffix of object files... o >>>>> checking whether we are using the GNU C compiler... no >>>>> checking whether /opt/pgi/linux86-64/18.4/bin/pgcc accepts -g... yes >>>>> checking for /opt/pgi/linux86-64/18.4/bin/pgcc option to accept ISO C89... none needed >>>>> checking whether /opt/pgi/linux86-64/18.4/bin/pgcc understands -c and -o together... yes >>>>> checking how to run the C preprocessor... /opt/pgi/linux86-64/18.4/bin/pgcc >>>>> configure: error: in `/home/laytonjb/src/mpich-3.2.1': >>>>> configure: error: C preprocessor "/opt/pgi/linux86-64/18.4/bin/pgcc" fails sanity check >>>>> See `config.log' for more details >>>>> >>>>> I've briefly looked through the config.log and this is all that stands out: >>>>> >>>>> >>>>> $ grep -i error config.log >>>>> pgcc-Error-Unknown switch: -qversion >>>>> PGC/x86-64 Linux 18.4-0: compilation completed with severe errors >>>>> PGC-S-0035-Syntax error: Recovery attempted by replacing identifier error by ';' (conftest.c: 14) >>>>> PGC/x86-64 Linux 18.4-0: compilation completed with severe errors >>>>> | Syntax error >>>>> PGC-S-0035-Syntax error: Recovery attempted by replacing identifier error by ';' (conftest.c: 14) >>>>> PGC/x86-64 Linux 18.4-0: compilation completed with severe errors >>>>> | Syntax error >>>>> configure:5951: error: in `/home/laytonjb/src/mpich-3.2.1': >>>>> configure:5953: error: C preprocessor "/opt/pgi/linux86-64/18.4/bin/pgcc" fails sanity check >>>>> HAVE_ERROR_CHECKING='' >>>>> MPI_MAX_ERROR_STRING='' >>>>> >>>>> I'm not sure how to fix this error. I've attached the config.log file in case this helps. >>>>> >>>>> Thanks for any and all help. >>>>> >>>>> Jeff >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> <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 >>> >> >> >> _______________________________________________ >> 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] Problems building mpich-3.2.1 with PGI 18.4 Community Edition
by Gus Correa 20 Jul '18

20 Jul '18

A long while ago, adding the -noswitcherror switch to pgcc was a quick and dirty workaround to the PGI constant change of the switches' names, and missing switches. Why don't they use --version as gcc? E.g.: ./configure CC='pgcc -noswitcherror' --prefix=/bla/bla But here, since capturing the actual compiler version may be critical for the Mpich building process, that may not help. My two cents, Gus Correa On 07/20/2018 05:14 PM, Jeff Hammond wrote: > The problem exists in PGI 18 but not PGI 17. This seems like a PGI bug > rather than an MPICH one. > > Jeff > > On Fri, Jul 20, 2018 at 8:24 AM, Jeff Layton <laytonjb(a)att.net > <mailto:[email protected]>> wrote: > > I fixed this problem and I get the exact same error. Again, I > grepped config.log and found the following. > > > $ grep -i error config.log > pgcc-Error-Unknown switch: -qversion > PGC/x86-64 Linux 18.4-0: compilation completed with severe errors > PGC-S-0035-Syntax error: Recovery attempted by replacing identifier > error by ';' (conftest.c: 14) > PGC/x86-64 Linux 18.4-0: compilation completed with severe errors > | Syntax error > PGC-S-0035-Syntax error: Recovery attempted by replacing identifier > error by ';' (conftest.c: 14) > PGC/x86-64 Linux 18.4-0: compilation completed with severe errors > | Syntax error > configure:5951: error: in `/home/laytonjb/src/mpich-3.2.1': > configure:5953: error: C preprocessor > "/opt/pgi/linux86-64/18.4/bin/pgcc" fails sanity check > HAVE_ERROR_CHECKING='' > MPI_MAX_ERROR_STRING='' > > > > I'm not an expert but it looks like configure sends an unknown > option to pgcc (-qversion). Then there appear to be some problems in > mpich when built with pgcc. > > Any comments or thoughts? > > Thanks! > > Jeff > > >> Dooh. Thanks - I'll try this and see what happens. >> >> Thanks! >> >> Jeff >> >>>> Am 19.07.2018 um 01:19 schrieb Jeff Layton <laytonjb(a)att.net> >>>> <mailto:[email protected]>: >>>> >>>> Hello, >>>> >>>> I'm trying to build mpich-3.2.1 with the PGI 18.4 Community >>>> Edition compilers. However, I get an error when running >>>> configure. The configure line is, >>>> >>>> ./configure --prefix=/home/laytonjb/bin/pgi-18.4-mpich-3.2.1 >>>> >>>> The error I get is, >>>> >>>> [laytonjb@laytonjb-Lenovo-G50-45 mpich-3.2.1]$ ./conf.jeff >>>> Configuring MPICH version 3.2.1 with >>>> '--prefix=/home/laytonjb/bin/pgi-18.4-mpich-3.2.1' >>>> 'CC=/opt/pgi/linux86-64/18.4/bin/pgcc' >>>> 'CPP=/opt/pgi/linux86-64/18.4/bin/pgcc' >>>> 'CXX=/opt/pgi/linux86-64/18.4/bin/pgg++' >>>> 'FC=/opt/pgi/linux86-64/18.4/bin/pgfortran' >>> pgg++ seems to be typo, duno whether this is related. >>> >>> -- Reuti >>> >>> >>>> 'F77=/opt/pgi/linux86-64/18.4/bin/pgf77' >>>> Running on system: Linux laytonjb-Lenovo-G50-45 >>>> 3.10.0-693.17.1.el7.x86_64 #1 SMP Thu Jan 25 20:13:58 UTC 2018 >>>> x86_64 x86_64 x86_64 GNU/Linux >>>> checking whether the C compiler works... yes >>>> checking for C compiler default output file name... a.out >>>> checking for suffix of executables... >>>> checking whether we are cross compiling... no >>>> checking for suffix of object files... o >>>> checking whether we are using the GNU C compiler... no >>>> checking whether /opt/pgi/linux86-64/18.4/bin/pgcc accepts -g... >>>> yes >>>> checking for /opt/pgi/linux86-64/18.4/bin/pgcc option to accept >>>> ISO C89... none needed >>>> checking whether /opt/pgi/linux86-64/18.4/bin/pgcc understands >>>> -c and -o together... yes >>>> checking how to run the C preprocessor... >>>> /opt/pgi/linux86-64/18.4/bin/pgcc >>>> configure: error: in `/home/laytonjb/src/mpich-3.2.1': >>>> configure: error: C preprocessor >>>> "/opt/pgi/linux86-64/18.4/bin/pgcc" fails sanity check >>>> See `config.log' for more details >>>> >>>> I've briefly looked through the config.log and this is all that >>>> stands out: >>>> >>>> >>>> $ grep -i error config.log >>>> pgcc-Error-Unknown switch: -qversion >>>> PGC/x86-64 Linux 18.4-0: compilation completed with severe errors >>>> PGC-S-0035-Syntax error: Recovery attempted by replacing >>>> identifier error by ';' (conftest.c: 14) >>>> PGC/x86-64 Linux 18.4-0: compilation completed with severe errors >>>> | Syntax error >>>> PGC-S-0035-Syntax error: Recovery attempted by replacing >>>> identifier error by ';' (conftest.c: 14) >>>> PGC/x86-64 Linux 18.4-0: compilation completed with severe errors >>>> | Syntax error >>>> configure:5951: error: in `/home/laytonjb/src/mpich-3.2.1': >>>> configure:5953: error: C preprocessor >>>> "/opt/pgi/linux86-64/18.4/bin/pgcc" fails sanity check >>>> HAVE_ERROR_CHECKING='' >>>> MPI_MAX_ERROR_STRING='' >>>> >>>> I'm not sure how to fix this error. I've attached the config.log >>>> file in case this helps. >>>> >>>> Thanks for any and all help. >>>> >>>> Jeff >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> <config.log>_______________________________________________ >>>> discuss mailing list discuss(a)mpich.org <mailto:[email protected]> >>>> To manage subscription options or unsubscribe: >>>> https://lists.mpich.org/mailman/listinfo/discuss >>>> <https://lists.mpich.org/mailman/listinfo/discuss> >>> >> >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org <mailto:[email protected]> >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss >> <https://lists.mpich.org/mailman/listinfo/discuss> >> > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org <mailto:[email protected]> > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > <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 > 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