Larry,
Sorry for not updating this thread. The issue was identified and fixed by
Rainer in r25290 (https://svn.open-mpi.org/trac/ompi/changeset/25290). Please
read the comments and the linked thread on the Intel forum for more info about.
I couldn't find a trace of this being fixed in the 1.4 s
Fixed by r25313.
Thanks,
george.
On Oct 11, 2011, at 16:54 , Ralph Castain wrote:
>> The patches (25245, 25248) proposed so far as a solution to this problem
>> should be removed, as they do not really solve the problem, instead they
>> alleviate the symptoms. From here there are two pos
George,
I have not had time to look over the 1.4.3 make check failure for
Intel 2011.6.233 compilers. Have you?
I had planned to get 1.4.3 compiled on all six of our compilers using
the latest compiler releases. I was putting off upgrading to 1.4.4 or
1.5.x until after that to minimize
On Oct 17, 2011, at 18:23 , Ralph Castain wrote:
>
> On Oct 17, 2011, at 4:14 PM, George Bosilca wrote:
>
>> Ralph,
>>
>> I have a concern about the code below (snippet from the commit 25303). You
>> moved the setting of proc_flags and proc_name in a function named set_arch.
>> As the name a
This commit put the mpirun process in an infinite loop for the simple case
mpirun -np 2 --mca orte_default_hostfile machinefile --bynode *my_app*
george.
On Oct 17, 2011, at 15:49 , r...@osl.iu.edu wrote:
> Author: rhc
> Date: 2011-10-17 15:49:04 EDT (Mon, 17 Oct 2011)
> New Revision: 25302
>
On Oct 17, 2011, at 4:14 PM, George Bosilca wrote:
> Ralph,
>
> I have a concern about the code below (snippet from the commit 25303). You
> moved the setting of proc_flags and proc_name in a function named set_arch.
> As the name and the lengthy comment above it indicate, the scope of this
>
Ralph,
I have a concern about the code below (snippet from the commit 25303). You
moved the setting of proc_flags and proc_name in a function named set_arch. As
the name and the lengthy comment above it indicate, the scope of this
particular function is to set the architecture of the remote pro