Thanks for the reply. What exactly is the purpose of the following files? hydra_pmi_proxy hydra_nameserver hydra_persist They are all in the 'bin' directory. T On 09/29/2013 08:38 PM, [email protected] wrote:
Message: 2 Date: Sun, 29 Sep 2013 09:51:44 -0500 From: Pavan Balaji<[email protected]> To: [email protected] Subject: Re: [mpich-discuss] packaging mpiexec with static binaries Message-ID:<[email protected]> Content-Type: text/plain; charset=us-ascii
On Sep 29, 2013, at 9:24 AM, Tabrez Ali wrote:
Now if I create a static binary of my code for users who find compiling from source daunting (dont ask why) then they can easily run in serial as there is no need for mpiexec but then they cant utilize the extra cores on their PCs.
Is there a way to package mpiexec along with the static binary? From testing it seems that if I ship along mpiexec.hydra and hydra_pmi_proxy then it appears to work as follows:
./mpiexec.hydra -n X ./mycode
But I am not sure if it is the right approach. Any tips/advice on packaging mpirun/mpiexec along (if possible) is highly appreciated.
Depends on what all features in mpiexec you are using. Typically shipping the contents of the bin and lib directories in your install path should be sufficient, but it assumes that your customers have the same dependency libraries as you (e.g., libc).
Alternatively, you could ask them to do an "apt-get/port/brew/yum install" of mpich on their platform. It'll either automatically build mpich on their machine or download binaries.
http://www.mpich.org/downloads/
-- Pavan
-- Pavan Balaji http://www.mcs.anl.gov/~balaji
------------------------------