Hmm. I do not have this problem on OS X (where I do not have Valgrind
installed) as of this morning's trunk. configure correctly determines
that valgrind is not present and therefore continues on:
--- MCA component memchecker:valgrind (m4 configuration macro)
checking for MCA component memchecker:valgrind compile mode... static
checking if MCA component memchecker:valgrind can compile... no
...etc.
Note that your message indicates that configure thinks that valgrind
support was explicitly requested. In this case, configure thinks,
"you explicitly requested it, I cannot provide it, so I should abort
rather than give unexpected results."
Can you send your full configure output and config.log?
On Apr 21, 2008, at 9:51 AM, Ralph H Castain wrote:
As an FYI for anyone similarly afflicted:
The only solution I have found is to gut the file
opal/mca/memchecker/valgrind/configure.m4:
# MCA_memchecker_valgrind_CONFIG([action-if-found], [action-if-not-
found])
# -----------------------------------------------------------
AC_DEFUN([MCA_memchecker_valgrind_CONFIG],[
happy=0 # none_needed
happy_value=0 # none_needed
memchecker_valgrind_happy=0 # This should suffice to get rid
of the
component
should_build=2
want_component=0
])dnl
Nothing else will allow you to build unless you have the valgrind
headers
installed on your machine.
Ralph
On 4/21/08 7:28 AM, "Ralph H Castain" <r...@lanl.gov> wrote:
I am finding that the memchecker code is again breaking the trunk,
specifically on any machine that does not have valgrind installed.
Apparently, memchecker now forces a requirement for valgrind?
Here is what I get:
--- MCA component memchecker:valgrind (m4 configuration macro)
checking for MCA component memchecker:valgrind compile mode... static
checking checking for the valgrind include directory ... none needed
checking valgrind/valgrind.h usability... no
checking valgrind/valgrind.h presence... no
checking for valgrind/valgrind.h... no
configure: WARNING: *** Could not find valgrind header files, as
valgrind
support was requested
configure: error: *** Cannot continue
Could somebody please fix this? I thought we had decided many moons
ago that
we would not require specific debuggers in default build
configurations - I
am somewhat surprised, therefore, to find that memchecker is "on" by
default, and now requires valgrind!
I have tried --disable-memchecker, but nothing will allow me to get
past
this error.
Thanks
Ralph
_______________________________________________
devel mailing list
de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel
_______________________________________________
devel mailing list
de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel
--
Jeff Squyres
Cisco Systems
