On Wed, Oct 29, 2008 at 1:49 PM, Jeff Squyres wrote:
> Ugh. IMHO, Cygwin != POSIX.
>
> The problem is that we're making the assumption that if dlsym() is present,
> RTLD_NEXT is defined. I guess that's not true for cygwin (lame). I suppose
> that we could also check for RTLD_NEXT...? Is there a
Ugh. IMHO, Cygwin != POSIX.
The problem is that we're making the assumption that if dlsym() is
present, RTLD_NEXT is defined. I guess that's not true for cygwin
(lame). I suppose that we could also check for RTLD_NEXT...? Is
there any other OS where dlsym() is present by RTLD_NEXT is no
On Wed, Oct 29, 2008 at 10:48 AM, George Bosilca wrote:
> Gustavo,
>
> I think we have a problem in the "make dist" for the 1.2. I just downloaded
> the latest 1.2.8, and the windows timer component header file is not in the
> tarball. This file is not automatically generated, and it is in the svn
Thank you very much Mi and Lenny for your detailed replies.
I believe I can summarize the infos to allow for
'Working with a QS22 CellBlade cluster' like this:
- Yes, messages are efficiently handled with "-mca btl openib,sm,self"
- Better to go to the OMPI-1.3 version ASAP
- It is currently mor
George --
Do you want to make a CMR for that fix for v1.2 anyway? It's still up
in the air as to whether there will be a 1.2.9 or not (let's hope not,
but...). If nothing else, we can have an unreleased 1.2.9 beta (or
somesuch) with a handful of fixes like this to close out the 1.2 series
Gustavo,
I think we have a problem in the "make dist" for the 1.2. I just
downloaded the latest 1.2.8, and the windows timer component header
file is not in the tarball. This file is not automatically generated,
and it is in the svn version.
Anyway, the 1.3 is nearly ready to replace the
On Mon, Oct 27, 2008 at 4:52 PM, Jeff Squyres wrote:
> Sorry for the lack of reply; several of us were at the MPI Forum meeting
> last week, and although I can't speak for everyone else, I know that I
> always fall [way] behind on e-mail when I travel. :-\
>
> The windows port is very much a work-
"dmesg |grep Node" on Cell will show :
Node 0: CPUS 0-1
Node 1: CPUS 2-3
.
Linux on Cell/BE puts the CPU-node mapping in /sys/devices/system/node
instead of /sys/devices/system/cpu.
Regards,
Mi
"Lenny
