Re: [OMPI devel] Memchecker: breaks trunk again

See https://svn.open-mpi.org/trac/ompi/ticket/1276. On Apr 21, 2008, at 6:44 PM, Rainer Keller wrote: Hi Jeff and Ralph, On Monday 21 April 2008 16:48, Jeff Squyres wrote: Ah, I see what's happening. The opal/mca/memchecker/valgrind/configure.m4 file is using "want memchecker" to indicate

Re: [OMPI devel] Memchecker: breaks trunk again

Hi Jeff and Ralph, On Monday 21 April 2008 16:48, Jeff Squyres wrote: > Ah, I see what's happening. > > The opal/mca/memchecker/valgrind/configure.m4 file is using "want > memchecker" to indicate that you want valgrind support. I think that > these should be two different issues. I'll file a

Re: [OMPI devel] Memchecker: breaks trunk again

Thanks Brian - I had been told precisely the opposite priority rule just a few weeks ago by someone else, hence my confusion. On 4/21/08 8:48 AM, "Brian W. Barrett" wrote: > On Mon, 21 Apr 2008, Ralph H Castain wrote: > >> So it appears to be a combination of

Re: [OMPI devel] Memchecker: breaks trunk again

Ah, I see what's happening. The opal/mca/memchecker/valgrind/configure.m4 file is using "want memchecker" to indicate that you want valgrind support. I think that these should be two different issues. I'll file a ticket. Additionally, for the platform file overriding the configure

Re: [OMPI devel] Memchecker: breaks trunk again

On Mon, 21 Apr 2008, Ralph H Castain wrote: So it appears to be a combination of memchecker=yes automatically requiring valgrind, and the override on the configure line of a param set by a platform file not working. So I can't speak to the valgrind/memchecker issue, but can to the

Re: [OMPI devel] Memchecker: breaks trunk again

On 4/21/08 8:10 AM, "Jeff Squyres" wrote: > 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

Re: [OMPI devel] Memchecker: breaks trunk again

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]) # ---

[OMPI devel] Memchecker: breaks trunk again

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