Adrian,
Has there been any progress on this bug? If you still cannot reproduce
it, if you send either Tim Prins or I a debugging patch we can run
with it. Or we can try to arrange access to one of our machines for you.
This bug is making it difficult for us to continue working off of the
On Mon, Apr 21, 2008 at 09:04:28AM -0400, Josh Hursey wrote:
> Adrian,
Hi!
> Has there been any progress on this bug? If you still cannot reproduce
> it, if you send either Tim Prins or I a debugging patch we can run
> with it. Or we can try to arrange access to one of our machines for you.
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 c
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_
I am now simply trying some of our vaunted configure system's options to see
what actually works, and what doesn't.
Here is one that does NOT work:
enable_mca_no_build=pml-v
Generates the following build error:
configure: error: conditional "OMPI_BUILD_vprotocol_pessimist_DSO" was never
defined
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 memc
This sounds like a bug in ompi/mca/pml/v/configure.m4 that should be
fixed. I'll file a ticket.
FYI: AM_CONDITIONAL's cannot go in MCA_pml_c_CONFIG. See ompi/mca/btl/
openib/configure.m4 for an example of how to do an AM_CONDITIONAL
properly.
On Apr 21, 2008, at 9:56 AM, Ralph H Castain
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 memchecker:valgrind (m4
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
platform/co
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 command
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 memchecker=yes automatically requi
Thanks, I have been looking for a way to fix this for weeks now. I'll
try the POST_CONFIGURE think asap.
Aurelien
Le 21 avr. 08 à 10:12, Jeff Squyres a écrit :
This sounds like a bug in ompi/mca/pml/v/configure.m4 that should be
fixed. I'll file a ticket.
FYI: AM_CONDITIONAL's cannot go in
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 tick
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 tha
14 matches
Mail list logo
