I can't speak to what you get from sacct, but I can say that things will
definitely be different when launched directly via srun vs indirectly thru
mpirun. The reason is that mpirun uses srun to launch the orte daemons, which
then fork/exec all the application processes under them (as opposed to
Thanks! Fixed in trunk and CMRd for 1.7.3
On Aug 9, 2013, at 1:07 AM, Michael Schlottke
wrote:
> Hi there,
>
> I don't know if this is the right place to post this, but it seems like the
> header guard in /opal/memoryhooks/memory.h does not work as intended:
> The header guard is written as
Ralph -
I think those warnings are just because of when they last synced with the
trunk; it looks like they haven't updated in the last week, when those
(and some usnic fixes) went in.
More concerning is the --enable-picky stuff and the disabling of SHMEM in
the right places.
Brian
On 8/11/13 1
Turning off the enable_picky, I get it to compile with the following warnings:
pget_elements_x_f.c:70: warning: no previous prototype for
'ompi_get_elements_x_f'
pstatus_set_elements_x_f.c:70: warning: no previous prototype for
'ompi_status_set_elements_x_f'
ptype_get_extent_x_f.c:69: warning: n
