You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
opal/mca/if: fix "struct sockaddr_in" and OS checks
Found a few more places we needed to adjust for changing from
OPAL_CHECK_OS_FLAVORS to OAC_CHECK_OS_FLAVORS.
Also, in the opal/mca/if components, we have configure.m4 scripts that
explicitly check $opal_found_sockaddr. This was a problem for a few
reasons:
1. We just deleted the setting of $opal_found_sockaddr from the
previous OPAL_CHECK_OS_FLAVORS macro (*why* it was set in that
macro isn't really clear -- "struct sockaddr" doesn't really have
anything to do with checking OS flavors).
2. The old OPAL_CHECK_OS_FLAVORS macro actually checking for "struct
sockaddr_in", not "struct sockaddr". This led to a lot of
confusion in this round of debugging.
Also, the additional network header checks and check for struct
sockaddr_in in OPAL_CHECK_OS_FLAVORS were redundant: they were already
being performed in OMPI's top-level configure.ac. Deleting these
redundant tests -- and indeed, deleting all of OPAL_CHECK_OS_FLAVORS
-- is fine. But we did need to set a global variable for the
opal/mca/if/*/configure.m4 scripts to check. This commit therefore
adjusts the top-level configure.ac script to explicitly save the
result of checking for "struct sockaddr_in" into
$opal_found_sockaddr_in.
Finally, slightly change the AC_MSG_RESULT output in the
opal/mca/if/*/configure.m4 scripts to make it clear that the check for
"struct sockaddr_in" is *not* using the regular AC_CHECK_TYPES method.
Instead, the "cached" results it is getting are from OPAL caching, not
regular Autoconf test caching. Do this because the "(cached)" output
that it previously emitted caused considerable confusion during this
round of debugging (i.e., I assumed it was coming from regular
Autoconf test caching, which is an entirely different mechanism).
Signed-off-by: Jeff Squyres <[email protected]>
0 commit comments