On Nov 21, 2005, at 10:34 AM, Troy Telford wrote:
On Mon, 21 Nov 2005 06:00:05 -0700, Jeff Squyres mpi.org>
wrote:
These warnings will likely be removed (or, more specifically, only
displayed if requested) once we include the feature to display which
BTL components/networks are being used at r
On Mon, 21 Nov 2005 06:00:05 -0700, Jeff Squyres
wrote:
Although George fixed the MX-abort error, let me clarify the rationale
here...
You are correct that at run-time, OMPI tries to load an run every
component that it finds. So if you have BTL components build for all
interconnects, OMPI w
Although George fixed the MX-abort error, let me clarify the rationale
here...
You are correct that at run-time, OMPI tries to load an run every
component that it finds. So if you have BTL components build for all
interconnects, OMPI will query each of them at run-time and try to use
the
The MX library call exit if the error handler is not set before the
initialization. This error get fixed, it will get into the tarball
shortly.
Meanwhile you can use the btl_base_exclude=mx,gm in order to force them to
be skipped.
Thanks,
george.
On Thu, 17 Nov 2005, Troy Telford wrot
I wouldn't be suprised if this is simply an issue of configuration:
In my test cluster, I've got Myrinet, InfiniBand, and Gigabit Ethernet
support.
My understanding is that when you use 'mpirun' without specifying an MCA
(including systemwide and/or user configurations in ~/.openmpi) , Open
