You're right. Sorry about the typo. It was just corrected.
On Aug 30, 2011, at 2:27 PM, Shamis, Pavel wrote:
> Hi all,
> I'm not sure, if it is relevant to this specific commit, but it is relevant
> for some of epoch changes.
> I was not able to compile latest trunk version on our cray system, t
You're right. Sorry about the typo. It was just corrected.
On Aug 30, 2011, at 2:27 PM, Shamis, Pavel wrote:
> Hi all,
> I'm not sure, if it is relevant to this specific commit, but it is relevant
> for some of epoch changes.
> I was not able to compile latest trunk version on our cray system, t
Hi all,
I'm not sure, if it is relevant to this specific commit, but it is relevant for
some of epoch changes.
I was not able to compile latest trunk version on our cray system, the failure
was in ess/alps component, for me it seems like simple typo. I did not have
chance to check my fix on our
Thanks! Much appreciate the help
On Aug 26, 2011, at 6:32 PM, George Bosilca wrote:
> I see. This should be fixed in r25098. Thanks for your patience.
>
> george.
>
> On Aug 26, 2011, at 19:47 , Ralph Castain wrote:
>
>> Has nothing to do with version, George - it's a problem of ORTE_ENABLE_
I see. This should be fixed in r25098. Thanks for your patience.
george.
On Aug 26, 2011, at 19:47 , Ralph Castain wrote:
> Has nothing to do with version, George - it's a problem of ORTE_ENABLE_EPOCH
> not being included in an AC_DEFINE. It is solely defined via AM_CONDITIONAL,
> but then u
Strange -- I don't see where ORTE_ENABLE_EPOCH is defined at all, other than
some warnings about it not being defined in autom4te.cache (which is weird in
itself -- it means that things in configure were complaining that it wasn't
defined; but the wording might imply that it was looking for an A
Has nothing to do with version, George - it's a problem of ORTE_ENABLE_EPOCH
not being included in an AC_DEFINE. It is solely defined via AM_CONDITIONAL,
but then used in .h files - which is simply wrong.
Please fix it.
On Aug 26, 2011, at 5:41 PM, George Bosilca wrote:
> We can't reproduce t
We can't reproduce this. It compiles and runs without troubles on our macs.
However, it might depend on the Mac OS X version, we recently moved to Lion.
Thanks,
george.
On Aug 26, 2011, at 19:19 , Ralph Castain wrote:
> Hate to say this, but the trunk is broken - won't build on Mac with t
Wesley --
I'm getting a bazillion "warning: "ORTE_ENABLE_EPOCH" is not defined" warnings.
By "bazillion", I mean:
% grep ORTE_ENABLE_EPOCH make.out | grep warning | wc -l
8695
%
Here's my configure statement on both OS X and Linux:
./configure --prefix=/tmp/bogus --disable-mpi-f77 --disab
Hate to say this, but the trunk is broken - won't build on Mac with that
disabled. I'll try to dig into it later :-(
On Aug 26, 2011, at 4:18 PM, Wesley Bland wrote:
> The epoch and resilient rote code is now macro'd away. To enable use
>
> --enable-resilient-orte
>
> which defines:
>
> ORTE
The epoch and resilient rote code is now macro'd away. To enable use
--enable-resilient-orte
which defines:
ORTE_ENABLE_EPOCH
ORTE_RESIL_ORTE
--
Wesley
On Aug 26, 2011, at 6:16 PM, wbl...@osl.iu.edu wrote:
> Author: wbland
> Date: 2011-08-26 18:16:14 EDT (Fri, 26 Aug 2011)
> New Revision: 25
11 matches
Mail list logo
