Charm++ parallel programming system

[Jozsef Bakosi <jbakosi AT lanl.gov>]

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 
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]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:jbakosi AT lanl.gov