Thanks for the report of the broken link. It is now fixed. I have also
added a paragraph about --enable-mpirun-prefix-by-default to
Ashley Pittman wrote:
> That looks like just what I need, thank you for the quick response.
> The closest I could find in the FAQ is this entry which has a broken
> link to the second entry.
> I need to avoid modifying ld.so.conf or setting up aliases so openmpi
> can be properly loaded and unloaded with the modules command.
> On Tue, 2008-03-04 at 09:37 -0500, Tim Prins wrote:
>> Hi Ashley,
>> Yes, you can have this done automatically. Just use the
>> '--enable-mpirun-prefix-by-default' option to configure.
>> I'm actually a bit surprised this is not in the FAQ. I'll have to add it.
>> Hope this helps,
>> Ashley Pittman wrote:
>>> I work for medium sized UK based ISV and am packaging open-mpi so that
>>> is can be made available as an option to our users, so far I've been
>>> very impressed by how smoothly things have gone but I've got one problem
>>> which doesn't seem to be covered by the FAQ.
>>> We install openmpi to /opt/openmpi-1.2.5 and are using the modules
>>> command to select which mpi to use, the modules command correctly sets
>>> PATH to pick up mpicc and mpirun on the head node however the issue
>>> comes with running a job, users need to specify -prefix on the mpirun
>>> command line. Is there a way to specify this in the environment so I
>>> could make it happen automatically as part of the modules environment?
>>> I've searched the archives for this, the closest I can find is this
>>> exchange in 2006, if I specify a full path to mpirun then it does the
>>> right thing but is there a way to extend this functionality to the case
>>> where mpirun is run from path?
>>> Yours, Ashley Pittman.
>>> users mailing list
>> users mailing list
> users mailing list