That's good that you guys revive this thread, I almost forget about it.
The code you're referring, is not part of the libevent. It was one
of my "fixes" around for problem on OS X (where kevent is not able to
work nicely with pty). It works on MAC as the code trigger an error so
there is n
Hi, Jeff...
This test was performed locally, yes. I'm short on machines at the moment to
perform any proper distributed tests.
--
Karol
-Original Message-
From: Jeff Squyres
List-Post: devel@lists.open-mpi.org
Date: Fri, 11 Apr 2008 16:36:33
To:Open MPI Developers
Subject: Re: [OMPI
This may depend on how you ran the app on FreeBSD -- did you run on
the localhost only?
We have/had a problem when running locally with regards to kevent --
I'm not 100% sure if we've fixed it yet. Let me check...
On Apr 5, 2008, at 1:53 AM, Karol Mroz wrote:
After digging a little deepe
It was: https://svn.open-mpi.org/trac/ompi/changeset/18077
Thanks.
On Apr 9, 2008, at 1:31 PM, Bernhard Fischer wrote:
On Wed, Apr 02, 2008 at 03:37:53PM -0400, Jeff Squyres wrote:
Thanks! We have a general rule to not apply autogen-worthy changes
during the US workday, so I'll commit this to
You might also want to look at:
http://www.open-mpi.org/faq/?category=vampirtrace
On Apr 11, 2008, at 1:53 AM, Andreas Knüpfer wrote:
On Thursday 10 April 2008, Swati Kher wrote:
2) If vampire trace by default is built with openmpi, if I set
VT_CC flag for compiling my application
On Thursday 10 April 2008, Swati Kher wrote:
>
> 2) If vampire trace by default is built with openmpi, if I set
> VT_CC flag for compiling my application, where I can view ".vtf" files
> after a parallel run ?
>
Let me answer the second question.
First of all, there is no default VT_CC flag
