On Thu, 14 Jan 2010 21:55:06 -0500, Jeff Squyres wrote:
> That being said, you could sign up on it and then set your membership to
> receive no mail...?
This is especially dangerous because the Open MPI lists munge the
Reply-To header, which is a bad thing
On Jan 14, 2010, at 7:38 PM, Aleksej Saushev wrote:
> The first one, "#! /usr/bin/env bash " should be "#! /usr/bin/env bash"
> at the very least.
Ah, in autogen.sh -- I thought you were referring to configure.
Strange that NetBSD doesn't like it; I wonder why...
Regardless, the extra space
Jeff Squyres writes:
> On Jan 14, 2010, at 7:00 PM, Aleksej Saushev wrote:
>
>> > Thanks! I have this queued up to commit in a few hours (we try not to
>> > commit autogen/configure-worthy changes during the US workday).
>>
>> While we're at autogen stuff, could you drop
Jeff Squyres writes:
> Thanks! I have this queued up to commit in a few hours (we try not to
> commit autogen/configure-worthy changes during the US workday).
While we're at autogen stuff, could you drop trailing space on
interpreter line? NetBSD doesn't like it.
While I'm
Thanks! I have this queued up to commit in a few hours (we try not to commit
autogen/configure-worthy changes during the US workday).
On Jan 14, 2010, at 11:54 AM, Aleksej Saushev wrote:
>
> Hello!
>
> Flawed logic: Linux isn't the only system with procfs.
> NetBSD has procfs too and may
Hello!
Flawed logic: Linux isn't the only system with procfs.
NetBSD has procfs too and may have /proc/cpuinfo as well,
but it isn't Linux.
I didn't check if FreeBSD has "cpuinfo" as well,
FreeBSD 6.3 doesn't but it's being desupported soon.
Difference against openmpi-1.5a1r22193 snapshot.