[OMPI devel] Free list warning

It looks like everything in ompi_free_list has been tied together and labeled as deprecated. So I’m getting this warning: In file included from class/ompi_free_list.c:12:0: ../opal/class/ompi_free_list.h: In function 'ompi_free_list_init_ex': ../opal/class/ompi_free_list.h:100:5: warning:

Re: [OMPI devel] Tues Mar 3rd telecon

I will also be available but suggest we skip next Tuesday. On Feb 25, 2015 5:04 PM, "Ralph Castain" wrote: > 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?

Re: [OMPI devel] Free list warning

Is it just complaining that the inline functions are deprecated or some code still using ompi_free_list_t? If it is the former I will go ahead and remove the dummy implementation. -Nathan On Wed, Feb 25, 2015 at 09:00:26PM -0800, Ralph Castain wrote: >It looks like everything in

Re: [OMPI devel] Free list warning

So far as I can tell, it is complaining about the definitions - the error doesn’t indicate anyone is using it > On Feb 26, 2015, at 8:07 AM, Nathan Hjelm wrote: > > > Is it just complaining that the inline functions are deprecated or some > code still using ompi_free_list_t?

Re: [OMPI devel] Free list warning

Ok, I put that implementation there to ease the transition for off-master components. Removing now. -Nathan On Thu, Feb 26, 2015 at 08:09:27AM -0800, Ralph Castain wrote: > So far as I can tell, it is complaining about the definitions - the error > doesn’t indicate anyone is using it > > > On

Re: [OMPI devel] [mpich-discuss] ROMIO+Lustre problems in OpenMPI 1.8.3

On 11/07/2014 06:26 AM, Ralph Castain wrote: Hi Rob Following up on this: I cannot find any reference to XOPEN_SOURCE in our included ROMIO source for Lustre. I only found one reference anywhere in ROMIO: romio/adio/ad_xfs/ad_xfs.h:11:#define _XOPEN_SOURCE 500 Any other suggestions on what

[OMPI devel] Using the Github ompi-release bot

I forgot to mention that you must change your Github flag to publicly state that you are part of the Open MPI organization to be able to use the ompi-release bot. Go to this page: https://github.com/orgs/open-mpi/people Find yourself, and change your membership from "Private" (the

[OMPI devel] opal_verbs_want_fork_support question

Hi Folks, Just tried to build a fresh head of master and am getting opal_verbs_want_fork_support as undefined symbol when trying to build opal lib. Any ideas on where this should go? It would be nice to get jenkins checking everything, or at least a light weight travis check. Howard

Re: [OMPI devel] opal_verbs_want_fork_support question

Just pushed some fixes into the trunk. However, the naming of the MCA variable for verbs fork is not following our usual requirements. I guess the code owners should address this topic. George. On Thu, Feb 26, 2015 at 4:52 PM, Howard Pritchard wrote: > Hi Folks, > >

Re: [OMPI devel] opal_verbs_want_fork_support question

Howard -- It looks like https://github.com/open-mpi/ompi/pull/415 was merged before it was ready. George then did some commits to try and fix things, but I still don't think they were right. I put some comments on #415 after it was merged; I don't know if they got mailed out or not. > On

Re: [OMPI devel] opal_verbs_want_fork_support question

A better fix is underway. One that will be checked on a verbs-enabled environment. George On Thu, Feb 26, 2015 at 5:08 PM, Jeff Squyres (jsquyres) wrote: > Howard -- > > It looks like https://github.com/open-mpi/ompi/pull/415 was merged before > it was ready. George

[OMPI devel] printf format warnings on master

Clang noted the following on FreeBSD-10/amd64 using the current master tarball: Making check in threads make opal_thread opal_condition CC opal_thread.o CCLD opal_thread CC opal_condition.o

[OMPI devel] BML changes

This message is mostly for Nathan, but figured I would go with the wider distribution. I have noticed some different behaviour that I assume started with this change. https://github.com/open-mpi/ompi/commit/4bf7a207e90997e75ba1c60d9d191d9d96402d04 I am noticing that the openib BTL will also

Re: [OMPI devel] opal_verbs_want_fork_support question

Sorry for the mess, it took me few commits and few cleanups to have it back in a workable state (and without other pending work from my own branches). I also changed the naming of few MCA parameters to reflect upon their location (OPAL and common and verbs). However, I create the corresponding

[OMPI devel] mtl:psm configury build broken in master

I have been testing mtl:psm on a very old system. Sometime pretty recently (this week I think), this started to break at configure time: --- MCA component mtl:psm (m4 configuration macro) checking for MCA component mtl:psm compile mode... dso checking --with-psm value... sanity check ok

[OMPI devel] CORRECTION: mtl:psm configury broken (but NOT on master)

Oops, my mistake - this was *not* a test of 'master' This problem appears in Jeff's latest unofficial tarball built from his branch "feature/libltdl-must-die". I don't know if Jeff introduced the problem in his branch, or is missing the fix. Either way, its in your lap, Jeff. -Paul On Thu,

[OMPI devel] Master warning on oob:ud w/ PGI

The warning below comes from pgi-14.7 on the latest master tarball (output from "make V=1"). -Paul libtool: compile: pgcc -DHAVE_CONFIG_H -I. -I/scratch/scratchdirs/hargrove/OMPI/openmpi-master-linux-x86_64-pgi-14.7/openmpi-dev-1118-gdc80863/orte/mca/oob/ud -I../../../../opal/include

Re: [OMPI devel] mtl:psm configury build broken in master

Nite that there's a psm finalize check right before that that is not cached. Sent from my phone. No type good. On Feb 26, 2015, at 7:12 PM, Paul Hargrove > wrote: I have been testing mtl:psm on a very old system. Sometime pretty recently (this week

[OMPI devel] nearly-irrepoducable failure of master on Mac OS X 10.8

Initially I was testing Jeff's tarball for PR 410, on Mac OS X 10.8 where cc is clang, I have configured with --prefix=[...] --enable-debug --enable-osx-builtin-atomics CC=cc CXX=c++ I passed "make check", but when I try to run ring_c I get the first failure shown (far) below. HOWEVER, I

Re: [OMPI devel] nearly-irrepoducable failure of master on Mac OS X 10.8

Hmmm…someone else recently reported this same issue (it was the Absoft folks hitting it occasionally on their MTT runs). I’m in the process of replacing that code path, so I don’t plan on pursuing it right now. However, we’ll have to see if the revised path resolves it. > On Feb 26, 2015, at