We think that this is ready. I have sent a note to our BSD friends asking them
to test.
If all works out ok, we plan on bringing this back to the trunk.
On Aug 31, 2010, at 5:03 PM, Barrett, Brian W wrote:
> Ah, I see, I misunderstood how you organized things. Never mind :).
>
>
> Brian
>
Ah, I see, I misunderstood how you organized things. Never mind :).
Brian
On Aug 31, 2010, at 2:48 PM, Ralph Castain wrote:
> I believe it is there, but correct me if not. All of the component
> configure.m4s depend on a test for sockaddr_in, which I believe RS will fail
> - yes?
>
> On Tue
I should also have noted that:
1. all of the opal_ifxxx functions still have their "no-op" versions when
struct sockaddr_in is not present.
2. we still "lazy discover" interfaces, so the new opal_if framework is
-not- opened unless you call one of the opal_ifxxx functions and get a
non-no-op vers
I believe it is there, but correct me if not. All of the component
configure.m4s depend on a test for sockaddr_in, which I believe RS will fail
- yes?
On Tue, Aug 31, 2010 at 2:42 PM, Barrett, Brian W wrote:
> Ralph -
>
> My Red Storm dev cluster isn't working right now, but I didn't see an
> opt
Ralph -
My Red Storm dev cluster isn't working right now, but I didn't see an option
for no if support at all. Did I miss it, or are we going to have to add it
later?
Thanks,
Brian
On Aug 31, 2010, at 2:28 PM, Ralph Castain wrote:
> Per a discussion on the devel telecon a week or two ago, I
