This has now been solved.
The solution (as suggested by Ralph) is to use the following four
configure options together:
./configure --enable_event_thread_support --enable_opal_multi_threads
--enable_orte_progress_threads --enable_mpi_thread_multiple
So, apparently the --enable_mpi_thread_mu
Hello,
we have been hit observing a strange behavior with OpenMPI 1.6.3
strace -f /share/apps/openmpi/1.6.3/bin/mpiexec -n 2
--nooversubscribe --display-allocation --display-map --tag-output
/share/apps/gamess/2011R1/gamess.2011R1.x
/state/partition1/rmurri/29515/exam01.F05 -scr
/state/partit
While I'm glad it worked, having it depend on orte progress thread wasn't done
by intent, hence the comment in the configure help output. I'm not seeing any
problems with using that option, but please let us know if you run into
something. It hasn't been as fully tested as we'd like.
On Jun 19
I don't see a hostfile on your command line - so I assume you are using a
default hostfile? What is in it?
On Jun 19, 2013, at 1:49 AM, Sergio Maffioletti
wrote:
> Hello,
>
> we have been hit observing a strange behavior with OpenMPI 1.6.3
>
> strace -f /share/apps/openmpi/1.6.3/bin/mpie
unsubscribe
Hi,
(colleague of OP here)
On 19 June 2013 15:09, Ralph Castain wrote:
> I don't see a hostfile on your command line - so I assume you are using a
> default hostfile? What is in it?
The hostfile comes from the batch system; it just contains the
unqualified host names:
$ cat $TMPDIR/machine
How is OMPI picking up this hostfile? It isn't being specified on the cmd line
- are you running under some resource manager?
I haven't seen that confusion elsewhere, so I'm trying to understand which code
path is involved - hence the questions.
On Jun 19, 2013, at 6:26 AM, Riccardo Murri wrot
Inizio messaggio inoltrato:
> Da: Lorenzo Donà
> Data: 19 giugno 2013 18.14.26 GMT+02.00
> A: us...@open-mpi.org
> Oggetto: error with openmpi on snow leopard
>
> Hi I compiled openmpi v1.7.1 and previous but I always found this message:
> Cannot open configuration file
> /Users/lorenzodona/D
How did you configure it?
On Jun 19, 2013, at 9:26 AM, Lorenzo Donà wrote:
>
>
> Inizio messaggio inoltrato:
>
>> Da: Lorenzo Donà
>> Data: 19 giugno 2013 18.14.26 GMT+02.00
>> A: us...@open-mpi.org
>> Oggetto: error with openmpi on snow leopard
>>
>> Hi I compiled openmpi v1.7.1 and previo
On 19 June 2013 16:01, Ralph Castain wrote:
> How is OMPI picking up this hostfile? It isn't being specified on the cmd
> line - are you running under some resource manager?
Via the environment variable `OMPI_MCA_orte_default_hostfile`.
We're running under SGE, but disable the OMPI/SGE integrat
configure it with gnu 4.6 without configurations options
when I compile another program this i the message:
Unfortunately, this installation of Open MPI was not compiled with
Fortran 90 support. As such, the mpif90 compiler is non-functional.
can you help me to configure correctly openmpi?
Il gio
Hmmm..certainly sounds like a bug. It should pickup that the node is local. It
checks the hostname (as returned by gethostname), but it also checks to see if
host resolves to a local address. I'm assuming that the offending host has some
other address besides just 127.0.1.1 as otherwise it could
Am 19.06.2013 um 19:43 schrieb Riccardo Murri :
> On 19 June 2013 16:01, Ralph Castain wrote:
>> How is OMPI picking up this hostfile? It isn't being specified on the cmd
>> line - are you running under some resource manager?
>
> Via the environment variable `OMPI_MCA_orte_default_hostfile`.
>
Have a look at the README file; it contains a lot of information about building
Open MPI.
In short, for F90 support, you want to have a Fortran 90 compiler (E.g.,
gfortran) in your PATH when you run configure.
On Jun 19, 2013, at 2:41 PM, Lorenzo Donà wrote:
> configure it with gnu 4.6 with
I have it I used gfortran after configuration I typed ake ckech and I passed
all the tests
but when I try to use mpif90 or others mpi compilers I find always
Cannot open configuration file
/Users/lorenzodona/Desktop/openmpi-1.7.1/share/openmpi/opal_wrapper-wrapper-data.txt
Error parsing data file
what prefix did you give configure? is your path and ld_library_path set to
that location?
On Jun 19, 2013, at 11:59 AM, Lorenzo Donà wrote:
> I have it I used gfortran after configuration I typed ake ckech and I passed
> all the tests
> but when I try to use mpif90 or others mpi compilers I f
Please send all the information listed here:
http://www.open-mpi.org/community/help/
On Jun 19, 2013, at 2:59 PM, Lorenzo Donà wrote:
> I have it I used gfortran after configuration I typed ake ckech and I passed
> all the tests
> but when I try to use mpif90 or others mpi compilers I fin
I export PATH=/usr/local/gfortran/bin:$PATH
i configured it in this way:
./configure CC=gcc CXX=g++ F77=gfortran FC=gfortran
-prefix=/Users/lorenzodona/Desktop/openmpi-1.7.1/bin
but the problem is the same
after type make i type make check and I passed all the test.
when I try to compile a f.90 fi
you need to put your prefix at the beginning:
PATH=/Users/lorenzodona/Desktop/openmpi-1.7.1/bin:$PATH
LD_LIBRARY_PATH=/Users/lorenzodona/Desktop/openmpi-1.7.1/lib:$LD_LIBRARY_PATH
then check that you have it correct by
which mpif90
On Jun 19, 2013, at 12:31 PM, Lorenzo Donà wrote:
> I export
ok thans let me try and I will you know
:)
Il giorno 19/giu/2013, alle ore 21.37, Ralph Castain ha scritto:
> you need to put your prefix at the beginning:
>
> PATH=/Users/lorenzodona/Desktop/openmpi-1.7.1/bin:$PATH
> LD_LIBRARY_PATH=/Users/lorenzodona/Desktop/openmpi-1.7.1/lib:$LD_LIBRARY_PATH
>
I can confirm that
--enable-event-thread-support --enable-opal-multi-threads
--enable-orte-progress-threads --enable-mpi-thread-multiple
worked for me as well under OSX 10.8.4 with clang. The orte-progress flag is
needed, without it the parallel process hangs.
I will report this to the MacPor
I export the two paths like you told me but the error it is the same
Cannot open configuration file
/Users/lorenzodona/Desktop/openmpi-1.7.1/share/openmpi/opal_wrapper-wrapper-data.txt
Error parsing data file opal_wrapper: Not found
when i type in bin:
MacBook-Pro-di-Lorenzo-Dona:bin lorenzodona$
On 19 June 2013 20:42, Reuti wrote:
> Am 19.06.2013 um 19:43 schrieb Riccardo Murri :
>
>> On 19 June 2013 16:01, Ralph Castain wrote:
>>> How is OMPI picking up this hostfile? It isn't being specified on the cmd
>>> line - are you running under some resource manager?
>>
>> Via the environment v
On 19 June 2013 20:42, Ralph Castain wrote:
> I'm assuming that the offending host has some other address besides
> just 127.0.1.1 as otherwise it couldn't connect to anything.
Yes, it has an IP on some 10.x.x.x network.
> I'm heading out the door for a couple of weeks, but can try to look at i
Hi Lorenzo,
I think you should export the following before doing configuration step:
$ export F77=gfortran
$ export FFLAGS='-m64'
$ export FC=gfortran
$ export FCFLAGS='-m64'
Also include --enable-gfortran in the configure step line.
Yours,
Reem
On 19 June 2013 21:11, Lorenzo Donà wr
Hi Lorenzo
Did you really use:
>> -prefix=/Users/lorenzodona/Desktop/openmpi-1.7.1/bin
as you say in your email (note the extra "bin" at the end)?
Or did you perhaps use something more common?
Say:
-prefix=/Users/lorenzodona/Desktop/openmpi-1.7.1
Is the extra "bin" sub-directory in your pref
On Jun 19, 2013, at 4:11 PM, Lorenzo Donà wrote:
> MacBook-Pro-di-Lorenzo-Dona:bin lorenzodona$ mpif90
> --
> Unfortunately, this installation of Open MPI was not compiled with
> Fortran 90 support. As such, the mpif90 compi
Am 19.06.2013 um 22:14 schrieb Riccardo Murri:
> On 19 June 2013 20:42, Reuti wrote:
>> Am 19.06.2013 um 19:43 schrieb Riccardo Murri :
>>
>>> On 19 June 2013 16:01, Ralph Castain wrote:
How is OMPI picking up this hostfile? It isn't being specified on the cmd
line - are you running
28 matches
Mail list logo
