Re: [OMPI users] mpirun

I don't recall Walt 's cases taking all of 5 seconds to start. More annoying is the hang after completion. Sent via the ASUS PadFone X mini, an AT 4G LTE smartphone Original Message From:Ralph Castain Sent:Fri, 29 May 2015 15:35:15 -0400 To:Open MPI Users

Re: [OMPI users] mpirun

Walt, can you disable firewall and network if possible and give it an other try ? Cheers, Gilles On Saturday, May 30, 2015, Walt Brainerd wrote: > It behaved this way with the Cygwin version (very recent update) > and with 1.8.5 that I built from source. > > On

Re: [OMPI users] mpirun

Another thing you might want to try: see how long it takes to run a simple MPI “hello” - see our “examples” directory. This will tell us if there is something about this app that is causing the delay, or something in the launch support > On May 29, 2015, at 1:13 PM, Ralph Castain

Re: [OMPI users] mpirun

Since you are able to build OMPI from scratch, can you build it with —enable-debug? If so, then you could set an MCA param or two for debug purposes that might help us narrow down where the delay is coming from. I’d start with "—mca state_base_verbose 5” and see if there is some noticeable hang

Re: [OMPI users] mpirun

I should explain a little more. Sorry. I built OpenMPI and Opencoarrays and Gfortran 5.1. It is with this combination that I am running a program using coarrays compiled by gfortran. The command "mpirun -np 4 a.exe" appears to take about 5 seconds to start up. This is true of another person

Re: [OMPI users] mpirun

It behaved this way with the Cygwin version (very recent update) and with 1.8.5 that I built from source. On Fri, May 29, 2015 at 12:35 PM, Ralph Castain wrote: > I assume you mean on cygwin? Or is this an older version that supported > native Windows? > > > On May 29, 2015,

Re: [OMPI users] mpirun

I assume you mean on cygwin? Or is this an older version that supported native Windows? > On May 29, 2015, at 12:34 PM, Walt Brainerd wrote: > > On Windows, mpirun appears to take about 5 seconds > to start. I can't try it on Linux. Intel takes no time to > start

[OMPI users] mpirun

On Windows, mpirun appears to take about 5 seconds to start. I can't try it on Linux. Intel takes no time to start executing its version. Is this expected? -- Walt Brainerd

Re: [OMPI users] Building OpenMPI on Raspberry Pi 2

George, I changed my configure command to be: ./configure CCASFLAGS=-march=native and I get an error while running configure: ... *** Assembler checking dependency style of gcc -std=gnu99... gcc3 checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister

Re: [OMPI users] Building OpenMPI on Raspberry Pi 2

As you are not cross-compiling I would expect gcc to use the right assembly by default. What is happening is you force the native mode (-march=native) ? George. On Fri, May 29, 2015 at 10:09 AM, Jeff Layton wrote: > On 05/29/2015 09:35 AM, Jeff Layton wrote: > > Gilles, >

Re: [OMPI users] How can I discover valid values for MCA parameters?

Follow-up to the 2nd question which I now realize is something else. I can see output when I do: ompi_info --param coll fca with a version of OpenMPI that was built with --prefix set to its installed location. I cannot get the output when I use a relocated version, i.e. built in one

Re: [OMPI users] How can I discover valid values for MCA parameters?

At the moment we only provide the list of possible values for emumerated integers. If an integer is enumerated you will see something like this in the ompi_info -a output: Valid values: 0:"static", 1:"sequential", 2:"unknown-root" I am hoping to expand this support to more variables in the

[OMPI users] How can I discover valid values for MCA parameters?

Sometimes I want to use one of the option flags, for example today it is mtl_mxm_verbose. How do I discover the valid possible values of various MCA parameters? I've tried ompi_info --all but it does not show the possible values, only the current value I've tried ompi_info --param all

Re: [OMPI users] Openmpi compilation errors

> On May 29, 2015, at 5:07 AM, Jeff Squyres (jsquyres) > wrote: > > On May 29, 2015, at 6:54 AM, Bruno Queiros wrote: > >> The name of the binary is correct: pgf90 the name of the file is also >> correct .pgf90.rc i do have some doubts about the

Re: [OMPI users] Building OpenMPI on Raspberry Pi 2

On 05/29/2015 09:35 AM, Jeff Layton wrote: Gilles, oops - yes, CFLAGS. But I also saw this posting: https://www.open-mpi.org/community/lists/users/2013/01/2.php where CCASFLAGS is used (I assume because for asm). I'm trying this flag when I configure Open MPI. I tried using the

Re: [OMPI users] Openmpi compilation errors

Luis Can you point me to that documentation you're reading? Em sex, 29 de mai de 2015 às 13:04, Luis Kornblueh < luis.kornbl...@mpimet.mpg.de> escreveu: > Hi, > > Bruno is using 10.4 as I ready only a second ago in one of his emails. I > have no idea if the compiler resource file trick works

Re: [OMPI users] Openmpi compilation errors

Thank you Jeff for the clarification and help. Em sex, 29 de mai de 2015 às 12:08, Jeff Squyres (jsquyres) < jsquy...@cisco.com> escreveu: > On May 29, 2015, at 6:54 AM, Bruno Queiros wrote: > > > > I understand that using Portland compiler isn't "advised" by Open Mpi, i >

Re: [OMPI users] Building OpenMPI on Raspberry Pi 2

Gilles, oops - yes, CFLAGS. But I also saw this posting: https://www.open-mpi.org/community/lists/users/2013/01/2.php where CCASFLAGS is used (I assume because for asm). I'm trying this flag when I configure Open MPI. Thanks! Jeff Jeff, shall I assume you made a typo and wrote

Re: [OMPI users] Building OpenMPI on Raspberry Pi 2

Jeff, shall I assume you made a typo and wrote CCFLAGS instead of CFLAGS ? also, can you double check the flags are correctly passed to the assembler with cd opal/asm make -n atomic-asm.lo Cheers, Gilles On Friday, May 29, 2015, Jeff Layton wrote: > Good morning, > > I'm

[OMPI users] Building OpenMPI on Raspberry Pi 2

Good morning, I'm building OpenMPI from source on a Raspberry Pi 2 and I've hit an error. The error is: make[2]: Entering directory '/work/pi/src/openmpi-1.8.5/opal/asm' CPPASatomic-asm.lo atomic-asm.S: Assembler messages: atomic-asm.S:7: Error: selected processor does not support ARM

Re: [OMPI users] Openmpi compilation errors

Hi, Bruno is using 10.4 as I ready only a second ago in one of his emails. I have no idea if the compiler resource file trick works with this old one. By the way it has to be .mypgf90rc not .pgf90rc at least following the current documentation. Cheerio, Luis On 29/05/15 13:07, Jeff

Re: [OMPI users] Openmpi compilation errors

On May 29, 2015, at 6:54 AM, Bruno Queiros wrote: > > I understand that using Portland compiler isn't "advised" by Open Mpi, i was > just wondering if there's a way of doing it, since i need Open Mpi compiled > with PG fortran and not gfortran for example. A further

Re: [OMPI users] Openmpi compilation errors

Hello Jeff I understand that using Portland compiler isn't "advised" by Open Mpi, i was just wondering if there's a way of doing it, since i need Open Mpi compiled with PG fortran and not gfortran for example. The name of the binary is correct: pgf90 the name of the file is also correct

Re: [OMPI users] Openmpi compilation errors

Thank you for the help Luis I did as you told me, i created a .pfg90.rc on the home directory of my user with: switch -pthread is replace(-lpthread) positional(linker) i tried to compile openmpi with make, but i still got the same error. Am i doing something wrong? How can i overcome this