Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: Re: [OMPI users] Compiling OpenMPI with PGI pgc++
From: Reuti (reuti_at_[hidden])
Date: 2014-01-29 12:35:01


Am 29.01.2014 um 18:24 schrieb Jeff Squyres (jsquyres):

> Oh, I'm sorry -- I mis-read your initial mail (I thought when you did use all the PGI compilers, it worked).
>
> I don't know the difference between pgc++ and pgcpp, unfortunately.

It's a matter of the ABI:

http://www.pgroup.com/lit/articles/insider/v4n1a2.htm

pgc++ uses the new ABI.

-- Reuti

> Do you have the latest version of your PGI compiler suite in that series?
>
>
> On Jan 29, 2014, at 12:10 PM, Jiri Kraus <jkraus_at_[hidden]> wrote:
>
>> Hi Jeff,
>>
>> thanks for taking a look. I don't want to mix compiler tool chains. I have just double checked my configure line and I am passing
>>
>> CXX=pgc++ CC=pgcc FC=pgfortran F77=pgfortran ...
>>
>> so there are only PGI compilers used.
>>
>> Thanks
>>
>> Jiri
>>
>>> Date: Wed, 29 Jan 2014 16:24:08 +0000
>>> From: "Jeff Squyres (jsquyres)" <jsquyres_at_[hidden]>
>>> To: Open MPI Users <users_at_[hidden]>
>>> Subject: Re: [OMPI users] Compiling OpenMPI with PGI pgc++
>>> Message-ID: <C7F17676-833E-4A51-AD9E-DE988C5D2E0F_at_[hidden]>
>>> Content-Type: text/plain; charset="us-ascii"
>>>
>>> That sounds about right.
>>>
>>> What's happening is that OMPI has learned a bunch about the C compiler
>>> before it does this C++ link test. In your first case (which is assumedly with
>>> gcc), it determines that it needs _GNU_SOURCE set -- or some other test has
>>> caused that to be set. Then it uses that with pgc++ and runs into the error you
>>> show below.
>>>
>>> Is there a reason you want to mix gcc and pgc++? It's usually simpler/better to
>>> use a single compiler suite for the whole thing.
>>>
>>>
>>> On Jan 29, 2014, at 10:54 AM, Jiri Kraus <jkraus_at_[hidden]> wrote:
>>>
>>>> Hi,
>>>>
>>>> I am trying to compile OpenMPI 1.7.3 with pgc++ (14.1) as C++ compiler.
>>> During configure it fails with
>>>>
>>>> checking if C and C++ are link compatible... no
>>>>
>>>> The error from config.log is:
>>>>
>>>> configure:18205: checking if C and C++ are link compatible
>>>> configure:18230: pgcc -c -DNDEBUG -fast conftest_c.c
>>>> configure:18237: $? = 0
>>>> configure:18268: pgc++ -o conftest -DNDEBUG -fast conftest.cpp
>>> conftest_c.o >&5
>>>> conftest.cpp:
>>>> "conftest.cpp", line 21: error: "_GNU_SOURCE" is predefined; attempted
>>>> redefinition ignored
>>>> #define _GNU_SOURCE 1
>>>> ^
>>>>
>>>> "conftest.cpp", line 86: error: "_GNU_SOURCE" is predefined; attempted
>>>> redefinition ignored
>>>> #define _GNU_SOURCE 1
>>>> ^
>>>>
>>>> "conftest.cpp", line 167: warning: statement is unreachable
>>>> return 0;
>>>> ^
>>>>
>>>> 2 errors detected in the compilation of "conftest.cpp".
>>>>
>>>> When I use pgcpp instead of pgc++ OpenMPI configures and builds.
>>>>
>>>> I am using
>>>>
>>>> CXX=pgcpp|pgc++ CC=pgcc FC=pgfortran F77=pgfortran CFLAGS=-fast
>>> FCFLAGS=-fast FFLAGS=-fast CXXFLAGS=-fast ./configure --with-
>>> hwloc=/shared/apps/rhel-6.2/tools/hwloc-1.7.1 --enable-hwloc-pci --with-cuda -
>>> -prefix=/home-2/jkraus/local/openmpi-1.7.3/pgi-14.1/cuda-5.5.22
>>>>
>>>> to configure OpenMPI. Any Idea what caused the errors with pgc++?
>>>>
>>>> Thanks
>>>>
>>>> Jiri
>>>>
>>>> -----------------------------------------------------------------------------------
>>>> Nvidia GmbH
>>>> W?rselen
>>>> Amtsgericht Aachen
>>>> HRB 8361
>>>> Managing Director: Karen Theresa Burns
>>>>
>>>> -----------------------------------------------------------------------------------
>>>> This email message is for the sole use of the intended recipient(s) and may
>>> contain
>>>> confidential information. Any unauthorized review, use, disclosure or
>>> distribution
>>>> is prohibited. If you are not the intended recipient, please contact the sender
>>> by
>>>> reply email and destroy all copies of the original message.
>>>> -----------------------------------------------------------------------------------
>>>>
>>>> _______________________________________________
>>>> users mailing list
>>>> users_at_[hidden]
>>>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>>>
>>>
>>> --
>>> Jeff Squyres
>>> jsquyres_at_[hidden]
>>> For corporate legal information go to:
>>> http://www.cisco.com/web/about/doing_business/legal/cri/
>>>
>>>
>>>
>>> ------------------------------
>>>
>>> Subject: Digest Footer
>>>
>>> _______________________________________________
>>> users mailing list
>>> users_at_[hidden]
>>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>>>
>>> ------------------------------
>>>
>>> End of users Digest, Vol 2796, Issue 1
>>> **************************************
>> _______________________________________________
>> users mailing list
>> users_at_[hidden]
>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>
>
> --
> Jeff Squyres
> jsquyres_at_[hidden]
> For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
>
> _______________________________________________
> users mailing list
> users_at_[hidden]
> http://www.open-mpi.org/mailman/listinfo.cgi/users