It depends on whether you are linking your library statically or dynamically. If you are linking statically, the linker puts everything in one executable that is sent to all of the nodes. If you do it dynamically, you need to make sure your libraries are available on all of the nodes you will be using (usually by using something like NFS to mirror your home directory across the cluster. You will also need to make sure your environment is set up correctly to allow the libraries to be found on the remote process, usually via an environment variable such as LD_LIBRARY_PATH. 

Wesley

On Jun 6, 2013, at 6:18 AM, Alejandro Allievi <alejandro.allievi@gmail.com> wrote:

H
i  

When linking to personal libraries using MPICH2, how does each process access them in a distributed environment?? Does the linker actually 
combines
everything 
into a single
executable
program
and "sends a copy" of entire executable to each process even though not all processes may use the libraries?? Can somebody shed some light on the entire linking process??

Thanks for any help!!

Alejandro
_______________________________________________
discuss mailing list     discuss@mpich.org
To manage subscription options or unsubscribe:
https://lists.mpich.org/mailman/listinfo/discuss