1
1

'''TEMPORARY''' fix for #1211 to allow normal builds on the trunk:

ensure that including valgrind.h is within the WANT_MEMCHECKER macro.  

But this does not seem right; memchecker is a framework and valgrind
is the component -- why are we including a component-specific header
file in a top-level OMPI .h file?  It seems like there should be a
memchecker .h file that generically hides these component-specific
details (i.e., what if we add some other memchecker components
someday?).

This commit was SVN r17432.
Этот коммит содержится в:
Jeff Squyres 2008-02-12 15:06:02 +00:00
родитель 8cc9a8e992
Коммит 7746549f30

Просмотреть файл

@ -14,14 +14,17 @@
#define OMPI_MEMCHECKER_H
#include "ompi_config.h"
#include "ompi/communicator/communicator.h"
#include "ompi/group/group.h"
#include "ompi/datatype/datatype.h"
#include "ompi/request/request.h"
#include "opal/mca/memchecker/base/base.h"
#include "valgrind/valgrind.h"
#if OMPI_WANT_MEMCHECKER
/* JMS why is this here? Seems like an abstraction violation... */
#include "valgrind/valgrind.h"
# define MEMCHECKER(x) do { \
if(RUNNING_ON_VALGRIND){ \
x; \