Our macros for the OMPI-level free list had one extra argument, a possible
return value to signal that the operation of retrieving the element from the
free list failed. However in this case the returned pointer was set to NULL as
well, so the error code was redundant. Moreover, this was a conti
On 7/2/13 8:22 AM, "George Bosilca" wrote:
> Our macros for the OMPI-level free list had one extra argument, a possible
> return value to signal that the operation of retrieving the element from the
> free list failed. However in this case the returned pointer was set to NULL as
> well, so the er
Here's the beginning of the error:
CC lt_interface.lo
In file included from ../../../opal/util/lt_interface.c:21:
../../../opal/libltdl/ltdl.h:36:31: libltdl/lt_system.h: No such file or
directory
../../../opal/libltdl/ltdl.h:37:30: libltdl/lt_error.h: No such file or
directory
../../../
Here's the autotools we're using for v1.7:
-
module-whatis "Load Autotools (ac 2.69, am 1.12.2, lt 2.4.2, and m4 1.4.16)"
eval set [ array get env HOME ]
set AUTOTOOLS "/u/mpiteam/local/autotools-2.69-1.12.2-2.4.2-1.4.16"
setenv AUTOTOOLS $AUTOTOOLS
-
On Jul 2, 2013, at 11:14 AM, "Je
+1.
I submitted a patch like this a while ago, and it met violent resistance. :-)
Although no one on the call today remembers exactly who raised the
resistance...
On Jul 2, 2013, at 10:40 AM, "Barrett, Brian W" wrote:
> On 7/2/13 8:22 AM, "George Bosilca" wrote:
>
>> Our macros for the
All -
I would like to remove the Darwin backtrace component. Since 10.5.0, OS X
has supported the execinfo() interface supported by Linux, which is both
easier to use and less fragile. So the impact will be a loss of stack
traces on failure on OS X versions prior to 10.5.0, which should be a
sma
+1
On Jul 2, 2013, at 11:21 AM, "Barrett, Brian W" wrote:
> All -
>
> I would like to remove the Darwin backtrace component. Since 10.5.0, OS X
> has supported the execinfo() interface supported by Linux, which is both
> easier to use and less fragile. So the impact will be a loss of stack
>
I definitively wonder why ? Whoever was the "resistance" might have had a good
(r at least valid) orison. I can't find any trace of your patch, but I would
definitively be interested to take a look at it (if you can resend it) to avoid
triggering the same type of opposition.
George.
On Jul
Jeff thought it was me and I thought it was you, so I think we're ok :).
Brian
On 7/2/13 9:45 AM, "George Bosilca" wrote:
>I definitively wonder why ? Whoever was the "resistance" might have had a
>good (r at least valid) orison. I can't find any trace of your patch, but
>I would definitively b
What: As per the discussion at the developer's meeting in June add an interface
for performance variables to the MCA base. The interface is implemented at the
MCA level to allow performance variables to be exposed from any level (opal,
orte, and ompi). For more information on performance variabl
10 matches
Mail list logo