Looks ok to me. Go ahead and commit to trunk and file a v1.5 CMR; you can say
I reviewed it.
On Feb 8, 2011, at 5:52 AM, Damien Guinier wrote:
> hi all
>
> On v1.5 branch, can we add MPI_ROOT variable on:
>/%{shell_scripts_path}/%{shell_scripts_basename}.sh
> and /%{shell_scripts_path}/%{s
This is the beauty of the MPI standard. Two reading can lead to two different
understanding and therefore implementations ...
On Feb 8, 2011, at 03:24 , Tobias Hilbrich wrote:
> Hi George,
>
> thanks for your fast answer! I hate the cancel too, but am a tool developer
> that unfortunately has
hi all
On v1.5 branch, can we add MPI_ROOT variable on:
/%{shell_scripts_path}/%{shell_scripts_basename}.sh
and /%{shell_scripts_path}/%{shell_scripts_basename}.csh
with the value : MPI_ROOT=%{_prefix}
The variable MPI_ROOT facilitate launch script creation. This variable
is asked by custom
Hi George,
thanks for your fast answer! I hate the cancel too, but am a tool developer
that unfortunately has to deal with it :( Likely, implementing the
functionality for something like this in an MPI implementation is far more
horrible ...
My MPI standard says the following (MPI 2.2):
- "A
