Hi Jeff,
I've committed the fixes (r30905). It is a problem to detect kernel
defines (such as AF_IB ), so we have to use AC_RUN_IFELSE macro.
Thanks,
Vasily.
On 27-Feb-14 17:09, Jeff Squyres (jsquyres) wrote:
I'm seeing this warning this morning:
-
configure.ac:1139: warning: AC_RUN_
some additional explanation - it could be a situation when AF_IB is
defined in user space but kernel doesn't support it.
On 03-Mar-14 08:53, Vasily Filipov wrote:
Hi Jeff,
I've committed the fixes (r30905). It is a problem to detect
kernel defines (such as AF_IB ), so we have to use AC_RU
I have a simple patch which fixes the remaining compiler warnings when
running with '--with-ft':
https://lisas.de/git/?p=open-mpi.git;a=commitdiff;h=4dee703a0a2e64972b0c35b7693c11a09f1fbe5f
Does anybody see any problems with this patch?
Adrian
It looks like you removed a number of sstore stage MCA parameters. Did they
move somewhere else? or do you have a different way to set those parameters?
Other than that it looks good to me.
On Mon, Mar 3, 2014 at 5:29 AM, Adrian Reber wrote:
> I have a simple patch which fixes the remaining co
I removed a complete function because it was not used:
../../../../../orte/mca/sstore/stage/sstore_stage_component.c: At top level:
../../../../../orte/mca/sstore/stage/sstore_stage_component.c:77:12: warning:
'sstore_stage_select' defined but not used [-Wunused-function]
static int sstore_stage
Please note Open MPI standards state that for .m4 files, you need to always
define preprocessor macros that are used for logical tests -- it is not
sufficient to #define them or not. Instead, always define them to 0 or 1
(which would have made much of the original patch be valid).
Please updat
This commit breaks building without MPI Fortran support. Note that I did *NOT*
specify --enable-oshmem-fortran:
-
*** OSHMEM Configuration options
checking if want SGI/Quadrix compatibility mode... yes
checking if want OSHMEM API parameter checking... always
checking if want pshmem_... yes
c
More specifically, this goes back to the original question I asked long ago: if
it is time to unify the fortran language CLI options (i.e., --disable-fortran
instead of/in addition to --disable-mpi-fortran / --disable-oshmem-fortran).
I say this because by the logic from #1 below, if you have to
Can't you test for that at run-time?
I.e., can't you do the configure-time test to see if AF_IB exists, and if it
does, do a run-time check to see if it's useful/supported in the kernel? Or is
there a reason not to do this (e.g., it would impose a performance penalty at
run time because the ch
On Mar 2, 2014, at 8:29 PM, Orion Poplawski wrote:
> We're not honoring DESTDIR here:
>
> make install-data-hook
> make[6]: Entering directory
> `/builddir/build/BUILD/openmpi-1.7.5rc1/ompi/mpi/java/java'
> /usr/bin/mkdir -p /usr/lib64/openmpi/share/doc/openmpi/javadoc
> /usr/bin/mkdir: cannot
It should probably be moved to the component initialization of the sstore
stage component since those parameters are how the user controls where to
store those files. I think there is an MCA registration function that is
called after component initialization - that would be the best spot, but I
do
I will prepare a patch that moves the parameter initialization somewhere else
and will not remove it. Do you think the other parts of the patch can be
applied (without sstore_stage_select() removal)?
On Mon, Mar 03, 2014 at 10:07:36AM -0600, Josh Hursey wrote:
> It should probably be moved to the
Ok, I see whats happening. That component is calling a gcc specific memory
barrier. I will replace it with the appropriate opal_atomic call.
-Nathan
On Sunday, March 02, 2014 5:12 PM, devel [devel-boun...@open-mpi.org] on behalf
of Paul Hargrove [phhargr...@lbl.gov] wrote:
> To: Open MPI Develo
Heads up...
(In [30909]) Now that we are binding by default, the issue of #slots and what
to do when oversubscribed has become a bit more complicated. This isn't a
problem in managed environments as we are always provided an accurate
assignment for the #slots, or when -host is used to define t
On Fri, Feb 21, 2014 at 10:12:54AM -0700, Nathan Hjelm wrote:
> On Fri, Feb 21, 2014 at 05:21:10PM +0100, Adrian Reber wrote:
> > There is a variable in the FT code which is not defined and therefore
> > currently #ifdef'd out.
> >
> > #if (OPAL_ENABLE_FT == 1) && (OPAL_ENABLE_FT_CR == 1)
> > #ifd
Fixed on the trunk and CMR'ed to 1.7.5.
-Nathan
On Sunday, March 02, 2014 5:17 PM, devel [devel-boun...@open-mpi.org] on behalf
of Paul Hargrove [phhargr...@lbl.gov] wrote:
> To: Open MPI Developers
> Subject: [OMPI devel] 1.7.5rc1 failure: unresolved pthread calls
>
> The failure below (from O
Looks good to me.
-Nathan
On Monday, March 03, 2014 10:04 AM, devel [devel-boun...@open-mpi.org] on
behalf of Adrian Reber [adr...@lisas.de] wrote:
> To: Open MPI Developers
> Subject: Re: [OMPI devel] mca_base_component_distill_checkpoint_ready
> variable
>
> On Fri, Feb 21, 2014 at 10:12:5
Yea. Those look fine. Thanks!
On Mon, Mar 3, 2014 at 10:42 AM, Adrian Reber wrote:
> I will prepare a patch that moves the parameter initialization somewhere
> else
> and will not remove it. Do you think the other parts of the patch can be
> applied (without sstore_stage_select() removal)?
>
>
WHAT: Add two new verbose outputs to BML layer
WHY: There are times that I really want to know which BTLs are being used.
These verbose outputs can help with that.
WHERE: ompi/mca/bml/r2/bml_r2.c
TIMEOUT: COB Friday, 7 March 2014
MORE DETAIL: I have run into some cases where I have added to a
19 matches
Mail list logo
