Re: [OMPI users] symbol lookup error for a "hello world" fortran script

Julien, the fortran lib is in /usr/lib/libmpi_mpifh.so.12 the C lib is the one from Intel MPI i guess the C lib is in /usr/lib, and not /usr/lib/openmpi/lib prepending /usr/lib is never recommended, so i suggest you simply remove /opt/intel/compilers_and_libraries_2016.1.150/linux/mpi/intel64/lib

Re: [OMPI users] symbol lookup error for a "hello world" fortran script

Gilles, Thank you for your fast reply. When I type whereis mpifort I have the following: *mpifort: /usr/bin/mpifort.openmpi /usr/bin/mpifort /usr/share/man/man1/mpifort.1.gz* I made sure I exported the LD_LIBRARY_PATH after I prepended /usr/lib/openmpi/lib. The same error is produced. If I type

Re: [OMPI users] symbol lookup error for a "hello world" fortran script

Julien, first, make sure you are using the Open MPI wrapper which mpifort should be /usr/lib/openmpi/bin if i understand correctly then make sure you exported your LD_LIBRARY_PATH *after* you prepended the path to Open MPI lib in your .bashrc you can either LD_LIBRARY_PATH=/usr/lib/openmpi/lib:$LD

[OMPI users] symbol lookup error for a "hello world" fortran script

Hi all, I am completely new to MPI (and relatively new to linux). I am sorry if the problem I encountered is obvious to solve. When I run the following simple test with mpirun: *program hello_world use mpi integer ierr call MPI_INIT ( ierr ) print *, "Hello world"

Re: [OMPI users] Java-OpenMPI returns with SIGSEGV

​​Hello Gundram, This seems to be an issue with psm. I have been communicating with Matias at Intel who has forwarded the problem to the correct team so they can investigate it. There is a new version of psm available at the link below. It will fix the issue you are currently seeing, howeve

Re: [OMPI users] MPI_ABORT was invoked on rank 0 in communicator compute with errorcode 59

Hi Mohammadali "Signal number 11 SEGV", is the Unix/Linux signal for a memory violation (a.k.a. segmentation violation or segmentation fault). This normally happens when the program tries to read or write in a memory area that it did not allocate, already freed, or belongs to another process. Tha

Re: [OMPI users] Open MPI State of the Union BOF at SC'16 next week

Make sense. Thanks for making the slides available. Would you mind posting to the list when the rest of us can get them? -Sean -- Sean Ahern Computational Engineering International 919-363-0883 On Tue, Nov 15, 2016 at 10:53 AM, Jeff Squyres (jsquyres) < jsquy...@cisco.com> wrote: > On Nov 10, 2

Re: [OMPI users] Open MPI State of the Union BOF at SC'16 next week

On Nov 10, 2016, at 9:31 AM, Jeff Squyres (jsquyres) wrote: > > The slides will definitely be available afterwards. We'll see if we can make > some flavor of recording available as well. After poking around a bit, it looks like the SC rules prohibit us from recording the BOF (which is not unr

Re: [OMPI users] Valgrind errors related to MPI_Win_allocate_shared

Joseph, thanks for the report, this is a real memory leak. i fixed it in master, and the fix is now being reviewed. meanwhile, you can manually apply the patch available at https://github.com/open-mpi/ompi/pull/2418.patch Cheers, Gilles On Tue, Nov 15, 2016 at 1:52 AM, Joseph Schuchart wrote:

Re: [OMPI users] An old code compatibility

Mahmood Naderan writes: > Hi, > The following mpifort command fails with a syntax error. It seems that the > code is compatible with old gfortran, but I am not aware of that. Any idea > about that? > > mpifort -ffree-form -ffree-line-length-0 -ff2c -fno-second-underscore > -I/opt/fftw-3.3.5/inclu

Re: [OMPI users] Valgrind errors related to MPI_Win_allocate_shared

Hi Luke, Thanks for your reply. From my understanding, the wrappers mainly help catch errors on the MPI API level. The errors I reported are well below the API layer (please correct me if I'm wrong here) However, I re-ran the code with the wrapper loaded via LD_PRELOAD and without the suppres