Charm++ parallel programming system

[Tom Quinn <trq AT astro.washington.edu>]

Hi Britton,

I wonder which application you are using?

The way I got it to work was to use the "++remote-shell" option to 
charmrun.  E.g. on stampede, I would start the application with:

./charmrun +p $proc ++mpiexec ++remote-shell $HOME/bin/mympiexec ./ChaNGa 
agora.param

and in $HOME/bin/mympiexec, I would set environment variables (again this 
is specific for stampede):

#!/bin/csh
# echo command: $*
setenv LD_LIBRARY_PATH $HOME/local/lib:$LD_LIBRARY_PATH
shift; shift; exec ibrun $*

But perhaps the charm developers have a better idea.

Tom Quinn       Astronomy, University of Washington
Internet:       
trq AT astro.washington.edu
Phone:          206-685-9009

On Tue, 23 May 2017, Britton Smith wrote:

> Hi everyone,
> I'm very new to charm++, so please forgive the basic nature of this
> question.
>
> I've compiled an application with charm++ that depends on a few other
> libraries that I've installed in a local directory.  The code compiles just
> fine, but when I try to run it with charmrun, the locally installed
> libraries can't be found.  I set my LD_LIBRARY_PATH to include the local
> installation paths in a .bash_aliases file, but that doesn't seem to work
> with charmrun.  The code runs correctly when I include the "++local"
> option, but not without.
>
> Is there another way to provide library paths for executables to charmrun?
>
> In case it helps, I'm using charm++ 6.7.1 on a linux machine running ubuntu
> 17.04.
>
> Thanks for the help,
>
> Britton
>
> -- 
> Dr. Britton Smith
> Assistant Research Scientist
> San Diego Supercomputer Center
> University of California, San Diego
> T: +1 858 822 0936
> F: +1 858 534 5117