Yes - but Marco said he was going to look into it. I meant that I would fix
the problem George identified, although it doesn't fix the problem Marco
hit.
Sorry for the confusion
On Wed, Mar 5, 2014 at 2:48 PM, Paul Hargrove wrote:
> Wait a second...
>
> Unless I am missing something Marco's e
Wait a second...
Unless I am missing something Marco's error means that Cygwin *did* return
INADDR_ANY.
According to George's research that shouldn't happen (unless on XP or older
and host is an empty string).
So, changing the code to check for INADDR_NONE just ignores what should be
an impossibl
Cool - I'll make the correction. Thx!
On Wed, Mar 5, 2014 at 2:08 PM, George Bosilca wrote:
> I'm afraid the snippet pointed by Ralph is incorrect, as INADDR_ANY should
> not be a valid return for inet_addr. Here is a quick check on different
> OSes.
>
> On Linux, the man Page states:
>
> If t
I’m afraid the snippet pointed by Ralph is incorrect, as INADDR_ANY should not
be a valid return for inet_addr. Here is a quick check on different OSes.
On Linux, the man Page states:
> If the input is invalid, INADDR_NONE (usually -1) is returned.
On Mac OS X:
> The constant INADDR_NONE is re
On 05/03/2014 04:06, Ralph Castain wrote:
The code generating the error is here:
in->sin_addr.s_addr = inet_addr(host);
if (in->sin_addr.s_addr == INADDR_ANY) {
return ORTE_ERR_BAD_PARAM;
}
The address is resolving to INADDR_ANY instead of a regular ad
The code generating the error is here:
in->sin_addr.s_addr = inet_addr(host);
if (in->sin_addr.s_addr == INADDR_ANY) {
return ORTE_ERR_BAD_PARAM;
}
The address is resolving to INADDR_ANY instead of a regular address. Does
cygwin require some other method for r
noted on cygwin with 1.7.4 and on 1.7.5rc1
$ mpirun -n 4 ./hello_c.exe
[MATZERI:06212] [[62628,1],0] ORTE_ERROR_LOG: Bad parameter in file
/pub/devel/openmpi/openmpi-1.7.5rc1-1/src/openmpi-1.7.5rc1/orte/mca/oob/tcp/oob_tcp.c
at line 292
[MATZERI:05620] [[62628,1],1] ORTE_ERROR_LOG: Bad paramete
