On Wed, Feb 25, 2015 at 4:14 PM, Jeff Squyres (jsquyres) wrote:
> On Feb 25, 2015, at 4:17 PM, Paul Hargrove wrote:
> >
> > The Linux and Solaris verbs issues are resolved.
>
> Good.
>
> > The BSD results are unchanged.
>
> That means this, right:
>
[...snip...]
Yes, that is what I mean.
>
On Feb 25, 2015, at 4:17 PM, Paul Hargrove wrote:
>
> The Linux and Solaris verbs issues are resolved.
Good.
> The BSD results are unchanged.
That means this, right:
--
On FreeBSD-{8,9,10}/amd64 I don't get past "make check":
Segmentation fault (core dumped)
FAIL: dlopen_test
Oddly, my Fr
Hey folks
Given that some number of us will be at the MPI Forum next week, do we have a
quorum available for the weekly telecon? Who would be able to make it?
Me: available
Ralph
The Linux and Solaris verbs issues are resolved.
The BSD results are unchanged.
-Paul [Sent from my phone]
On Feb 25, 2015 12:29 PM, "Jeff Squyres (jsquyres)"
wrote:
> Probably no point in re-testing the ones that already worked.
>
> The m4 typo affected systems that require extra libraries (e.
On Wed, Feb 25, 2015 at 12:29 PM, Jeff Squyres (jsquyres) <
jsquy...@cisco.com> wrote:
> /me wishes yet again that shell scripting had a "strict" mode that would
> yell at you when you use "$foop" instead of "$foo" (and $foop doesn't
> exist/was never set).
See http://redsymbol.net/articles/unof
Probably no point in re-testing the ones that already worked.
The m4 typo affected systems that require extra libraries (e.g., libibverbs, or
even libdl). Instead of filling in _LIBS, _LIBS was accidentally
being left empty.
/me wishes yet again that shell scripting had a "strict" mode that wo
I've queued new tests for the platforms w/ verbs-related failures.
Is there any point retesting the BSDs as well?
-Paul
On Wed, Feb 25, 2015 at 12:02 PM, Jeff Squyres (jsquyres) <
jsquy...@cisco.com> wrote:
> Sorry, I meant:
>
> bot:hargrove
>
>
> > On Feb 25, 2015, at 3:01 PM, Jeff Squyres (jsq
Sorry, I meant:
bot:hargrove
> On Feb 25, 2015, at 3:01 PM, Jeff Squyres (jsquyres)
> wrote:
>
> Per my prior mail, m4 typo fixed -- could you release the hounds again?
>
>> On Feb 25, 2015, at 2:13 PM, Paul Hargrove wrote:
>>
>>
>> On Wed, Feb 25, 2015 at 10:17 AM, Paul Hargrove wrote:
Per my prior mail, m4 typo fixed -- could you release the hounds again?
> On Feb 25, 2015, at 2:13 PM, Paul Hargrove wrote:
>
>
> On Wed, Feb 25, 2015 at 10:17 AM, Paul Hargrove wrote:
> I did that and just shipped a tarball to get Hargroved.
>
> Tests have been dispatched... I will report c
Yeah, I had a typo in an m4 section of code. I'm making a new tarball now.
> On Feb 25, 2015, at 2:41 PM, Paul Hargrove wrote:
>
> FYI:
>
> On several systems where Jeff's tarball for pr410 ran fine yesterday, I am
> seeing errors in today's tarball related to either libverbs or mca_oob_ud.
>
FYI:
On several systems where Jeff's tarball for pr410 ran fine yesterday, I am
seeing errors in today's tarball related to either libverbs or mca_oob_ud.
Issue #1:
On Solaris verbs support is now rejected at configure time.
Configure output appears below as "1)"
Issue #2:
On Linux I get undefi
On Wed, Feb 25, 2015 at 10:17 AM, Paul Hargrove wrote:
> I did that and just shipped a tarball to get Hargroved.
>>
>
> Tests have been dispatched... I will report complete results later today.
> The first of the BSD results should be in soon, and I'll plan to report
> go/nogo.
>
"NOGO"
I don'
On Feb 25, 2015, at 1:17 PM, Paul Hargrove wrote:
>
> Assuming that the new tarball finds dlopen() support in libc on the BSDs then
> I am not going to encounter the new behavior unless I manually disable
> (something like "--enable-mca-no-build=dl-dlopen", right?). To be honest,
> any platfo
On Wed, Feb 25, 2015 at 9:56 AM, Jeff Squyres (jsquyres) wrote:
> On Feb 25, 2015, at 11:51 AM, Dave Goodell (dgoodell)
> wrote:
> >
> >> This is a good question: what should we do here?
> >>
> >> 1. Abort the configure (e.g., insist that the user install libltdl or
> --disable-dlopen)
> >
> > I
On Feb 25, 2015, at 11:51 AM, Dave Goodell (dgoodell)
wrote:
>
>> This is a good question: what should we do here?
>>
>> 1. Abort the configure (e.g., insist that the user install libltdl or
>> --disable-dlopen)
>
> I'd do this. A clear message should make this no big deal for users, and in
New tarball is there that fails if --disable-dlopen is not specified and
neither dl component can be built.
Also has the fix for "look for dlopen in standard libs and then in libdl".
> On Feb 25, 2015, at 11:52 AM, Paul Hargrove wrote:
>
>
> On Wed, Feb 25, 2015 at 8:45 AM, Jeff Squyres (jsq
On Wed, Feb 25, 2015 at 8:45 AM, Jeff Squyres (jsquyres) wrote:
> > SECOND:
> > On {Free,Net,Open}BSD dlopen() appears in libc, not in libdl.
> > So, I suspect one *should* be able to compile dl:dlopen on all these
> systems with the proper configure tests.
>
> Cool; I'll fix this. ...done.
L
On Feb 25, 2015, at 10:45 AM, Jeff Squyres (jsquyres)
wrote:
> On Feb 24, 2015, at 5:44 PM, Paul Hargrove wrote:
>>
>> FIRST:
>> I believe that *something* should have occurred when no dl component could
>> be built.
>> Either the build should have been aborted or it could/should have switche
On Feb 24, 2015, at 5:44 PM, Paul Hargrove wrote:
>
> FIRST:
> I believe that *something* should have occurred when no dl component could be
> built.
> Either the build should have been aborted or it could/should have switched to
> building everything static.
> However, the failure at runtime s
You need to configure OMPI --with-mxm=/path/to/mxm in order to use Yalla.
In addition, Yalla is only available on Master as it is a new feature. If
you want to play with other PMLs in the release branch, you may try the MXM
MTL (again, you first need to configure your build to use the MXM library)
20 matches
Mail list logo
