[mpich-discuss] Problems building mpich-3.2.1 with PGI 18.4 Community Edition
Gus Correa
gus at ldeo.columbia.edu
Fri Jul 20 17:25:48 CDT 2018
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 at 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 at att.net <mailto:laytonjb at 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 at att.net>
>>>>>> <mailto:laytonjb at 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 at 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 at mpich.org <mailto:discuss at mpich.org>
>>>>>> To manage subscription options or unsubscribe:
>>>>>> https://lists.mpich.org/mailman/listinfo/discuss
>>>>>> <https://lists.mpich.org/mailman/listinfo/discuss>
>>>>>
>>>>
>>>> _______________________________________________
>>>> discuss mailing list discuss at mpich.org <mailto:discuss at mpich.org>
>>>> To manage subscription options or unsubscribe:
>>>> https://lists.mpich.org/mailman/listinfo/discuss
>>>> <https://lists.mpich.org/mailman/listinfo/discuss>
>>>>
>>> _______________________________________________
>>> discuss mailing list discuss at mpich.org <mailto:discuss at mpich.org>
>>> To manage subscription options or unsubscribe:
>>> https://lists.mpich.org/mailman/listinfo/discuss
>>> <https://lists.mpich.org/mailman/listinfo/discuss>
>>> --
>>> Jeff Hammond
>>> jeff.science at gmail.com <mailto:jeff.science at gmail.com>
>>> http://jeffhammond.github.io/
>>> _______________________________________________
>>> discuss mailing list discuss at mpich.org
>>> To manage subscription options or unsubscribe:
>>> https://lists.mpich.org/mailman/listinfo/discuss
>>
>> _______________________________________________
>> discuss mailing list discuss at mpich.org
>> To manage subscription options or unsubscribe:
>> https://lists.mpich.org/mailman/listinfo/discuss
>
> _______________________________________________
> discuss mailing list discuss at mpich.org
> To manage subscription options or unsubscribe:
> https://lists.mpich.org/mailman/listinfo/discuss
>
_______________________________________________
discuss mailing list discuss at mpich.org
To manage subscription options or unsubscribe:
https://lists.mpich.org/mailman/listinfo/discuss
More information about the discuss
mailing list