[OMPI users] minor glitch in 1.5-rc5 Windows build - has workaround

Hi all, There's a small hiccup in building a Windows version of 1.5-rc5. When you configure in the CMake GUI, you can ask for a Debug or Release project before you hit Generate. If you ask for a Debug project, you can still change it to Release in Visual Studio, and it will build successfu

Re: [OMPI users] deadlock in openmpi 1.5rc5

Hi, sorry for the confusion, that was indeed the trunk version of things I was running. Here's the same problem using http://www.open-mpi.org/software/ompi/v1.5/downloads/openmpi-1.5rc5.tar.bz2 command-line: ../openmpi_devel/bin/mpirun -hostfile hostfiles/hostfile.wgsgX -npernode 11 ./bin/mpi_

[OMPI users] Bug in POWERPC32.asm?

I was looking in my copy of openmpi-1.4.1 opal/asm/base/POWERPC32.asm and saw the following: START_FUNC(opal_sys_timer_get_cycles) LSYM(15) mftbu r0 mftb r11 mftbu r2 cmpw cr7,r2,r0 bne+ cr7,REFLSYM(14) li r4,0 li r9,0 or r3,r

Re: [OMPI users] deadlock in openmpi 1.5rc5

You clearly have an issue with version confusion. The file cited in your warning: > [wgsg0:29074] Warning -- mutex was double locked from errmgr_hnp.c:772 does not exist in 1.5rc5. It only exists in the developer's trunk at this time. Check to ensure you have the right paths set, blow away the

[OMPI users] Memory allocation error when linking with MPI libraries

Hello, I'am having an sigsegv error when using simple program compiled and link with openmpi. I have reproduce the problem using really simple fortran code. It actually does not even use MPI, but just link with mpi shared libraries. (problem does not appear when I do not link with mpi libraries)