Charm++ parallel programming system

[Jeff Hammond <jeff.science AT gmail.com>]

You should let ALCF know about your softenv issues.

Jeff

On Tue, Jan 10, 2017 at 3:15 PM, Jozsef Bakosi <jbakosi AT gmail.com> wrote:

Well, apparently, if I have in ~/.soft

+mpiwrapper-xl

@default

i.e., no +mpiwrapper-bgclang, and I do

soft add +mpiwrapper-bgclang,

it builds fine. That's good enough for me, but go figure.

Thanks,

J

On Tue, Jan 10, 2017 at 3:45 PM, Jozsef Bakosi <jbakosi AT gmail.com> wrote:

Oh, I just noticed that enabling both +mpiwrapper-xl +mpiwrapper-bgclang seems to totally screw up the environment, as mpic++ now points to the XL wrapper. I guess, the best would be if the build did not depend on xl for the bgclang build.

On Tue, Jan 10, 2017 at 3:37 PM, Jozsef Bakosi <jbakosi AT gmail.com> wrote:

Okay, when I enable the xl suite in .soft so that my .soft file contains the following:

------

    +mpiwrapper-xl

    +mpiwrapper-bgclang

@default

------

I get a different error:

checking "whether C++ compiler supports C++11 without flags"... "no"

checking "whether C++ compiler supports C++11 with '-std=c++0x'"... "no"

checking "whether C++ compiler supports C++11 with '-qlanglvl=extended0x'"... "yes"

checking "whether C++ compiler supports C++11 with '--c++11'"... "no"

checking "whether C++ compiler supports C++11 with '-h std=c++11'"... "no"

Charm++ requires some C++11 support, but doesn't know the flag to enable it

Based on this, it seem like you guys are detecting the std flag based on -std=c++0x, which I think now should be -std=c++11. Clang will support that one. Though, I still don't understand why you don't reproduce this problem.

In addition, the fact that now I am getting this different error, it might mean that the build still requires +mpiwrapper-bgclang in .soft. (I don't know if this is a problem or not, or desirable or not - I don't know enough about the BG/Q environment.)

Thanks,

Jozsef

On Tue, Jan 10, 2017 at 3:27 PM, Jozsef Bakosi <jbakosi AT gmail.com> wrote:

What do you have in your ~/.soft? Do you enable +mpiwrapper-xl by any chance? Because I don't...

On Tue, Jan 10, 2017 at 2:25 PM, Sam White <white67 AT illinois.edu> wrote:

Hmm, I verified this just now and when I do the following two commands it works for me. Maybe there is something wrong with your soft file, but I am not familiar with the environment enough to say.

$ soft add +mpiwrapper-bgclang

$ ./build charm++ mpi-bluegeneq clang --build-shared --with-production -j48 -O3 -DNDEBUG

-Sam

On Tue, Jan 10, 2017 at 2:47 PM, Jozsef Bakosi <jbakosi AT gmail.com> wrote:

Thanks, Sam,

I am trying to build using:

$ build charm++ mpi-bluegeneq clang --build-shared --with-production -j48 -O3 -DNDEBUG

and I still get:

mpixlcxx not in default path; please load xl wrappers for MPI

I have in ~/.soft:

+mpiwrapper-bgclang

@default

This is attempting to build commit f68880df5d3, which includes "ba9fa6e9ccd mpi-bluegeneq: add support for building on bgclang's MPI wrappers".

What am I doing wrong?

Thanks,

Jozsef

On Tue, Jan 3, 2017 at 3:49 PM, Sam White <white67 AT illinois.edu> wrote:

Hi Jozsef,

We added support for using the bgclang compiler after the 6.7.1 release to the pamilrts-bluegeneq target, but not yet to the mpi-bluegeneq target. I have just added that support and it should be merged before the upcoming 6.8.0 release, so thanks for pointing that out!
https://charm.cs.illinois.edu/gerrit/#/c/2099/

If you want to use the pamilrts version now (on mainline charm), here is the build command:
$ soft add +mpiwrapper-bgclang $ ./build charm++ pamilrts-bluegeneq clang

-Sam

On Tue, Jan 3, 2017 at 4:10 PM, Jozsef Bakosi <jbakosi AT gmail.com> wrote:

Hi folks,

I'm trying to build on mira using the bgclang compiler suite? Has this ever been attempted or it is only the xl suite that is supported? I get:

mpixlcxx not in default path; please load xl wrappers for MPI

Here is the build command:

build charm++ mpi-bluegeneq --build-shared --with-production -j48 -O3 -DNDEBUG

Thanks,

Jozsef

--

Jeff Hammond
jeff.science AT gmail.com
http://jeffhammond.github.io/