mething compiled with x.y.*
will run on x.y+1.* without the need for you to recompile.
mixing x.y and x.y+1 on the same machinefile (and that's what we are
talking about) can only work by accident, not by design.
>>
>> On Oct 29, 2010, at 12:12 PM, guillaume ranquet wrote:
>&
:
> George --
>
> Scott's patch was different than the one you applied. Apparently, his fixes
> this user's problem (I don't know if Guillaume tested yours).
>
> Which one wins?
>
>
>
> On Jun 3, 2010, at 9:49 AM, Scott Atchley wrote:
>
>> On Jun 3, 2010, at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I snipped some parts of the exchange and responding to 2 mails in this
one. (this may not be proper netiquette on this ML?)
On 06/02/2010 03:54 PM, Jeff Squyres wrote:
> What happens if you run:
>
> ~/openmpi-1.4.2-bin/bin/mpirun --mca btl
loc2_disable to 1 (for good measure, ensure that it's
> set on all nodes where you are running Open MPI).
>
>
>
> On May 31, 2010, at 11:02 AM, guillaume ranquet wrote:
>
> we use a slightly modified openmpi-1.4.1
>
> the patch is here:
>
> --- ompi/mca/btl/tcp/btl_
wrote:
> What OMPI version are you using?
>
> On May 31, 2010, at 5:37 AM, guillaume ranquet wrote:
>
> Hi,
> I'm new to the list and quite new to the world of MPI.
>
> a bit of background:
> I'm a sysadmin and have to provide a working environment (debian base)
> for rese
sue, that disables the
openmpi "leave_pinned" option?
the various questions I have:
is this bug/behaviour known?
if so, is there a better workaround?
as I'm not an openmpi user, I don't really know if it's considered
acceptable to have this option disabled?
does the list want more details
