"Jeff Squyres (jsquyres)" :
>I think that the best thing to do would be to add some relevant tests in
>configure for IPv6 headers/types/whatever, and then put appropriate
>#if's around in the code.
This is exactly the way we'd like to start. But right now I'm on a
conference and then out for vacat
machine without IPv6 stuff,
then it's just a matter of adjusting the #if's, etc.
> -Original Message-
> From: devel-boun...@open-mpi.org
> [mailto:devel-boun...@open-mpi.org] On Behalf Of Ralf Wildenhues
> Sent: Wednesday, April 05, 2006 4:33 AM
> To: de...@ope
* Christian Kauhaus wrote on Tue, Apr 04, 2006 at 07:04:43PM CEST:
>
> If someone could provide us an account on a non-IPv6-enabled Unix
> machine (like an old Solaris or HP-UX), this would be very helpful.
> This way we can be sure not to break the build with our patches.
FWIW, I may be able to
Ralph Castain :
> There has been a lot of discussion about IPv6 in Open MPI and
> OpenRTE recently. My comments here relate solely to OpenRTE and are
> intended to help provide some clarity to the discussion.
Thank you very much for your helpful clarifications. We are currently
collecting so
There has been a lot of discussion about IPv6 in Open MPI and OpenRTE
recently. My comments here relate solely to OpenRTE and are intended to
help provide some clarity to the discussion.
OpenRTE communications are done via the Runtime Messaging Library (RML)
API. The RML is really a strategy l