Charm++ parallel programming system

[Jozsef Bakosi <jbakosi AT gmail.com>]

Forgot to CC the list.

---------- Forwarded message ----------
From: Jozsef Bakosi <jbakosi AT gmail.com>
Date: Mon, May 9, 2016 at 12:09 PM
Subject: Re: [charm] Build on mac os
To: Jeff Hammond <jeff.science AT gmail.com>

Thanks, Jeff,

It turned out that my problem was that my charm++ build was picking up the system-wide clang and not the one I wanted it to.

This stackoverflow answer gave me a clue. My system-wide clang is most likely based on an older clang than 3.7 and this gave me the error.

The solution was to enable the correct newer clang that I installed via macports by 'port select clang mp-clang-3.8'. I needed this anyway, because I'm building on the mpi layer so I also need to correctly match the mpi wrappers with the underlying compilers.

Thanks,

Jozsef

On Mon, May 9, 2016 at 11:00 AM, Jeff Hammond <jeff.science AT gmail.com> wrote:

https://github.com/ParRes/Kernels/blob/master/travis/install-charm%2B%2B.sh is my recipe for Charm++ on Mac OS. You can verify it works by visiting https://travis-ci.org/ParRes/Kernels/jobs/127622171, as one instance. You can see from list archives that Charm++ experts helped me debug my Travis configs so I hope they are correct. 

Jeff 

On Monday, May 9, 2016, Jozsef Bakosi <jbakosi AT gmail.com> wrote:

Hi folks,

I'm using macports and installed the package openmpi-clang38, activated it by 'port select --set mpi openmpi-clang38-fortran', then attempt to build with

$ build charm++ mpi-darwin-x86_64 --build-shared -j8 -stdlib=libc++ -g

but I get errors, such as

invalid deployment target for -stdlib=libc++ (requires OS X 10.7 or later)

Is this because the Charm++ build does not pick up the macports-installed clang but the system-wide (older) one?

What is the recommended/easiest way to build Charm++ on Mac OS X?

Thanks,

Jozsef

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