Howdy,
here's a creative way to deadlock a program: create and destroy 65500 and
some communicators and send a message on each of them:
#include
#define CHECK(a)\
{ \
int e
On Sep 5, 2009, at 3:00 AM, Jeff Squyres wrote:
On Sep 4, 2009, at 5:47 PM, Sylvain Jeaugey wrote:
Understood. So, let's say that we're only implementing a hurdle to
discourage users from doing things wrong. I guess the efficiency of
this
will reside in the message displayed to the user ("Y
On Sep 4, 2009, at 5:47 PM, Sylvain Jeaugey wrote:
Understood. So, let's say that we're only implementing a hurdle to
discourage users from doing things wrong. I guess the efficiency of
this
will reside in the message displayed to the user ("You are about to
break
the entire machine and you
On Sep 4, 2009, at 2:56 PM, Nadia Derbey wrote:
Actually, I didn't have the problem on my side, because hg is not
known
in my build environment. Never noticed these lines:
-
*** Checking versions
checking for SVN version... ../configure: line 4285: hg: command not
found
done
On Sep 4, 2009, at 2:34 PM, Sylvain Jeaugey wrote:
hg -R "$srcdir" tip | head -1 | grep "^changeset:" | cut -d: -f3
Good catch; I changed it slightly from this to:
hg -v -R "$srcdir" tip | grep ^changeset: | head -n 1 | cut -d: -f3
I put this on the trunk since I couldn't push to your bb t
