Re: [OMPI users] MPI Datatypes and RMA

Bruce, this issue was previously fixed on master and v2.x, but for some reasons, the fix was not backported to v1.10 i made a PR at https://github.com/open-mpi/ompi-release/pull/1120/files in the mean time, feel free to manually apply the patch at

[OMPI users] OpenSHMEM + STM Linking Problem

In my computer I have installed both OpenMPI and TinySTM. I have written a code which has both shmem and Software Transactional Memory(STM) calls. When I am compiling the code using oshcc it is showing "stm.h not found". Could anyone please help me on this matter? Regards RYAN SAPTARSHI RAY

Re: [OMPI users] OpenSHMEM + STM Linking Problem

stm.h is not a header file in either Open MPI or OpenSHMEM. Is that a TinySTM header file? If you're having a problem with compiling TinySTM applications, you should probably contact their support channels -- we don't know/can't help with that. Sorry. > On May 2, 2016, at 5:57 AM, RYAN

Re: [OMPI users] OpenSHMEM + STM Linking Problem

Dear Jeff Yes stm.h is a TinySTM header file. My query is that is it possible to use both shmem and TinySTM calls in the same code? Regards Ryan On Mon, 02 May 2016 16:05:05 +0530 "Jeff Squyres (jsquyres)" wrote >stm.h is not a header file in either Open MPI or OpenSHMEM. Is that a TinySTM

Re: [OMPI users] OpenSHMEM + STM Linking Problem

Ryan, I do not know if that can work, but you should at least be able to compile your application. if you use MPI wrappers (e.g. mpicc and friends), then you likely have to explicitly set the stm path and library for example mpicc -I$STM_HOME/include myapp.c -L$STM_HOME/lib -lstm Cheers,

Re: [OMPI users] users Digest, Vol 3489, Issue 1

Gilles, I downloaded and built openmpi-2.0.0rc2 and used that for the test. I get a crash on more than 1 processor for the lock/unlock protocol with the error message [node005:29916] *** An error occurred in MPI_Win_lock [node005:29916] *** reported by process [3736862721,6] [node005:29916]

Re: [OMPI users] users Digest, Vol 3489, Issue 1

Its not really a good idea to mix active and passive synchronization (we may actually explicitly forbid it in the future). You can remove the calls to MPI_Win_fence () and still have correct synchronization. That said, you did find a bug in my bad synchronization detection because this is legal:

[OMPI users] Problem with 'orted: command not found'

Hi, I'm having problem with Open MPI version 1.10.2. I've installed two virtual machines on VirtualBox, both are the same images of Ubuntu 12.04 64bit. Both have the same accounts, both have everything configured almost exactly the same. I have configured OMPI only with the --prefix to specify my

Re: [OMPI users] Problem with 'orted: command not found'

The key is this error: bash: orted: command not found Meaning: you need to set your PATH and LD_LIBRARY_PATH properly for non-interactive logins. See https://www.open-mpi.org/faq/?category=running#adding-ompi-to-path. > On May 2, 2016, at 5:36 PM, Maciek Lewiński

Re: [OMPI users] Problem with 'orted: command not found'

I already had correct paths in .bashrc: export PATH=/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/bin:/usr/local/bin:/home/$USER/.openmpi/bin export LD_LIBRARY_PATH=:/usr/local/lib:/usr/local/lib:/home/$USER/.openmpi/lib I can run

Re: [OMPI users] Problem with 'orted: command not found'

Make sure you check that these paths are set for *non-interactive* logins. > On May 2, 2016, at 6:14 PM, Maciek Lewiński wrote: > > I already had correct paths in .bashrc: > > export >

Re: [OMPI users] Problem with 'orted: command not found'

If OpenMPI is installed at the same path on every node, the easiest optin is to re-configure with --enable-mpirun-prefix-by-default an other option is to use `which mpirun` instead of mpirun and yet an other option is to mpirun --prefix=$USER/.openmpi Cheers, Gilles On Tuesday, May 3, 2016,