Charm++ parallel programming system

[Jozsef Bakosi <jbakosi AT lanl.gov>]

I have not even attempted using PGI with libc++. Historically, they only 
support
the GNU headers and even that only some specific versions of them (not the
latest and not even 4.9, which is the earliest I have on my box, shipped
modified + still including some from the system), plus the -stdlib=libc++
command line argument is only supported by g++, clang, and intel, AFAIK, and 
not
by pgc++.

Thanks though,
Jozsef

On 04.25.2017 13:23, Nils Deppe wrote:
>    Hi Jozsef,
>    I haven't tried this but it might be possible to use libc++ with PGI.
>    If you can use a package manager to install libc++ then charm can be
>    compiled with:
>    ./build charm++ multicore-linux64 -j8 -stdlib=libc++
>    or if you compiled it yourself you can use:
>    ./build charm++ multicore-linux64 -j8 -stdlib=libc++
>    -I/path/to/llvm/build/include/c++/v1 -L/path/to/llvm/build/lib
>    Best,
>    Nils
>    Nils Deppe
>    Ph.D. Candidate, Physics, Cornell University
>    Teukolsky Group and SXS Collaboration
>    Office: 619 Space Sciences Building,
>               122 Sciences Dr.,
>               Cornell University, Ithaca, NY
>    ./build charm++ multicore-linux64 clang -j8 -stdlib=libc++
>    On Tue, Apr 25, 2017 at 1:15 PM, Jozsef Bakosi 
> <[1]jbakosi AT lanl.gov>
>    wrote:
> 
>      Thanks, Phil,
>      That works. It continues and next I get stuck with:
>      "/usr/include/c++/4.9/cstdlib", line 118: error: the global scope
>      has no
>                "div_t"
>          using ::div_t;
>      which seems like a PGI / GNU standard C++ library problem, and is
>      most similar
>      to the issue at [2]https://devtalk.nvidia.com/
>      default/topic/977515/openacc-toolkit/-openacc-c-the-global-
>      scope-has-no-quot-acos-quot-using-acos/.
>      Now my build command is:
>      ./build charm++ mpi-linux-x86_64 pgcc --build-shared
>      -I/usr/include/c++/4.9 -I/opt/pgi/linux86-64/16.10/include-gcc49
>      Thanks for the help. I shelve this for now.
>      Thanks,
>      Jozsef
>      On 04.25.2017 11:38, Phil Miller wrote:
>      >    On Tue, Apr 25, 2017 at 11:32 AM, Jozsef Bakosi
>      
> <[1][3]jbakosi AT lanl.gov>
>      >    wrote:
>      >
>      >      Hi folks,
>      >      I'm trying to compile with the PGI compilers and I get:
>      >      Error checking is enabled
>      >      Statistics collection is enabled
>      >      Charm tracing is enabled
>      >      Charm tracing communication thread is disabled
>      >      CharmDebug is enabled
>      >      Charm record/replay is enabled
>      >      CCS is enabled
>      >      Charm control point is enabled
>      >      Charm LB user data is disabled
>      >      Setting load balancing timer type as 'double'
>      >      ### whether C++ compiler works
>      >      #include <stdio.h>
>      >      void foo(void) {
>      >              printf("Hello, world!\n");
>      >      }
>      >      pgCC -fPIC -DCMK_FIND_FIRST_OF_PREDICATE=1 --no_using_std
>      >      -I../include -I. -c
>      >      test.cpp -o test.o
>      >      ./configure: line 2145: pgCC: command not found
>      >      This is with PGI 16.10, which only provides pgc++ and not
>      pgCC. I
>      >      tried setting
>      >      the shell env var pgCC=pgc++ but that does not help. My build
>      >      command is:
>      >      ./build charm++ mpi-linux-x86_64 pgcc --build-shared
>      >      What is the recommended way to build with the pgi compilers?
>      >
>      >    Apparently we're going to have to update our scripts some, to
>      point at
>      >    the new compiler name.
>      >    In the meanwhile, you can edit the name from pgCC to pgc++ in
>      >    src/arch/common/cc-pgcc.sh and then your build should at least
>      be able
>      >    to try to proceed.
>      >
>      >      Thanks,
>      >      Jozsef
>      >
>      > References
>      >
>      >    1. 
> mailto:[4]jbakosi AT lanl.gov
> 
> References
> 
>    1. 
> mailto:jbakosi AT lanl.gov
>    2. 
> https://devtalk.nvidia.com/default/topic/977515/openacc-toolkit/-openacc-c-the-global-scope-has-no-quot-acos-quot-using-acos/
>    3. 
> mailto:jbakosi AT lanl.gov
>    4. 
> mailto:jbakosi AT lanl.gov