Charm++ parallel programming system

[Phil Miller <mille121 AT illinois.edu>]

On Mon, Jun 21, 2010 at 13:15, Haowei Huang 
<huangh AT in.tum.de>
 wrote:
>     Hi Chee Wai , Phil,
>           I think I find the problem. I built a charm++ on Cray without
> specified pgcc and pgf90 so a building directory called mpi-crayxt was
> generated. Now I use command  " ./build Tau mpi-crayxt
> --tau-makefile=$TAU_MAKEFILE -O3" to build Tau under charm++ root
> directory mpi-crayxt and everything is fine. A interesting question is that
> when we specify pgcc and pgf90 there is a linking error shows mpi.h couldn't
> find. Do you have any idea or suggestion about this? Thanks a lot.

When you specify the use of particular compiler binaries, the charm++
build scripts will use those directly, as you asked, rather than the
wrappers that your system administrators provide to set include paths
appropriately. On Jaguar and Kraken, they use a module system to
select what compiler gets invoked when one runs 'cc', 'CC', 'mpicc',
or 'mpiCC', with those names referring to wrappers that point at the
right MPI and other library headers.

Phil