The 1.12 series had a set of problems caused by a changeover in the
maintainers, so it should never be used. I’m not sure if any of those issues
are behind this problem, but it could be so.
Anyway, I think pretty much all of us are using automake 1.14 by this time. We
can discuss how far up to
Dave,
this is an automake issue indeed.
i use automake 1.12.2 (as advised at
http://www.open-mpi.org/source/building.php, and
this is the version used to build the snapshots)
automake 1.12.2 adds the following line in ompi/include/Makefile.in :
$(srcdir)/mpi.h.in: $(am__configure_deps)
Per the telecon today, I updated libevent to the 2.0.22-stable release as there
is a bug fix of a race condition when using event_active, which we use in a lot
of places.
Remember to "rm -rf opal/mca/event/libevent2021” after you pull the update as
the stale directory will remain.
Ralph
On Tue, Jan 6, 2015 at 4:25 PM, Jeff Squyres (jsquyres)
wrote:
> My enthusiasm for this was primarily because I thought we had talked about
> exactly this issue before (at the last meeting in Chicago?), and decided
> that the option is useless -- in part, because it always *must* be enabled
> for
My enthusiasm for this was primarily because I thought we had talked about
exactly this issue before (at the last meeting in Chicago?), and decided that
the option is useless -- in part, because it always *must* be enabled for
shared memory correctness.
Is that incorrect?
On Jan 6, 2015, at 4
Successive alteration of the build system made this option less relevant
and especially less meaningful. However, while removing it sounds like a
desirable cleanup, we have to keep in mind that this will enable all locks
and all memory barriers even in cases where they are not necessary
(via OPAL_W
+1
> On Jan 6, 2015, at 9:04 AM, Jeff Squyres (jsquyres)
> wrote:
>
> +1
>
> On Jan 6, 2015, at 11:55 AM, Howard Pritchard wrote:
>
>> I agree. Please remove this config option.
>>
>> 2015-01-06 9:44 GMT-07:00 Nathan Hjelm :
>>
>> What: Remove the --disable-smp-locks configure option from
+1
On Jan 6, 2015, at 11:55 AM, Howard Pritchard wrote:
> I agree. Please remove this config option.
>
> 2015-01-06 9:44 GMT-07:00 Nathan Hjelm :
>
> What: Remove the --disable-smp-locks configure option from master.
>
> Why: Use of this option produces incorrect results/undefined behavior
>
On Jan 5, 2015, at 8:40 PM, Gilles Gouaillardet
wrote:
> Dave,
>
> what if you do
>
> touch ompi/include/mpi.h.in && sleep 1 && touch
> config/opal_config_pthreads.m4 && ./autogen.pl && module unload
> cisco/autotools/ac269-am1133-lt242 && ./configure --prefix=$PWD/_prefix &&
> make
>
>
>
I agree. Please remove this config option.
2015-01-06 9:44 GMT-07:00 Nathan Hjelm :
>
> What: Remove the --disable-smp-locks configure option from master.
>
> Why: Use of this option produces incorrect results/undefined behavior
> when any shared memory BTL is in use. Since BTL usage is enabled
What: Remove the --disable-smp-locks configure option from master.
Why: Use of this option produces incorrect results/undefined behavior
when any shared memory BTL is in use. Since BTL usage is enabled even
when using cm for point-to-point this option can never be safely used.
When: Thurs, Jan 6
11 matches
Mail list logo
