Re: [OMPI users] Help!!!!!!!!!!!!Openmpi instal for ubuntu 64 bits

[Gus Correa]

Jeff Squyres wrote:
Please note that this is an English-speaking list.  
I don't know if Tim speaks ?Spanish?, 


Portuguese.


but I unfortunately don't.  :-)

Also note that I asked for some specific information, 
but you ignored it when you replied.  Please see the following web page:


http://www.open-mpi.org/community/help/



On Nov 29, 2010, at 5:03 PM, Maurício Rodrigues wrote:

senhor Tim Prince, 

Gostaria de agradecer o email  que me enviou sobre openmpi, 
na verdade, estou tentando compilar o Regcm 4, 
e quando uso o comando, make regcm, aparece um erro 
"mpif90" por isso fui em busca da solução do problema do openmpi,
utilizo um computador de plataforma 64 bits com sistema operacional ubuntu 10, 
nao consigo instalar de forma alguma o open, faço passo a passo.


If you did not yet install OpenMPI, I wonder how can you use mpif90
to compile REGCM4.
You may be inadvertently using another mpif90, from another MPI,
perhaps something that came with Ubuntu or a compiler.

What is the output of "which mpif90"?



1- ./configure FC=ifort F77=ifort CC=icc CXX=icpc

2-make all

3 sudo make install all

os passos 1 e 2 operam normalmente, mas quando uso o comando make install 

aparece o erro que nao consigo solucionar.


You say only step 3 above fails.
You could try "sudo -E make install".

Alternatively, to avoid problems with sudo, you could configure
with --prefix=${HOME}/openmpi, where ${HOME} is
your home directory path.
Then install without sudo
(just "make install").

Good luck.

Gus Correa




se tiver alguma idéia sobre isso, por favor me ajude.



obrigado

2010/11/29 Tim Prince 
On 11/29/2010 11:31 AM, Gus Correa wrote:
Hi Mauricio

Check if you have icc (in the Intel compiler bin directory/subdirectories).

Check also if it is in your PATH environment variable.
"which icc" will tell.
If not, add it to PATH.

Actually, the right way to do it
is to run the Intel scripts to set the whole compiler environment,
not only PATH.
The scripts should be called something like iccvars.csh  iccvars.sh for C/C++ 
and  ifortvars.csh  ifortvars.sh for Fortran, and are also in the Intel bin 
directory.

You can source these scripts in your .cshrc/.bashrc file,
using the correct shell (.sh if you use [ba]sh, .csh if you use [t]csh).
This is in the Intel compiler documentation, take a look.
For the icc version mentioned, there is a compilervars.[c]sh which takes care 
of both C++ and Fortran (if present), as do either of the iccvars or ifortvars, 
when the compilers are installed in the same directory.


Also, you can compile OpenMPI with gcc,g++ and gfortran, if you want.
If they are not yet installed in your Ubuntu, you can get them with apt-get, or 
whatever Ubuntu uses to get packages.

icc ought to work interchangeably with gcc, provided the same g++ version is 
always on PATH. icc doesn't work without the g++.  Thus, it is entirely 
reasonable to build openmpi with gcc and use either gcc or icc to build the 
application.  gfortran and ifort, however, involve incompatible run-time 
libraries, and the openmpi fortran libraries won't be interchangeable.

You must take care not to mix 32- and 64-bit compilers/libraries.  Normally you 
would build everything 64-bit, both openmpi and the application.  Ubuntu 
doesn't follow the standard scheme for location of 32-bit vs. 64-bit compilers 
and libraries, but the Intel compiler version you mentioned should resolve this 
automatically.

--
Tim Prince


___
users mailing list
us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users



--
Maurício Paulo Rodrigues
Bacharelando em Física 
Universidade Federal de Viçosa

Mobile- (32)-9972 2239
e-mail alternativo mauricio.pa...@ufv.br 
___

users mailing list
us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users

Re: [OMPI users] [Rocks-Discuss] compiling Openmpi on solaris studio express

[Nehemiah Dacres]

thanks.
FYI: its openmpi-1.4.2 from a tarball like you assume
I changed this line
 *Sun\ F* | *Sun*Fortran*)
  # Sun Fortran 8.3 passes all unrecognized flags to the linker
  _LT_TAGVAR(lt_prog_compiler_pic, $1)='-KPIC'
  _LT_TAGVAR(lt_prog_compiler_static, $1)='-Bstatic'
  _LT_TAGVAR(lt_prog_compiler_wl, $1)='-Qoption ld '

 unfortunately my autoconf tool is out of date (2.59 , it says it wants
2.60+ )


On Mon, Nov 29, 2010 at 4:11 PM, Rolf vandeVaart  wrote:

>  No, I do not believe so.  First, I assume you are trying to build either
> 1.4 or 1.5, not the trunk.
> Secondly, I assume you are building from a tarfile that you have
> downloaded.  Assuming these
> two things are true, then (as stated in the bug report), prior to running
> configure, you want to
> make the following edits to config/libtool.m4 in all the places you see it.
> ( I think just one place)
>
> FROM:
>
> *Sun\ F*)
>   # Sun Fortran 8.3 passes all unrecognized flags to the linker
>   _LT_TAGVAR(lt_prog_compiler_pic, $1)='-KPIC'
>   _LT_TAGVAR(lt_prog_compiler_static, $1)='-Bstatic'
>   _LT_TAGVAR(lt_prog_compiler_wl, $1)=''
>   ;;
>
> TO:
>
> *Sun\ F*)
>   # Sun Fortran 8.3 passes all unrecognized flags to the linker
>   _LT_TAGVAR(lt_prog_compiler_pic, $1)='-KPIC'
>   _LT_TAGVAR(lt_prog_compiler_static, $1)='-Bstatic'
>   _LT_TAGVAR(lt_prog_compiler_wl, $1)='-Qoption ld '
>   ;;
>
>
>
> Note the difference in the lt_prog_compiler_wl line.
>
I ran ./configure anyway, but I don't think it did anything

>
> Then, you need to run ./autogen.sh.  Then, redo your configure but you do
> not need to do anything
> with LDFLAGS.  Just use your original flags.  I think this should work, but
> I am only reading
> what is in the ticket.
>
> Rolf
>
>
>
> On 11/29/10 16:26, Nehemiah Dacres wrote:
>
> that looks about right. So the suggestion:
>
> ./configure LDFLAGS="-notpath ... ... ..."
>
> -notpath should be replaced by whatever the proper flag should be, in my case 
> -L ?
>
>
>
>
> On Mon, Nov 29, 2010 at 3:16 PM, Rolf vandeVaart <
> rolf.vandeva...@oracle.com> wrote:
>
>> This problem looks a lot like a thread from earlier today.  Can you look
>> at this
>> ticket and see if it helps?  It has a workaround documented in it.
>>
>> https://svn.open-mpi.org/trac/ompi/ticket/2632
>>
>> Rolf
>>
>>
>> On 11/29/10 16:13, Prentice Bisbal wrote:
>>
>> No, it looks like ld is being called with the option -path, and your
>> linker doesn't use that switch. Grep you Makefile(s) for the string
>> "-path". It's probably in a statement defining LDFLAGS somewhere.
>>
>> When you find it, replace it with the equivalent switch for your
>> compiler. You may be able to override it's value on the configure
>> command-line, which is usually easiest/best:
>>
>> ./configure LDFLAGS="-notpath ... ... ..."
>>
>> --
>> Prentice
>>
>>
>> Nehemiah Dacres wrote:
>>
>>
>>  it may have been that  I didn't set ld_library_path
>>
>> On Mon, Nov 29, 2010 at 2:36 PM, Nehemiah Dacres 
>>  > wrote:
>>
>> thank you, you have been doubly helpful, but I am having linking
>> errors and I do not know what the solaris studio compiler's
>> preferred linker is. The
>>
>> the configure statement was
>>
>> ./configure --prefix=/state/partition1/apps/sunmpi/
>> --enable-mpi-threads --with-sge --enable-static
>> --enable-sparse-groups CC=/opt/oracle/solstudio12.2/bin/suncc
>> CXX=/opt/oracle/solstudio12.2/bin/sunCC
>> F77=/opt/oracle/solstudio12.2/bin/sunf77
>> FC=/opt/oracle/solstudio12.2/bin/sunf90
>>
>>compile statement was
>>
>> make all install 2>errors
>>
>>
>> error below is
>>
>> f90: Warning: Option -path passed to ld, if ld is invoked, ignored
>> otherwise
>> f90: Warning: Option -path passed to ld, if ld is invoked, ignored
>> otherwise
>> f90: Warning: Option -path passed to ld, if ld is invoked, ignored
>> otherwise
>> f90: Warning: Option -path passed to ld, if ld is invoked, ignored
>> otherwise
>> f90: Warning: Option -soname passed to ld, if ld is invoked, ignored
>> otherwise
>> /usr/bin/ld: unrecognized option '-path'
>> /usr/bin/ld: use the --help option for usage information
>> make[4]: *** [libmpi_f90.la  
>> ] Error 2
>> make[3]: *** [all-recursive] Error 1
>> make[2]: *** [all] Error 2
>> make[1]: *** [all-recursive] Error 1
>> make: *** [all-recursive] Error 1
>>
>> am I doing this wrong? are any of those configure flags unnecessary
>> or inappropriate
>>
>>
>>
>> On Mon, Nov 29, 2010 at 2:06 PM, Gus Correa >  > wrote:
>>
>> Nehemiah Dacres wrote:
>>
>> I want to compile 

Re: [OMPI users] Question about collective messages implementation

[George Bosilca]

With the increasing gap between network bandwidth and processor computing 
power, the current trend in linear algebra is toward communication avoiding 
algorithms (aka. replacing communications with redundant computations). You're 
taking the exact opposite path, I wonder if you can get any benefit ...

Moreover, your proposed approach only makes sense if you expect the LAPACK 
operation to be faster if the other cores are silent (in order to use them for 
the computation itself). This is very tricky to do for a single LAPACK call, as 
usually OMP_NUM_THREADS & co. are affecting the entire application. I remember 
reading somewhere that MKL provide a function to change the number of threads 
at runtime, maybe you should look in that direction.

  george.


On Nov 2, 2010, at 06:33 , Ashley Pittman wrote:

> 
> On 2 Nov 2010, at 10:21, Jerome Reybert wrote:
>> - in my implementation, is MPI_Bcast aware that it should use shared memory
>> memory communication? Is data go through the network? It seems it is the 
>> case,
>> considering the first results.
>> - is there any other methods to group task by machine, OpenMPI being aware
>> that it is grouping task by shared memory?
>> - is it possible to assign a policy (in this case, a shared memory policy) to
>> a Bcast or a Barrier call?
>> - do you have any better idea for this problem? :)
> 
> Interesting stuff, two points quickly spring to mind from the above:
> 
> MPI_Comm_split() is an expensive operation, sure the manual says it's low 
> cost but it shouldn't be used inside any critical loops so be sure you are 
> doing the Comm_Split() at startup and then re-using it as and when needed.
> 
> Any blocking call into OpenMPI will poll consuming CPU cycles until the call 
> is complete, you can mitigate against this by telling OpenMPI to aggressively 
> call yield whilst polling which would mean that your parallel Lapack function 
> could get the CPU resources it required.  Have a look at this FAQ entry for 
> details of the option and what you can expect it to do.
> 
> http://www.open-mpi.org/faq/?category=running#force-aggressive-degraded
> 
> Ashley.
> 
> -- 
> 
> Ashley Pittman, Bath, UK.
> 
> Padb - A parallel job inspection tool for cluster computing
> http://padb.pittman.org.uk
> 
> 
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users

Re: [OMPI users] Solaris10/SPARC: atomic_cmpset_64 broken

[George Bosilca]

We're in process of analyzing this issue. I'll keep you updated.

  george.


On Nov 13, 2010, at 08:40 , Nicolai Stange wrote:

> Hi everybody,
> 
> gcc 4.5.1 with -O2 optimizes the 'ret = newval' away because %0 is
> declared as being write only.
> Fix is attached.
> 
> Regards
> 
> Nicolai
> <02_fix_atomic_cmpset_64.diff>___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users

Re: [OMPI users] Help!!!!!!!!!!!!Openmpi instal for ubuntu 64 bits

[Jeff Squyres]

Please note that this is an English-speaking list.  I don't know if Tim speaks 
?Spanish?, but I unfortunately don't.  :-)

Also note that I asked for some specific information, but you ignored it when 
you replied.  Please see the following web page:

http://www.open-mpi.org/community/help/



On Nov 29, 2010, at 5:03 PM, Maurício Rodrigues wrote:

> senhor Tim Prince, 
> 
> Gostaria de agradecer o email  que me enviou sobre openmpi, na verdade, estou 
> tentando compilar o Regcm 4, e quando uso o comando, make regcm, aparece um 
> erro "mpif90" por isso fui em busca da solução do problema do openmpi,utilizo 
> um computador de plataforma 64 bits com sistema operacional ubuntu 10, nao 
> consigo instalar de forma alguma o open, faço passo a passo.
> 
> 1- ./configure FC=ifort F77=ifort CC=icc CXX=icpc
> 
> 2-make all
> 
> 3 sudo make install all
> 
> os passos 1 e 2 operam normalmente, mas quando uso o comando make install 
> aparece o erro que nao consigo solucionar.
> 
> se tiver alguma idéia sobre isso, por favor me ajude.
> 
> 
> 
> obrigado
> 
> 2010/11/29 Tim Prince 
> On 11/29/2010 11:31 AM, Gus Correa wrote:
> Hi Mauricio
> 
> Check if you have icc (in the Intel compiler bin directory/subdirectories).
> 
> Check also if it is in your PATH environment variable.
> "which icc" will tell.
> If not, add it to PATH.
> 
> Actually, the right way to do it
> is to run the Intel scripts to set the whole compiler environment,
> not only PATH.
> The scripts should be called something like iccvars.csh  iccvars.sh for C/C++ 
> and  ifortvars.csh  ifortvars.sh for Fortran, and are also in the Intel bin 
> directory.
> 
> You can source these scripts in your .cshrc/.bashrc file,
> using the correct shell (.sh if you use [ba]sh, .csh if you use [t]csh).
> This is in the Intel compiler documentation, take a look.
> For the icc version mentioned, there is a compilervars.[c]sh which takes care 
> of both C++ and Fortran (if present), as do either of the iccvars or 
> ifortvars, when the compilers are installed in the same directory.
> 
> 
> Also, you can compile OpenMPI with gcc,g++ and gfortran, if you want.
> If they are not yet installed in your Ubuntu, you can get them with apt-get, 
> or whatever Ubuntu uses to get packages.
> 
> icc ought to work interchangeably with gcc, provided the same g++ version is 
> always on PATH. icc doesn't work without the g++.  Thus, it is entirely 
> reasonable to build openmpi with gcc and use either gcc or icc to build the 
> application.  gfortran and ifort, however, involve incompatible run-time 
> libraries, and the openmpi fortran libraries won't be interchangeable.
> 
> You must take care not to mix 32- and 64-bit compilers/libraries.  Normally 
> you would build everything 64-bit, both openmpi and the application.  Ubuntu 
> doesn't follow the standard scheme for location of 32-bit vs. 64-bit 
> compilers and libraries, but the Intel compiler version you mentioned should 
> resolve this automatically.
> 
> -- 
> Tim Prince
> 
> 
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
> 
> 
> 
> -- 
> Maurício Paulo Rodrigues
> Bacharelando em Física 
> Universidade Federal de Viçosa
> Mobile- (32)-9972 2239
> e-mail alternativo mauricio.pa...@ufv.br 
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users


-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/

Re: [OMPI users] Problem with sending messages from one of the machines

[George Bosilca]

You can use the tcp_if_include/tcp_if_exclude with address ranges instead of 
names. ompi_info --mca btl tcp give you some hints:

>  MCA btl: parameter "btl_tcp_if_include" (current value: 
> , data
>   source: default value)
>   Comma-delimited list of devices or CIDR notation of 
> networks
>   to use for MPI communication (e.g., "eth0,eth1" or
>   "192.168.0.0/16,10.1.4.0/24").  Mutually exclusive 
> with
>   btl_tcp_if_exclude.
>  MCA btl: parameter "btl_tcp_if_exclude" (current value: 
> , data
>   source: default value)
>   Comma-delimited list of devices or CIDR notation of 
> networks
>   to NOT use for MPI communication -- all devices not 
> matching
>   these specifications will be used (e.g., 
> "eth0,eth1" or
>   "192.168.0.0/16,10.1.4.0/24").  Mutually exclusive 
> with
>   btl_tcp_if_include.
> 

  george.


On Nov 18, 2010, at 05:19 , Krzysztof Zarzycki wrote:

> We just discovered this ticket, which might describe the same problem that we 
> have:
> 
> https://svn.open-mpi.org/trac/ompi/ticket/1505
> 
> It seems unresolved... do you have a workaround for it? I've seen the "-mca 
> opal_net_private_ipv4 " parameter, but I don't exactly know how to use it... 
> At least my experiments failed to do anything.
> 
> I'll be very grateful for your help,
> Krzysztof
> 
> 
> 2010/11/17 Grzegorz Maj 
> 2010/11/11 Jeff Squyres :
> > On Nov 11, 2010, at 3:23 PM, Krzysztof Zarzycki wrote:
> >
> >> No, unfortunately specification of interfaces is a little more 
> >> complicated...  eth0/1/2 is not common for both machines.
> >
> > Can you define "common"?  Do you mean that eth0 on one machine is on a 
> > different network then eth0 on the other machine?
> >
> > Is there any way that you can make them the same?  It would certainly make 
> > things easier.
> 
> Yes, they are on different networks and unfortunately we are not
> allowed to play with this.
> 
> >
> >> I've tried to play with (oob/btl)_tcp_ if_include, but actually... I don't 
> >> know exactly how.
> >
> > See my other mail:
> >
> >http://www.open-mpi.org/community/lists/users/2010/11/14737.php
> >
> >> Anyway, do you have any ideas how to further debug the communication 
> >> problem?
> >
> > The connect() is not getting through somehow.  Sadly, we don't have enough 
> > debug messages to show exactly what is going wrong when these kinds of 
> > things happen; I have a half-finished branch that has much better 
> > debug/error messages, but I've never had the time to finish it (indeed, I 
> > think there's a bug in that development branch right now, otherwise I'd 
> > recommend giving it a whirl).  :-\
> 
> Analyzing the strace of both processes shows, that on both sides the
> call to 'poll' after connect/accept succeeds. As I understand they
> even exchange some information, which is always 8 bytes, like
> D\227\0\1\0\0\0\0. One of them sends this information and the other
> receives it. But after receiving, it does:
> 
> 
> recv(8, "\5g\0\1\0\0\0\0", 8, 0)= 8
> fcntl64(8, F_GETFL) = 0x2 (flags O_RDWR)
> fcntl64(8, F_SETFL, O_RDWR|O_NONBLOCK)  = 0
> getpeername(8, {sa_family=AF_INET, sin_port=htons(57885),
> sin_addr=inet_addr("10.0.0.2")}, [16]) = 0
> close(8)
> 
> 
> In a working scenario (on another machines), after receiving, these
> bytes are resent and then proceeds the proper communication (my
> 'hello' message is sent).
> 
> The above address 10.0.0.2 is eth2 on the host machine, which indeed
> should be used in this communication.
> 
> While playing with network interfaces it came out, that when we bring
> down one of the aliases (eth2:0), it starts working. How should we
> enforce mpirun not to use this alias, when it's up? We were trying to
> use (oob/btl)_tcp_ if_exclude and specifying eth2:0, but it doesn't
> seem to help.
> 
> Regards,
> Grzegorz
> 
> 
> >
> > --
> > Jeff Squyres
> > jsquy...@cisco.com
> > For corporate legal information go to:
> > http://www.cisco.com/web/about/doing_business/legal/cri/
> >
> >
> > ___
> > users mailing list
> > us...@open-mpi.org
> > http://www.open-mpi.org/mailman/listinfo.cgi/users
> >
> >
> 
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
> 
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users

Re: [OMPI users] [Rocks-Discuss] compiling Openmpi on solaris studio express

[Rolf vandeVaart]

No, I do not believe so.  First, I assume you are trying to build either 
1.4 or 1.5, not the trunk.
Secondly, I assume you are building from a tarfile that you have 
downloaded.  Assuming these
two things are true, then (as stated in the bug report), prior to 
running configure, you want to
make the following edits to config/libtool.m4 in all the places you see 
it. ( I think just one place)


FROM:

   *Sun\ F*)
 # Sun Fortran 8.3 passes all unrecognized flags to the linker
 _LT_TAGVAR(lt_prog_compiler_pic, $1)='-KPIC'
 _LT_TAGVAR(lt_prog_compiler_static, $1)='-Bstatic'
 _LT_TAGVAR(lt_prog_compiler_wl, $1)=''
 ;;

TO:

   *Sun\ F*)
 # Sun Fortran 8.3 passes all unrecognized flags to the linker
 _LT_TAGVAR(lt_prog_compiler_pic, $1)='-KPIC'
 _LT_TAGVAR(lt_prog_compiler_static, $1)='-Bstatic'
 _LT_TAGVAR(lt_prog_compiler_wl, $1)='-Qoption ld '
 ;;



Note the difference in the lt_prog_compiler_wl line. 

Then, you need to run ./autogen.sh.  Then, redo your configure but you 
do not need to do anything
with LDFLAGS.  Just use your original flags.  I think this should work, 
but I am only reading

what is in the ticket.

Rolf


On 11/29/10 16:26, Nehemiah Dacres wrote:

that looks about right. So the suggestion:

./configure LDFLAGS="-notpath ... ... ..."

-notpath should be replaced by whatever the proper flag should be, in my case -L ? 

  

On Mon, Nov 29, 2010 at 3:16 PM, Rolf vandeVaart 
> wrote:


This problem looks a lot like a thread from earlier today.  Can
you look at this
ticket and see if it helps?  It has a workaround documented in it.

https://svn.open-mpi.org/trac/ompi/ticket/2632

Rolf


On 11/29/10 16:13, Prentice Bisbal wrote:

No, it looks like ld is being called with the option -path, and your
linker doesn't use that switch. Grep you Makefile(s) for the string
"-path". It's probably in a statement defining LDFLAGS somewhere.

When you find it, replace it with the equivalent switch for your
compiler. You may be able to override it's value on the configure
command-line, which is usually easiest/best:

./configure LDFLAGS="-notpath ... ... ..."

--
Prentice


Nehemiah Dacres wrote:
  

it may have been that  I didn't set ld_library_path

On Mon, Nov 29, 2010 at 2:36 PM, Nehemiah Dacres 
> wrote:

thank you, you have been doubly helpful, but I am having linking
errors and I do not know what the solaris studio compiler's
preferred linker is. The

the configure statement was

./configure --prefix=/state/partition1/apps/sunmpi/
--enable-mpi-threads --with-sge --enable-static
--enable-sparse-groups CC=/opt/oracle/solstudio12.2/bin/suncc
CXX=/opt/oracle/solstudio12.2/bin/sunCC
F77=/opt/oracle/solstudio12.2/bin/sunf77
FC=/opt/oracle/solstudio12.2/bin/sunf90

   compile statement was

make all install 2>errors


error below is

f90: Warning: Option -path passed to ld, if ld is invoked, ignored
otherwise
f90: Warning: Option -path passed to ld, if ld is invoked, ignored
otherwise
f90: Warning: Option -path passed to ld, if ld is invoked, ignored
otherwise
f90: Warning: Option -path passed to ld, if ld is invoked, ignored
otherwise
f90: Warning: Option -soname passed to ld, if ld is invoked, ignored
otherwise
/usr/bin/ld: unrecognized option '-path'
/usr/bin/ld: use the --help option for usage information
make[4]: *** [libmpi_f90.la  
] Error 2
make[3]: *** [all-recursive] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive] Error 1

am I doing this wrong? are any of those configure flags unnecessary
or inappropriate



On Mon, Nov 29, 2010 at 2:06 PM, Gus Correa 
> wrote:

Nehemiah Dacres wrote:

I want to compile openmpi to work with the solaris studio
express  or
solaris studio. This is a different version than is installed on
rockscluster 5.2  and would like to know if there any
gotchas or configure
flags I should use to get it working or portable to nodes on
the cluster.
Software-wise,  it is a fairly homogeneous environment with
only slight
variations on the hardware side which could be isolated
(machinefile flag
and what-not)
Please advise

Re: [OMPI users] Help!!!!!!!!!!!!Openmpi instal for ubuntu 64 bits

[Maurício Rodrigues]

senhor Tim Prince,

Gostaria de agradecer o email  que me enviou sobre openmpi, na verdade,
estou tentando compilar o Regcm 4, e quando uso o comando, make regcm,
aparece um erro "mpif90" por isso fui em busca da solução do problema do
openmpi,utilizo um computador de plataforma 64 bits com sistema operacional
ubuntu 10, nao consigo instalar de forma alguma o open, faço passo a passo.

1- ./configure FC=ifort F77=ifort CC=icc CXX=icpc

2-make all

3 sudo make install all

os passos 1 e 2 operam normalmente, mas quando uso o comando make install
aparece o erro que nao consigo solucionar.

se tiver alguma idéia sobre isso, por favor me ajude.



obrigado

2010/11/29 Tim Prince 

> On 11/29/2010 11:31 AM, Gus Correa wrote:
>
>> Hi Mauricio
>>
>> Check if you have icc (in the Intel compiler bin
>> directory/subdirectories).
>>
>> Check also if it is in your PATH environment variable.
>> "which icc" will tell.
>> If not, add it to PATH.
>>
>> Actually, the right way to do it
>> is to run the Intel scripts to set the whole compiler environment,
>> not only PATH.
>> The scripts should be called something like iccvars.csh  iccvars.sh for
>> C/C++ and  ifortvars.csh  ifortvars.sh for Fortran, and are also in the
>> Intel bin directory.
>>
>> You can source these scripts in your .cshrc/.bashrc file,
>> using the correct shell (.sh if you use [ba]sh, .csh if you use [t]csh).
>> This is in the Intel compiler documentation, take a look.
>>
> For the icc version mentioned, there is a compilervars.[c]sh which takes
> care of both C++ and Fortran (if present), as do either of the iccvars or
> ifortvars, when the compilers are installed in the same directory.
>
>
>> Also, you can compile OpenMPI with gcc,g++ and gfortran, if you want.
>> If they are not yet installed in your Ubuntu, you can get them with
>> apt-get, or whatever Ubuntu uses to get packages.
>>
>>  icc ought to work interchangeably with gcc, provided the same g++ version
> is always on PATH. icc doesn't work without the g++.  Thus, it is entirely
> reasonable to build openmpi with gcc and use either gcc or icc to build the
> application.  gfortran and ifort, however, involve incompatible run-time
> libraries, and the openmpi fortran libraries won't be interchangeable.
>
> You must take care not to mix 32- and 64-bit compilers/libraries.  Normally
> you would build everything 64-bit, both openmpi and the application.  Ubuntu
> doesn't follow the standard scheme for location of 32-bit vs. 64-bit
> compilers and libraries, but the Intel compiler version you mentioned should
> resolve this automatically.
>
> --
> Tim Prince
>
>
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
>



-- 
Maurício Paulo Rodrigues
Bacharelando em Física
Universidade Federal de Viçosa
Mobile- (32)-9972 2239
e-mail alternativo mauricio.pa...@ufv.br

Re: [OMPI users] [Rocks-Discuss] compiling Openmpi on solaris studio express

[Nehemiah Dacres]

I believe the user specifically wishes to use the special debugging tools in
Solaris Studio. The flag in question seems to be -rpath according to the
logs,  It would be suspicious if this was a flag for the Solaris linker. I
don't have access to any solaris machines but I may try make a virtual
install to investigate.



Hi Nehemiah

Hard to tell, I never tried Sun/Oracle Studio compilers.
However, the Intel compilers, for instance, require you to setup
environment variables that include PATH and LD_LIBRARY_PATH at least.
Would this be the case with Sun Studio?
Do you have its full environment set?

As for the error message,
indeed, "man ld" doesn't show "-path" as a possible option.
Would this be a "Solaris thing", perhaps an option
to the Solaris linker?

For what it is worth, OpenMPI compiles with gcc,g++ and gfortran,
which may be a workaround for you, if you want to stick to free compilers.
Likewise, it also compiles with Open64 compilers, although later
on I had trouble with the Open64 Fortran compiler (not to compile OpenMPI,
but MPI applications).
Do you have any specific requirement for Sun/Oracle software?

OpenMPI also compiles with Intel and PGI compilers,
but those aren't free.

Finally, make sure you are passing the Sun compilers to the OpenMPI
configure script correctly.
Somehow your warning messages are labeled "f90", not "sunf90" as I
would expect, but this may be just the way Sun decided to spell their
own error messages.

If you are in Rocks, better install the compilers in /share/apps,
not in /opt as it is now.
That will make the Sun compilers and their possible shared libraries
available to all nodes.
/share/apps is the right place to install mostly anything that doesn't
come in the Rocks/CentOS distribution.

Good luck,

Re: [OMPI users] [Rocks-Discuss] compiling Openmpi on solaris studio express

[Nehemiah Dacres]

I put the ld flag on the command line ( ./configure
--prefix=/state/partition1/apps/sunmpi/ --enable-mpi-threads --with-sge
--enable-static --enable-sparse-groups
CC=/opt/oracle/solstudio12.2/bin/suncc
CXX=/opt/oracle/solstudio12.2/bin/sunCC
F77=/opt/oracle/solstudio12.2/bin/sunf77
FC=/opt/oracle/solstudio12.2/bin/sunf90
LD_LIBRARY_PATH=/opt/oracle/solstudio12.2/lib/amd64/lib CFLAGS=-m64
CXXFLAGS=-m64 FFLAGS=-m64 FCFLAGS=-m64
LDFLAGS=-L/opt/oracle/solstudio12.2/lib/amd64/lib)
which may have been redundant but it still didn't work.

the last line before the same error is thus:

libtool: link: /opt/oracle/solstudio12.2/bin/sunf90 -G  .libs/mpi.o
.libs/mpi_sizeof.o .libs/mpi_comm_spawn_multiple_f90.o
.libs/mpi_testall_f90.o .libs/mpi_testsome_f90.o .libs/mpi_waitall_f90.o
.libs/mpi_waitsome_f90.o .libs/mpi_wtick_f90.o .libs/mpi_wtime_f90.o
-rpath /home/dacresni/openmpi/openmpi-1.4.2/ompi/.libs -rpath
/home/dacresni/openmpi/openmpi-1.4.2/orte/.libs -rpath
/home/dacresni/openmpi/openmpi-1.4.2/opal/.libs -rpath
/opt/oracle/solstudio12.2/lib
-L/home/dacresni/openmpi/openmpi-1.4.2/orte/.libs
-L/home/dacresni/openmpi/openmpi-1.4.2/opal/.libs
-L/opt/oracle/solstudio12.2/lib/amd64/lib ../../../ompi/.libs/libmpi.so
/home/dacresni/openmpi/openmpi-1.4.2/orte/.libs/libopen-rte.so
/home/dacresni/openmpi/openmpi-1.4.2/opal/.libs/libopen-pal.so -ldl -lnsl
-lutil -lm  -m64   -mt -soname libmpi_f90.so.0 -o .libs/libmpi_f90.so.0.0.0


which, if I'm not mistaken, specifically what i told it NOT to do.

On Mon, Nov 29, 2010 at 3:26 PM, Nehemiah Dacres  wrote:

> that looks about right. So the suggestion:
>
> ./configure LDFLAGS="-notpath ... ... ..."
>
> -notpath should be replaced by whatever the proper flag should be, in my case 
> -L ?
>
>
> On Mon, Nov 29, 2010 at 3:16 PM, Rolf vandeVaart <
> rolf.vandeva...@oracle.com> wrote:
>
>>  This problem looks a lot like a thread from earlier today.  Can you look
>> at this
>> ticket and see if it helps?  It has a workaround documented in it.
>>
>> https://svn.open-mpi.org/trac/ompi/ticket/2632
>>
>> Rolf
>>
>>
>> On 11/29/10 16:13, Prentice Bisbal wrote:
>>
>> No, it looks like ld is being called with the option -path, and your
>> linker doesn't use that switch. Grep you Makefile(s) for the string
>> "-path". It's probably in a statement defining LDFLAGS somewhere.
>>
>> When you find it, replace it with the equivalent switch for your
>> compiler. You may be able to override it's value on the configure
>> command-line, which is usually easiest/best:
>>
>> ./configure LDFLAGS="-notpath ... ... ..."
>>
>> --
>> Prentice
>>
>>
>> Nehemiah Dacres wrote:
>>
>>
>>  it may have been that  I didn't set ld_library_path
>>
>> On Mon, Nov 29, 2010 at 2:36 PM, Nehemiah Dacres 
>>  > wrote:
>>
>> thank you, you have been doubly helpful, but I am having linking
>> errors and I do not know what the solaris studio compiler's
>> preferred linker is. The
>>
>> the configure statement was
>>
>> ./configure --prefix=/state/partition1/apps/sunmpi/
>> --enable-mpi-threads --with-sge --enable-static
>> --enable-sparse-groups CC=/opt/oracle/solstudio12.2/bin/suncc
>> CXX=/opt/oracle/solstudio12.2/bin/sunCC
>> F77=/opt/oracle/solstudio12.2/bin/sunf77
>> FC=/opt/oracle/solstudio12.2/bin/sunf90
>>
>>compile statement was
>>
>> make all install 2>errors
>>
>>
>> error below is
>>
>> f90: Warning: Option -path passed to ld, if ld is invoked, ignored
>> otherwise
>> f90: Warning: Option -path passed to ld, if ld is invoked, ignored
>> otherwise
>> f90: Warning: Option -path passed to ld, if ld is invoked, ignored
>> otherwise
>> f90: Warning: Option -path passed to ld, if ld is invoked, ignored
>> otherwise
>> f90: Warning: Option -soname passed to ld, if ld is invoked, ignored
>> otherwise
>> /usr/bin/ld: unrecognized option '-path'
>> /usr/bin/ld: use the --help option for usage information
>> make[4]: *** [libmpi_f90.la  
>> ] Error 2
>> make[3]: *** [all-recursive] Error 1
>> make[2]: *** [all] Error 2
>> make[1]: *** [all-recursive] Error 1
>> make: *** [all-recursive] Error 1
>>
>> am I doing this wrong? are any of those configure flags unnecessary
>> or inappropriate
>>
>>
>>
>> On Mon, Nov 29, 2010 at 2:06 PM, Gus Correa >  > wrote:
>>
>> Nehemiah Dacres wrote:
>>
>> I want to compile openmpi to work with the solaris studio
>> express  or
>> solaris studio. This is a different version than is installed on
>> rockscluster 5.2  and would like to know if there any
>> gotchas or configure
>> flags I should use to get it working or portable to nodes on
>> the cluster.
>> 

Re: [OMPI users] MPI_Comm_split

[Jeff Squyres]

On Nov 24, 2010, at 4:55 PM, Hicham Mouline wrote:

> The tree is not symmetrical in that the valid values for the 10th parameter
> depends on the values selected in the 0th to 9th parameter (all the ancestry
> in the tree), for e.g., we may have a lot of nodes in the left of the tree
> than in the right, see attachment ( I hope they're allowed ) 
> 
> The depth of the tree of course is the same everywhere, but not all nodes at
> some level have the same number of children.
> Is it better to just list vertically all the possible branches (n-tuples) at
> the master level and split that list uniformly over the slaves?

Yes, you certainly can MPI_COMM_SPLIT this way.  As Bill mentioned, if you do 
the splits at the beginning of a long computation, the cost of them is 
irrelevant.  I would expect for 128 MPI processes, doing 7-8 MPI_COMM_SPLITs 
will take far less than a second (although that's a total SWAG).  So if it 
helps your coding and you're going to be running for a little while, go ahead 
and do them.

Bill mentioned one good reason for splitting communicators: distinct sub groups 
for MPI collectives.  Another good reason is for message separation.  If you 
want to do a parameter sweep in a specific set of procs, you can give them 
their own communicator in order to guarantee that you have "private" 
communications between them (e.g., that tag X will never collide with tag X on 
another process).

That being said, if all your communications will solely be within that subset 
of processes, then making new communicators may not be necessary. I.e., you'll 
never have colliding tags, so you don't need to create a private communication 
space.

That being said, it may be useful to have all your subgroups be able to have a 
starting rank of 0 and be able to use MPI_COMM_SIZE to find how many peers are 
in your subgroup.  Having distinct sub-communicators is helpful here.

That being said... (this can go on ad nauseam -- it just depends on your app 
and whether you want to do the splitting or not; there's no universally right 
answer here)

-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/

Re: [OMPI users] [Rocks-Discuss] compiling Openmpi on solaris studio express

[Gus Correa]

Hi Nehemiah

Hard to tell, I never tried Sun/Oracle Studio compilers.
However, the Intel compilers, for instance, require you to setup
environment variables that include PATH and LD_LIBRARY_PATH at least.
Would this be the case with Sun Studio?
Do you have its full environment set?

As for the error message,
indeed, "man ld" doesn't show "-path" as a possible option.
Would this be a "Solaris thing", perhaps an option
to the Solaris linker?

For what it is worth, OpenMPI compiles with gcc,g++ and gfortran,
which may be a workaround for you, if you want to stick to free compilers.
Likewise, it also compiles with Open64 compilers, although later
on I had trouble with the Open64 Fortran compiler (not to compile 
OpenMPI, but MPI applications).

Do you have any specific requirement for Sun/Oracle software?

OpenMPI also compiles with Intel and PGI compilers,
but those aren't free.

Finally, make sure you are passing the Sun compilers to the OpenMPI
configure script correctly.
Somehow your warning messages are labeled "f90", not "sunf90" as I
would expect, but this may be just the way Sun decided to spell their
own error messages.

If you are in Rocks, better install the compilers in /share/apps,
not in /opt as it is now.
That will make the Sun compilers and their possible shared libraries 
available to all nodes.

/share/apps is the right place to install mostly anything that doesn't
come in the Rocks/CentOS distribution.

Good luck,
Gus Correa


Nehemiah Dacres wrote:

it may have been that  I didn't set ld_library_path

On Mon, Nov 29, 2010 at 2:36 PM, Nehemiah Dacres  wrote:


thank you, you have been doubly helpful, but I am having linking errors and
I do not know what the solaris studio compiler's preferred linker is. The

the configure statement was

./configure --prefix=/state/partition1/apps/sunmpi/ --enable-mpi-threads
--with-sge --enable-static --enable-sparse-groups
CC=/opt/oracle/solstudio12.2/bin/suncc
CXX=/opt/oracle/solstudio12.2/bin/sunCC
F77=/opt/oracle/solstudio12.2/bin/sunf77
FC=/opt/oracle/solstudio12.2/bin/sunf90

   compile statement was

make all install 2>errors


error below is

f90: Warning: Option -path passed to ld, if ld is invoked, ignored
otherwise
f90: Warning: Option -path passed to ld, if ld is invoked, ignored
otherwise
f90: Warning: Option -path passed to ld, if ld is invoked, ignored
otherwise
f90: Warning: Option -path passed to ld, if ld is invoked, ignored
otherwise
f90: Warning: Option -soname passed to ld, if ld is invoked, ignored
otherwise
/usr/bin/ld: unrecognized option '-path'
/usr/bin/ld: use the --help option for usage information
make[4]: *** [libmpi_f90.la] Error 2
make[3]: *** [all-recursive] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive] Error 1

am I doing this wrong? are any of those configure flags unnecessary or
inappropriate



On Mon, Nov 29, 2010 at 2:06 PM, Gus Correa  wrote:


Nehemiah Dacres wrote:


I want to compile openmpi to work with the solaris studio express  or
solaris studio. This is a different version than is installed on
rockscluster 5.2  and would like to know if there any gotchas or
configure
flags I should use to get it working or portable to nodes on the cluster.
Software-wise,  it is a fairly homogeneous environment with only slight
variations on the hardware side which could be isolated (machinefile flag
and what-not)
Please advise



Hi Nehemiah
I just answered your email to the OpenMPI list.
I want to add that if you build OpenMPI with Torque support,
the machine file for each is not needed, it is provided by Torque.
I believe the same is true for SGE (but I don't use SGE).
Gus Correa




--
Nehemiah I. Dacres
System Administrator
Advanced Technology Group Saint Louis University

Re: [OMPI users] [Rocks-Discuss] compiling Openmpi on solaris studio express

[Nehemiah Dacres]

that looks about right. So the suggestion:

./configure LDFLAGS="-notpath ... ... ..."

-notpath should be replaced by whatever the proper flag should be, in
my case -L ?


On Mon, Nov 29, 2010 at 3:16 PM, Rolf vandeVaart  wrote:

>  This problem looks a lot like a thread from earlier today.  Can you look
> at this
> ticket and see if it helps?  It has a workaround documented in it.
>
> https://svn.open-mpi.org/trac/ompi/ticket/2632
>
> Rolf
>
>
> On 11/29/10 16:13, Prentice Bisbal wrote:
>
> No, it looks like ld is being called with the option -path, and your
> linker doesn't use that switch. Grep you Makefile(s) for the string
> "-path". It's probably in a statement defining LDFLAGS somewhere.
>
> When you find it, replace it with the equivalent switch for your
> compiler. You may be able to override it's value on the configure
> command-line, which is usually easiest/best:
>
> ./configure LDFLAGS="-notpath ... ... ..."
>
> --
> Prentice
>
>
> Nehemiah Dacres wrote:
>
>
>  it may have been that  I didn't set ld_library_path
>
> On Mon, Nov 29, 2010 at 2:36 PM, Nehemiah Dacres 
>  > wrote:
>
> thank you, you have been doubly helpful, but I am having linking
> errors and I do not know what the solaris studio compiler's
> preferred linker is. The
>
> the configure statement was
>
> ./configure --prefix=/state/partition1/apps/sunmpi/
> --enable-mpi-threads --with-sge --enable-static
> --enable-sparse-groups CC=/opt/oracle/solstudio12.2/bin/suncc
> CXX=/opt/oracle/solstudio12.2/bin/sunCC
> F77=/opt/oracle/solstudio12.2/bin/sunf77
> FC=/opt/oracle/solstudio12.2/bin/sunf90
>
>compile statement was
>
> make all install 2>errors
>
>
> error below is
>
> f90: Warning: Option -path passed to ld, if ld is invoked, ignored
> otherwise
> f90: Warning: Option -path passed to ld, if ld is invoked, ignored
> otherwise
> f90: Warning: Option -path passed to ld, if ld is invoked, ignored
> otherwise
> f90: Warning: Option -path passed to ld, if ld is invoked, ignored
> otherwise
> f90: Warning: Option -soname passed to ld, if ld is invoked, ignored
> otherwise
> /usr/bin/ld: unrecognized option '-path'
> /usr/bin/ld: use the --help option for usage information
> make[4]: *** [libmpi_f90.la  
> ] Error 2
> make[3]: *** [all-recursive] Error 1
> make[2]: *** [all] Error 2
> make[1]: *** [all-recursive] Error 1
> make: *** [all-recursive] Error 1
>
> am I doing this wrong? are any of those configure flags unnecessary
> or inappropriate
>
>
>
> On Mon, Nov 29, 2010 at 2:06 PM, Gus Correa   > wrote:
>
> Nehemiah Dacres wrote:
>
> I want to compile openmpi to work with the solaris studio
> express  or
> solaris studio. This is a different version than is installed on
> rockscluster 5.2  and would like to know if there any
> gotchas or configure
> flags I should use to get it working or portable to nodes on
> the cluster.
> Software-wise,  it is a fairly homogeneous environment with
> only slight
> variations on the hardware side which could be isolated
> (machinefile flag
> and what-not)
> Please advise
>
>
> Hi Nehemiah
> I just answered your email to the OpenMPI list.
> I want to add that if you build OpenMPI with Torque support,
> the machine file for each is not needed, it is provided by Torque.
> I believe the same is true for SGE (but I don't use SGE).
> Gus Correa
>
>
>
>
> --
> Nehemiah I. Dacres
> System Administrator
> Advanced Technology Group Saint Louis University
>
>
>
>
> --
> Nehemiah I. Dacres
> System Administrator
> Advanced Technology Group Saint Louis University
>
>
> 
>
> ___
> users mailing 
> listusers@open-mpi.orghttp://www.open-mpi.org/mailman/listinfo.cgi/users
>
>  ___
> users mailing 
> listusers@open-mpi.orghttp://www.open-mpi.org/mailman/listinfo.cgi/users
>
>
>
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
>



-- 
Nehemiah I. Dacres
System Administrator
Advanced Technology Group Saint Louis University

Re: [OMPI users] launching the mpi runtime

[Jeff Squyres]

On Nov 29, 2010, at 2:29 PM, Hicham Mouline wrote:

> If the GUI's on windows, and the compute processes are on linux for
> instance, no MPI communication is possible right.
> That means, I do need to write custom code to communicate between the GUI
> process (win) and the mpi master (linux)

With Open MPI, correct -- we don't currently support "MPI talk" between Windows 
and Linux.  Sorry!  :-(

-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/

Re: [OMPI users] launching the mpi runtime

[Jeff Squyres]

On Nov 24, 2010, at 4:41 PM, Hicham Mouline wrote:

>> Sadly true.  There has been (very) little demand for this, so we
>> haven't spent much (any) time on making it work.
> 
> Is it the same for MacOSX? can't mix MacOsX and linux?
> Can't mix Win and MacOSX?

The issue is mainly Windows, I believe.  I *believe* that the network transport 
that Windows uses is not compatible with any other.

Shiqing -- can you confirm/deny?

Hence, you can run OSX + Linux MPI jobs, although you need to be careful about 
exactly how you do it -- heterogeneity is not for the meek.  You need to have 
different executables for your different OS's, for example.

-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/

Re: [OMPI users] launching the mpi runtime

[Jeff Squyres]

On Nov 23, 2010, at 8:34 AM, Hicham Mouline wrote:

>> MPI doesn't necessarily mean SPMD -- you can certainly have the GUI call 
>> MPI_INIT and then call MPI_COMM_SPAWN to launch a different >executable to 
>> do the compute working stuff. 
> 
> This is confusing to me.
> If the GUI does that, will the GUI process (running on windows) be able to 
> spawn mpi processes on separate linux boxes and "MPI talk" to them using the 
> intercommunicator returned?

Sorry for the delayed reply -- SC10 and the US holiday got in the way.

All I mean here is that your MPI job doesn't have to consist of a single 
executable.  You can have a GUI front-end application that MPI_COMM_SPAWN's 
non-GUI worker processes on the back-end nodes.

The point of MPI_COMM_SPAWN is that you can spawn some other MPI processes and 
get an intercommuicator back that you can use for normal MPI communications.  
To be clear, if your GUI calls MPI_COMM_SPAWN to launch non-GUI "worker" 
executable on the compute nodes, then you can use the intercommunicator that is 
returned via MPI_COMM_SPAWN to MPI_SEND / MPI_RECV / etc. with the new 
processes.  The new processes will need to call MPI_COMM_GET_PARENT to get the 
intercommunicator that is shared with the parent process(es).

Make sense?  Read through the MPI spec section on "dynamic processes" for more 
details.

-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/

Re: [OMPI users] [Rocks-Discuss] compiling Openmpi on solaris studio express

[Rolf vandeVaart]

This problem looks a lot like a thread from earlier today.  Can you look 
at this

ticket and see if it helps?  It has a workaround documented in it.

https://svn.open-mpi.org/trac/ompi/ticket/2632

Rolf

On 11/29/10 16:13, Prentice Bisbal wrote:

No, it looks like ld is being called with the option -path, and your
linker doesn't use that switch. Grep you Makefile(s) for the string
"-path". It's probably in a statement defining LDFLAGS somewhere.

When you find it, replace it with the equivalent switch for your
compiler. You may be able to override it's value on the configure
command-line, which is usually easiest/best:

./configure LDFLAGS="-notpath ... ... ..."

--
Prentice


Nehemiah Dacres wrote:
  

it may have been that  I didn't set ld_library_path

On Mon, Nov 29, 2010 at 2:36 PM, Nehemiah Dacres > wrote:

thank you, you have been doubly helpful, but I am having linking
errors and I do not know what the solaris studio compiler's
preferred linker is. The

the configure statement was

./configure --prefix=/state/partition1/apps/sunmpi/
--enable-mpi-threads --with-sge --enable-static
--enable-sparse-groups CC=/opt/oracle/solstudio12.2/bin/suncc
CXX=/opt/oracle/solstudio12.2/bin/sunCC
F77=/opt/oracle/solstudio12.2/bin/sunf77
FC=/opt/oracle/solstudio12.2/bin/sunf90

   compile statement was

make all install 2>errors


error below is

f90: Warning: Option -path passed to ld, if ld is invoked, ignored
otherwise
f90: Warning: Option -path passed to ld, if ld is invoked, ignored
otherwise
f90: Warning: Option -path passed to ld, if ld is invoked, ignored
otherwise
f90: Warning: Option -path passed to ld, if ld is invoked, ignored
otherwise
f90: Warning: Option -soname passed to ld, if ld is invoked, ignored
otherwise
/usr/bin/ld: unrecognized option '-path'
/usr/bin/ld: use the --help option for usage information
make[4]: *** [libmpi_f90.la ] Error 2
make[3]: *** [all-recursive] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive] Error 1

am I doing this wrong? are any of those configure flags unnecessary
or inappropriate



On Mon, Nov 29, 2010 at 2:06 PM, Gus Correa > wrote:

Nehemiah Dacres wrote:

I want to compile openmpi to work with the solaris studio
express  or
solaris studio. This is a different version than is installed on
rockscluster 5.2  and would like to know if there any
gotchas or configure
flags I should use to get it working or portable to nodes on
the cluster.
Software-wise,  it is a fairly homogeneous environment with
only slight
variations on the hardware side which could be isolated
(machinefile flag
and what-not)
Please advise


Hi Nehemiah
I just answered your email to the OpenMPI list.
I want to add that if you build OpenMPI with Torque support,
the machine file for each is not needed, it is provided by Torque.
I believe the same is true for SGE (but I don't use SGE).
Gus Correa




-- 
Nehemiah I. Dacres
System Administrator 
Advanced Technology Group Saint Louis University





--
Nehemiah I. Dacres
System Administrator 
Advanced Technology Group Saint Louis University





___
users mailing list
us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users



___
users mailing list
us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users
  

Re: [OMPI users] [Rocks-Discuss] compiling Openmpi on solaris studio express

[Prentice Bisbal]

No, it looks like ld is being called with the option -path, and your
linker doesn't use that switch. Grep you Makefile(s) for the string
"-path". It's probably in a statement defining LDFLAGS somewhere.

When you find it, replace it with the equivalent switch for your
compiler. You may be able to override it's value on the configure
command-line, which is usually easiest/best:

./configure LDFLAGS="-notpath ... ... ..."

--
Prentice


Nehemiah Dacres wrote:
> it may have been that  I didn't set ld_library_path
> 
> On Mon, Nov 29, 2010 at 2:36 PM, Nehemiah Dacres  > wrote:
> 
> thank you, you have been doubly helpful, but I am having linking
> errors and I do not know what the solaris studio compiler's
> preferred linker is. The
> 
> the configure statement was
> 
> ./configure --prefix=/state/partition1/apps/sunmpi/
> --enable-mpi-threads --with-sge --enable-static
> --enable-sparse-groups CC=/opt/oracle/solstudio12.2/bin/suncc
> CXX=/opt/oracle/solstudio12.2/bin/sunCC
> F77=/opt/oracle/solstudio12.2/bin/sunf77
> FC=/opt/oracle/solstudio12.2/bin/sunf90
> 
>compile statement was
> 
> make all install 2>errors
> 
> 
> error below is
> 
> f90: Warning: Option -path passed to ld, if ld is invoked, ignored
> otherwise
> f90: Warning: Option -path passed to ld, if ld is invoked, ignored
> otherwise
> f90: Warning: Option -path passed to ld, if ld is invoked, ignored
> otherwise
> f90: Warning: Option -path passed to ld, if ld is invoked, ignored
> otherwise
> f90: Warning: Option -soname passed to ld, if ld is invoked, ignored
> otherwise
> /usr/bin/ld: unrecognized option '-path'
> /usr/bin/ld: use the --help option for usage information
> make[4]: *** [libmpi_f90.la ] Error 2
> make[3]: *** [all-recursive] Error 1
> make[2]: *** [all] Error 2
> make[1]: *** [all-recursive] Error 1
> make: *** [all-recursive] Error 1
> 
> am I doing this wrong? are any of those configure flags unnecessary
> or inappropriate
> 
> 
> 
> On Mon, Nov 29, 2010 at 2:06 PM, Gus Correa  > wrote:
> 
> Nehemiah Dacres wrote:
> 
> I want to compile openmpi to work with the solaris studio
> express  or
> solaris studio. This is a different version than is installed on
> rockscluster 5.2  and would like to know if there any
> gotchas or configure
> flags I should use to get it working or portable to nodes on
> the cluster.
> Software-wise,  it is a fairly homogeneous environment with
> only slight
> variations on the hardware side which could be isolated
> (machinefile flag
> and what-not)
> Please advise
> 
> 
> Hi Nehemiah
> I just answered your email to the OpenMPI list.
> I want to add that if you build OpenMPI with Torque support,
> the machine file for each is not needed, it is provided by Torque.
> I believe the same is true for SGE (but I don't use SGE).
> Gus Correa
> 
> 
> 
> 
> -- 
> Nehemiah I. Dacres
> System Administrator 
> Advanced Technology Group Saint Louis University
> 
> 
> 
> 
> -- 
> Nehemiah I. Dacres
> System Administrator 
> Advanced Technology Group Saint Louis University
> 
> 
> 
> 
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users

Re: [OMPI users] [Rocks-Discuss] compiling Openmpi on solaris studio express

[Nehemiah Dacres]

thank you, you have been doubly helpful, but I am having linking errors and
I do not know what the solaris studio compiler's preferred linker is. The

the configure statement was

./configure --prefix=/state/partition1/apps/sunmpi/ --enable-mpi-threads
--with-sge --enable-static --enable-sparse-groups
CC=/opt/oracle/solstudio12.2/bin/suncc
CXX=/opt/oracle/solstudio12.2/bin/sunCC
F77=/opt/oracle/solstudio12.2/bin/sunf77
FC=/opt/oracle/solstudio12.2/bin/sunf90

   compile statement was

make all install 2>errors


error below is

f90: Warning: Option -path passed to ld, if ld is invoked, ignored otherwise
f90: Warning: Option -path passed to ld, if ld is invoked, ignored otherwise
f90: Warning: Option -path passed to ld, if ld is invoked, ignored otherwise
f90: Warning: Option -path passed to ld, if ld is invoked, ignored otherwise
f90: Warning: Option -soname passed to ld, if ld is invoked, ignored
otherwise
/usr/bin/ld: unrecognized option '-path'
/usr/bin/ld: use the --help option for usage information
make[4]: *** [libmpi_f90.la] Error 2
make[3]: *** [all-recursive] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive] Error 1

am I doing this wrong? are any of those configure flags unnecessary or
inappropriate



On Mon, Nov 29, 2010 at 2:06 PM, Gus Correa  wrote:

> Nehemiah Dacres wrote:
>
>> I want to compile openmpi to work with the solaris studio express  or
>> solaris studio. This is a different version than is installed on
>> rockscluster 5.2  and would like to know if there any gotchas or configure
>> flags I should use to get it working or portable to nodes on the cluster.
>> Software-wise,  it is a fairly homogeneous environment with only slight
>> variations on the hardware side which could be isolated (machinefile flag
>> and what-not)
>> Please advise
>>
>>
> Hi Nehemiah
> I just answered your email to the OpenMPI list.
> I want to add that if you build OpenMPI with Torque support,
> the machine file for each is not needed, it is provided by Torque.
> I believe the same is true for SGE (but I don't use SGE).
> Gus Correa
>



-- 
Nehemiah I. Dacres
System Administrator
Advanced Technology Group Saint Louis University

Re: [OMPI users] Help!!!!!!!!!!!!Openmpi instal for ubuntu 64 bits

[Tim Prince]

On 11/29/2010 11:31 AM, Gus Correa wrote:

Hi Mauricio

Check if you have icc (in the Intel compiler bin 
directory/subdirectories).


Check also if it is in your PATH environment variable.
"which icc" will tell.
If not, add it to PATH.

Actually, the right way to do it
is to run the Intel scripts to set the whole compiler environment,
not only PATH.
The scripts should be called something like iccvars.csh  iccvars.sh 
for C/C++ and  ifortvars.csh  ifortvars.sh for Fortran, and are also 
in the Intel bin directory.


You can source these scripts in your .cshrc/.bashrc file,
using the correct shell (.sh if you use [ba]sh, .csh if you use [t]csh).
This is in the Intel compiler documentation, take a look.
For the icc version mentioned, there is a compilervars.[c]sh which takes 
care of both C++ and Fortran (if present), as do either of the iccvars 
or ifortvars, when the compilers are installed in the same directory.


Also, you can compile OpenMPI with gcc,g++ and gfortran, if you want.
If they are not yet installed in your Ubuntu, you can get them with 
apt-get, or whatever Ubuntu uses to get packages.


icc ought to work interchangeably with gcc, provided the same g++ 
version is always on PATH. icc doesn't work without the g++.  Thus, it 
is entirely reasonable to build openmpi with gcc and use either gcc or 
icc to build the application.  gfortran and ifort, however, involve 
incompatible run-time libraries, and the openmpi fortran libraries won't 
be interchangeable.


You must take care not to mix 32- and 64-bit compilers/libraries.  
Normally you would build everything 64-bit, both openmpi and the 
application.  Ubuntu doesn't follow the standard scheme for location of 
32-bit vs. 64-bit compilers and libraries, but the Intel compiler 
version you mentioned should resolve this automatically.


--
Tim Prince

[OMPI users] compiling Openmpi on solaris studio express

[Nehemiah Dacres]

I want to compile openmpi to work with the solaris studio express  or
solaris studio. This is a different version than is installed on
rockscluster 5.2  and would like to know if there any gotchas or configure
flags I should use to get it working or portable to nodes on the cluster.
Software-wise,  it is a fairly homogeneous environment with only slight
variations on the hardware side which could be isolated (machinefile flag
and what-not)
Please advise

-- 
Nehemiah I. Dacres
System Administrator
Advanced Technology Group Saint Louis University

Re: [OMPI users] launching the mpi runtime

[Hicham Mouline]

>> therefore, I guess I need to separate the GUI binary from the
mpi-processes 
>> binary and have the GUI process talk to the "master" mpi process (on
linux) 
>> for calc requests. 
>> 
>> I was hoping I wouldn't have to write a custom code to do that. 
>MPI doesn't necessarily mean SPMD -- you can certainly have the GUI call
MPI_INIT and then call MPI_COMM_SPAWN to launch a >different executable to
do the compute working stuff.

Hi Jeff,

I couldn't quite understand this last statement.
If the GUI's on windows, and the compute processes are on linux for
instance, no MPI communication is possible right.
That means, I do need to write custom code to communicate between the GUI
process (win) and the mpi master (linux)

regards,

Re: [OMPI users] Help!!!!!!!!!!!!Openmpi instal for ubuntu 64 bits

[Ralph Castain]

I would guess that the problem is that your path and ld_library_path aren't 
correctly pointing to the Intel compiler. Try ensuring they are and then 
rebuild.


On Nov 29, 2010, at 11:07 AM, Maurício Rodrigues wrote:

> I'm using Intel ® C + + 2011 Composer XE for Linux, I have no idea how to 
> solve this problem.
> I would like to help if possible.
> Thank you from the already
> 
> Em 29 de novembro de 2010 16:06, Maurício Rodrigues 
>  escreveu:
>  usando o Intel®  C++ Composer XE 2011 for Linux, nao tenho nenhuma idéia de 
> como resolver este problema.
> gostaria de ajuda se possivel.
> obrigado desde de já
> 
> 2010/11/29 Ralph Castain 
> 
> Are you using the Intel compiler? The build system is looking for an "icc" 
> command and not finding it. Perhaps something in your environment is defining 
> CC to be "icc"?
> 
> 
> On Nov 29, 2010, at 10:43 AM, Maurício Rodrigues wrote:
> 
>> HI, I need to install opnmpi 1.4.2 in Ubuntu 4.10 64bit, and giving this 
>> error all the time ... I would like to help.
>> below follows the lines of the error.
>> 
>> Thank you!
>> 
>> /home/fjustino/fjustino/openmpi-1.4.2/libtool: line 7847: icc: command not 
>> found
>> libtool: install: error: relink `libopen-rte.la' with the above command 
>> before installing it
>> make[3]: *** [install-libLTLIBRARIES] Error 1
>> make[3]: Leaving directory `/home/fjustino/fjustino/openmpi-1.4.2/orte'
>> make[2]: *** [install-am] Error 2
>> make[2]: Leaving directory `/home/fjustino/fjustino/openmpi-1.4.2/orte'
>> make[1]: *** [install-recursive] Error 1
>> make[1]: Leaving directory `/home/fjustino/fjustino/openmpi-1.4.2/orte'
>> make: *** [install-recursive] Error 1
>> 
>> 
>> 
>> -- 
>> Maurício Paulo Rodrigues
>> Bacharelando em Física 
>> Universidade Federal de Viçosa
>> Mobile- (32)-9972 2239
>> e-mail alternativo mauricio.pa...@ufv.br 
>> Brazil
>> ___
>> users mailing list
>> us...@open-mpi.org
>> http://www.open-mpi.org/mailman/listinfo.cgi/users
> 
> 
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
> 
> 
> 
> -- 
> Maurício Paulo Rodrigues
> Bacharelando em Física 
> Universidade Federal de Viçosa
> Mobile- (32)-9972 2239
> e-mail alternativo mauricio.pa...@ufv.br 
> 
> 
> 
> -- 
> Maurício Paulo Rodrigues
> Bacharelando em Física 
> Universidade Federal de Viçosa
> Mobile- (32)-9972 2239
> e-mail alternativo mauricio.pa...@ufv.br 
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users

[OMPI users] Mac Ifort and gfortran together

[David Robertson]

Hi all,

I'm noticing a strange problem with Open MPI 1.4.2 on Mac OS X 10.6. We 
use both Intel Ifort 11.1 and gfortran 4.3 on the same machine and 
switch between them to test and debug code.


I had runtime problems when I compiled openmpi in my usual way of no 
shared libraries so I switched to shared and it runs now. However, in 
order for it to work with ifort I ended up needing to add the location 
of my intel compiled Open MPI libraries (/opt/intelsoft/openmpi/lib) to 
my DYLD_LIBRARY_PATH environment variable to to get codes to compile 
and/or run with ifort.


The problem is that adding /opt/intelsoft/openmpi/lib to 
DYLD_LIBRARY_PATH broke my Open MPI for gfortran. Now when I try to 
compile with mpif90 for gfortran it thinks it's actually trying to 
compile with ifort still. As soon as I take the above path out of 
DYLD_LIBRARY_PATH everything works fine.


Also, when I run ompi_info everything looks right except prefix. It says 
/opt/intelsoft/openmpi rather than /opt/gfortransoft/openmpi like it 
should. It should be noted that having /opt/intelsoft/openmpi in 
LD_LIBRARY_PATH does not produce the same effect.


Thanks,
Dave

Re: [OMPI users] MPI-IO Lustre driver update?

[Jeff Squyres]

On Nov 29, 2010, at 11:46 AM, George Wm Turner wrote:

> Is there a rough, order of magnitude timeline for v1.5.2?  I have a user 
> wanting to do some serious testing on the Lustre filesystem and he's 
> wondering what options he should consider.

Definitely not before January.  I'd estimate the Feburary timeline, although 
ROMIO will likely come into the OMPI trunk in the "near future" (i.e., Bull is 
actively working on it -- I just sent some comments on their patch earlier 
today).

-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/

Re: [OMPI users] mpool_sm_max_size disappeared ?

[Eugene Loh]

Gilbert Grosdidier wrote:

  
  
  I found this parameter mpool_sm_max_size in this post:
  http://www.open-mpi.org/community/lists/devel/2008/11/4883.php
  
  
  But I was unable to spot it back into the 'ompi_info -all'
output for v 1.4.3.
  Is it still existing ?
  

No.

  
   If not, which other one is replacing it, please ?
  

It no longer makes any sense.

Up through OMPI 1.3.1, OMPI made crude estimates of how large the sm
backing file should be.  You could limit the actual size with min and
max parameters.  The problem was that the estimate was so crude that
often the allocated size was excessively large while in other cases the
size was insufficient to allow the job to start up.  After 1.3.1, the
estimate of the size needed to start the job became much more precise. 
So, the job should always at least start.  You might still want to
employ a "minimum" (to give the sm area some extra room for performance
reasons), but there is no longer any point in have a "maximum" size. 
If you were to set a maximum that is smaller than what OMPI needs, the
job wouldn't start anyhow.

You may find the FAQ useful.  Check
http://www.open-mpi.org/faq/?category=sm .  There are discussions of
these issues, plus ways of estimating how much room OMPI needs,
therefore also ways of tuning OMPI so that it will need less.  E.g., if
you think the sm area is taking up too much space, the FAQ tells you
what parameters to use to make OMPI less space hungry.

  
  Also, is it possible to specify to OpenMPI
  which filesystem to use for the SM backing file, please ?
  

Again, check the FAQ.
http://www.open-mpi.org/faq/?category=sm#where-sm-file

  
  Thanks in advance for any help,   Regards,   G.
  
  


  

De rien.

Re: [OMPI users] Help!!!!!!!!!!!!Openmpi instal for ubuntu 64 bits

[Maurício Rodrigues]

I'm using Intel ® C + + 2011 Composer XE for Linux, I have no idea how to
solve this problem.
I would like to help if possible.
Thank you from the alreadyá

2010/11/29 Jeff Squyres 

> That's a lot of exclamation points.  :-)
>
> It looks like the Intel compiler executable (icc) is simply not found.
>  However, I'm surprised you got so far in the build process before that
> error occurs -- that doesn't seem right.
>
> Please send all the information listed here:
>
>http://www.open-mpi.org/community/help/
>
>
> On Nov 29, 2010, at 12:43 PM, Maurício Rodrigues wrote:
>
> > HI, I need to install opnmpi 1.4.2 in Ubuntu 4.10 64bit, and giving this
> error all the time ... I would like to help.
> > below follows the lines of the error.
> >
> > Thank you!
> >
> > /home/fjustino/fjustino/openmpi-1.4.2/libtool: line 7847: icc: command
> not found
> > libtool: install: error: relink `libopen-rte.la' with the above command
> before installing it
> > make[3]: *** [install-libLTLIBRARIES] Error 1
> > make[3]: Leaving directory `/home/fjustino/fjustino/openmpi-1.4.2/orte'
> > make[2]: *** [install-am] Error 2
> > make[2]: Leaving directory `/home/fjustino/fjustino/openmpi-1.4.2/orte'
> > make[1]: *** [install-recursive] Error 1
> > make[1]: Leaving directory `/home/fjustino/fjustino/openmpi-1.4.2/orte'
> > make: *** [install-recursive] Error 1
> >
> >
> >
> > --
> > Maurício Paulo Rodrigues
> > Bacharelando em Física
> > Universidade Federal de Viçosa
> > Mobile- (32)-9972 2239
> > e-mail alternativo mauricio.pa...@ufv.br
> > Brazil
> > ___
> > users mailing list
> > us...@open-mpi.org
> > http://www.open-mpi.org/mailman/listinfo.cgi/users
>
>
> --
> Jeff Squyres
> jsquy...@cisco.com
> For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/
>
>
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
>



-- 
Maurício Paulo Rodrigues
Bacharelando em Física
Universidade Federal de Viçosa
Mobile- (32)-9972 2239
e-mail alternativo mauricio.pa...@ufv.br

Re: [OMPI users] Help!!!!!!!!!!!!Openmpi instal for ubuntu 64 bits

[Maurício Rodrigues]

I'm using Intel ® C + + 2011 Composer XE for Linux, I have no idea how to
solve this problem.
I would like to help if possible.
Thank you from the already

Em 29 de novembro de 2010 16:06, Maurício Rodrigues <
mauriciopaulorodrig...@gmail.com> escreveu:

>  usando o Intel®  C++ Composer XE 2011 for Linux, nao tenho nenhuma idéia
> de como resolver este problema.
> gostaria de ajuda se possivel.
> obrigado desde de já
>
> 2010/11/29 Ralph Castain 
>
> Are you using the Intel compiler? The build system is looking for an "icc"
>> command and not finding it. Perhaps something in your environment is
>> defining CC to be "icc"?
>>
>>
>> On Nov 29, 2010, at 10:43 AM, Maurício Rodrigues wrote:
>>
>> HI, I need to install opnmpi 1.4.2 in Ubuntu 4.10 64bit, and giving this
>> error all the time ... I would like to help.
>> below follows the lines of the error.
>>
>> Thank you!
>>
>> /home/fjustino/fjustino/openmpi-1.4.2/libtool: line 7847: icc: command not
>> found
>> libtool: install: error: relink `libopen-rte.la' with the above command
>> before installing it
>> make[3]: *** [install-libLTLIBRARIES] Error 1
>> make[3]: Leaving directory `/home/fjustino/fjustino/openmpi-1.4.2/orte'
>> make[2]: *** [install-am] Error 2
>> make[2]: Leaving directory `/home/fjustino/fjustino/openmpi-1.4.2/orte'
>> make[1]: *** [install-recursive] Error 1
>> make[1]: Leaving directory `/home/fjustino/fjustino/openmpi-1.4.2/orte'
>> make: *** [install-recursive] Error 1
>>
>>
>>
>> --
>> Maurício Paulo Rodrigues
>> Bacharelando em Física
>> Universidade Federal de Viçosa
>> Mobile- (32)-9972 2239
>> e-mail alternativo mauricio.pa...@ufv.br
>> Brazil
>>  ___
>> users mailing list
>> us...@open-mpi.org
>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>>
>>
>>
>> ___
>> users mailing list
>> us...@open-mpi.org
>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>>
>
>
>
> --
> Maurício Paulo Rodrigues
> Bacharelando em Física
> Universidade Federal de Viçosa
> Mobile- (32)-9972 2239
> e-mail alternativo mauricio.pa...@ufv.br
>



-- 
Maurício Paulo Rodrigues
Bacharelando em Física
Universidade Federal de Viçosa
Mobile- (32)-9972 2239
e-mail alternativo mauricio.pa...@ufv.br

Re: [OMPI users] Help!!!!!!!!!!!!Openmpi instal for ubuntu 64 bits

[Maurício Rodrigues]

 usando o Intel®  C++ Composer XE 2011 for Linux, nao tenho nenhuma idéia de
como resolver este problema.
gostaria de ajuda se possivel.
obrigado desde de já

2010/11/29 Ralph Castain 

> Are you using the Intel compiler? The build system is looking for an "icc"
> command and not finding it. Perhaps something in your environment is
> defining CC to be "icc"?
>
>
> On Nov 29, 2010, at 10:43 AM, Maurício Rodrigues wrote:
>
> HI, I need to install opnmpi 1.4.2 in Ubuntu 4.10 64bit, and giving this
> error all the time ... I would like to help.
> below follows the lines of the error.
>
> Thank you!
>
> /home/fjustino/fjustino/openmpi-1.4.2/libtool: line 7847: icc: command not
> found
> libtool: install: error: relink `libopen-rte.la' with the above command
> before installing it
> make[3]: *** [install-libLTLIBRARIES] Error 1
> make[3]: Leaving directory `/home/fjustino/fjustino/openmpi-1.4.2/orte'
> make[2]: *** [install-am] Error 2
> make[2]: Leaving directory `/home/fjustino/fjustino/openmpi-1.4.2/orte'
> make[1]: *** [install-recursive] Error 1
> make[1]: Leaving directory `/home/fjustino/fjustino/openmpi-1.4.2/orte'
> make: *** [install-recursive] Error 1
>
>
>
> --
> Maurício Paulo Rodrigues
> Bacharelando em Física
> Universidade Federal de Viçosa
> Mobile- (32)-9972 2239
> e-mail alternativo mauricio.pa...@ufv.br
> Brazil
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
>
>
>
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
>



-- 
Maurício Paulo Rodrigues
Bacharelando em Física
Universidade Federal de Viçosa
Mobile- (32)-9972 2239
e-mail alternativo mauricio.pa...@ufv.br

Re: [OMPI users] Help!!!!!!!!!!!!Openmpi instal for ubuntu 64 bits

[Ralph Castain]

Are you using the Intel compiler? The build system is looking for an "icc" 
command and not finding it. Perhaps something in your environment is defining 
CC to be "icc"?


On Nov 29, 2010, at 10:43 AM, Maurício Rodrigues wrote:

> HI, I need to install opnmpi 1.4.2 in Ubuntu 4.10 64bit, and giving this 
> error all the time ... I would like to help.
> below follows the lines of the error.
> 
> Thank you!
> 
> /home/fjustino/fjustino/openmpi-1.4.2/libtool: line 7847: icc: command not 
> found
> libtool: install: error: relink `libopen-rte.la' with the above command 
> before installing it
> make[3]: *** [install-libLTLIBRARIES] Error 1
> make[3]: Leaving directory `/home/fjustino/fjustino/openmpi-1.4.2/orte'
> make[2]: *** [install-am] Error 2
> make[2]: Leaving directory `/home/fjustino/fjustino/openmpi-1.4.2/orte'
> make[1]: *** [install-recursive] Error 1
> make[1]: Leaving directory `/home/fjustino/fjustino/openmpi-1.4.2/orte'
> make: *** [install-recursive] Error 1
> 
> 
> 
> -- 
> Maurício Paulo Rodrigues
> Bacharelando em Física 
> Universidade Federal de Viçosa
> Mobile- (32)-9972 2239
> e-mail alternativo mauricio.pa...@ufv.br 
> Brazil
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users

Re: [OMPI users] Help!!!!!!!!!!!!Openmpi instal for ubuntu 64 bits

[Damien]

icc is the Intel C/C++ compiler.  Do you have it installed on your system?

Damien

On 29/11/2010 10:43 AM, Maurício Rodrigues wrote:
HI, I need to install opnmpi 1.4.2 in Ubuntu 4.10 64bit, and giving 
this error all the time ... I would like to help.

below follows the lines of the error.

Thank you!

/home/fjustino/fjustino/openmpi-1.4.2/libtool: line 7847: icc: command 
not found
libtool: install: error: relink `libopen-rte.la 
' with the above command before installing it

make[3]: *** [install-libLTLIBRARIES] Error 1
make[3]: Leaving directory `/home/fjustino/fjustino/openmpi-1.4.2/orte'
make[2]: *** [install-am] Error 2
make[2]: Leaving directory `/home/fjustino/fjustino/openmpi-1.4.2/orte'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/home/fjustino/fjustino/openmpi-1.4.2/orte'
make: *** [install-recursive] Error 1



--
Maurício Paulo Rodrigues
Bacharelando em Física
Universidade Federal de Viçosa
Mobile- (32)-9972 2239
e-mail alternativo mauricio.pa...@ufv.br 
Brazil


___
users mailing list
us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users

[OMPI users] Help!!!!!!!!!!!!Openmpi instal for ubuntu 64 bits

[Maurício Rodrigues]

HI, I need to install opnmpi 1.4.2 in Ubuntu 4.10 64bit, and giving this
error all the time ... I would like to help.
below follows the lines of the error.

Thank you!

/home/fjustino/fjustino/openmpi-1.4.2/libtool: line 7847: icc: command not
found
libtool: install: error: relink `libopen-rte.la' with the above command
before installing it
make[3]: *** [install-libLTLIBRARIES] Error 1
make[3]: Leaving directory `/home/fjustino/fjustino/openmpi-1.4.2/orte'
make[2]: *** [install-am] Error 2
make[2]: Leaving directory `/home/fjustino/fjustino/openmpi-1.4.2/orte'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/home/fjustino/fjustino/openmpi-1.4.2/orte'
make: *** [install-recursive] Error 1



-- 
Maurício Paulo Rodrigues
Bacharelando em Física
Universidade Federal de Viçosa
Mobile- (32)-9972 2239
e-mail alternativo mauricio.pa...@ufv.br
Brazil

Re: [OMPI users] Calling MPI_Test() too many times results in a time spike

[Ioannis Papadopoulos]

Hi,

Has anyone observed similar behaviour? Is it something that I'll have to 
deal with it in my code or does it indeed qualify as an issue to be 
looked into?


Thanks

Yiannis Papadopoulos wrote:

It is a quad core machine (Intel Core2 Quad CPU Q9550 - 64bit).
OpenMPI is the one that comes with Fedora 13.

I tested it on a cluster of Intel Xeon (32bit) with Gigabit Ethernet
with OpenMPI 1.3.3, the results are:

// with no timeout
Total time: 1.00309 secs
Estimated calls: 1116537
MPI_Test calls:  395488
Average: 0.018129 secs
Max: 0.0002990606 secs [91608]
Min: 0.008807 secs [694]
Successful MPI_Test(): 0.421085 secs

// with timeout
Total time: 1.00342 secs
Estimated calls: 1140521
MPI_Test calls:  1004
Average: 0.018511 secs
Max: 0.100477 secs [1003]
Min: 0.008813 secs [729]
Successful MPI_Test(): 0.100477 secs

I have seen similar behavior using IBM MPI on Power5+/AIX.
On Fri, Nov 12, 2010 at 11:00 AM, Jeff Squyres  wrote:
   

What kind of network did you do these tests on?

Were both processes on the same machine or different machines?


On Nov 10, 2010, at 12:29 AM, Yiannis Papadopoulos wrote:

 

Hello,

I am using OpenMPI 1.4.1. I have a small test case that calls
MPI_Test() too many times. I see one or two random time spikes when
this happens. On the other hand, if I avoid calling MPI_Test() based
on a timeout, this problem disappears.

For example, with no timeout, the results I'm getting are:
Total time: 1.8 secs
MPI_Test calls: 5541425
Average: 0.001234 secs
Max: 0.0002560616 secs [4374247]
Min: 0.00 secs [1]
Successful MPI_Test(): 0.090599 secs

With timeout of 0.0001secs (which means I just delay a bit calling MPI_Test()):
Total time: 1.9 secs
MPI_Test calls: 9946
Average: 0.18 secs
Max: 0.011921 secs [98]
Min: 0.00 secs [1]
Successful MPI_Test(): 0.011921 secs

With a timeout of 0.01secs:
Total time: 1.0001 secs
MPI_Test calls: 101
Average: 0.001936 secs
Max: 0.028610 secs [100]
Min: 0.00 secs [2]
Success: 0.028610 secs


Things to notice:
1) the total time is similar
2) the number of MPI_Test() calls varies drastically
3) the average MPI_Test() call time is significantly less when a
timeout is introduced
4) the call that takes the most time is not the last one (the
successful) as one would expect except the case that the timeout is a
bit big (0.01secs).
5) the time of the slowest MPI_Test() call is 2 orders of magnitude
higher than the the successful MPI_Test() in the non-timeout version.

Does this qualify as a bug?

Thanks


PS The code I have used follows. I compiled it with

  mpic++ -O3 mpi_test_delay.cc -o mpi_test_delay_no_timeout

for no timeout and

  mpic++ -O3 -DTIMEOUT=0.01 mpi_test_delay.cc -o mpi_test_delay

for a timeout of 0.01secs.

// mpi_test_delay.cc
#include
#include
#include
#include
#include
#include
#include

int main(int argc, char* argv[])
{
  MPI_Init(,);

  MPI_Comm comm = MPI_COMM_WORLD;
  int rank = MPI_PROC_NULL;
  int size = MPI_PROC_NULL;
  MPI_Comm_rank(comm,);
  MPI_Comm_size(comm,);

  if (size<2) {
MPI_Abort(comm, -1);
  }

  const std::size_t bufsize = 1024;
  char buffer[bufsize];

  // warm-up
  unsigned int N = 0;
  if (rank==0) {
sleep(1);
MPI_Send(buffer, bufsize, MPI_BYTE, 1, 0, comm);
  }
  else {
MPI_Request req;
MPI_Irecv(buffer, bufsize, MPI_BYTE, MPI_ANY_TAG, 0, comm,);
for (int flag = 0; flag==0; ++N) {
  MPI_Test(,, MPI_STATUS_IGNORE);
}
  }

  // measurement container
  std::vector  time_res;
  time_res.reserve(N * 1.1);

  MPI_Barrier(comm);

  // benchmark MPI_Test
  double total_time = MPI_Wtime();

  if (rank==0) {
sleep(1);
MPI_Send(buffer, bufsize, MPI_BYTE, 1, 0, comm);
  }
  else if (rank==1) {
MPI_Request req;
MPI_Irecv(buffer, bufsize, MPI_BYTE, MPI_ANY_TAG, 0, comm,);

#ifdef TIMEOUT
double timeout = 0.0;
#endif
for (int flag = 0; flag==0; ) {
#ifdef TIMEOUT
  double ntimeout = MPI_Wtime();
  if ( (ntimeout-timeout)

Re: [OMPI users] MPI-IO Lustre driver update?

[Jeff Squyres]

There's work going on right now to update the ROMIO in the OMPI v1.5 series.  
We hope to include it in v1.5.2.


On Nov 29, 2010, at 10:34 AM, Mark Dixon wrote:

> Hi,
> 
> I notice that there's been quite a bit of work recently on ROMIO's Lustre 
> driver. As far as I can see from openmpi's SVN, this doesn't seem to have 
> landed there yet (README indicates V04, yet V05 is in MPICH2 and MVAPICH2).
> 
> Is there a timescale for when this will be make it into a release, please?
> 
> Thanks,
> 
> Mark
> -- 
> -
> Mark Dixon   Email: m.c.di...@leeds.ac.uk
> HPC/Grid Systems Support Tel (int): 35429
> Information Systems Services Tel (ext): +44(0)113 343 5429
> University of Leeds, LS2 9JT, UK
> -
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users


-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/

Re: [OMPI users] mpool_sm_max_size disappeared ?

[Gilbert Grosdidier]

Bonjour,

 I found this parameter mpool_sm_max_size in this post:
http://www.open-mpi.org/community/lists/devel/2008/11/4883.php

 But I was unable to spot it back into the 'ompi_info -all' output for 
v 1.4.3.

Is it still existing ?

 If not, which other one is replacing it, please ?

 Also, is it possible to specify to OpenMPI
which filesystem to use for the SM backing file, please ?

 Thanks in advance for any help,   Regards,   G.

Re: [OMPI users] ABOUT ERROR WITH MPIRUN

[Jeff Squyres]

Sorry for the delay in replying; many of us were at SC10 and then most of us 
were off for the US Thanksgiving holiday last week.

This error means that your application called MPI_ABORT -- meaning that your 
application intentionally chose to quit.  You might need to look through the 
source code to figure out why it's doing that, and/or look at any messages 
above this one to figure out why it's choosing to abort like this.



On Nov 21, 2010, at 8:01 PM, Tushar Andriyas wrote:

> Hi there,
> 
> I had a few suggestions in the previous few threads and I have been trying a 
> lot of things to coax mpirun to work. But it does not want to. I am pasting 
> an error file and ompi_info 
> 
> ERROR FILE:
> 
> [uinta-0027:03360] MPI_ABORT invoked on rank 0 in communicator MPI_COMM_WORLD 
> w\
> ith errorcode 4776233
> [uinta-0027:03357] [0,0,0]-[0,1,4] mca_oob_tcp_msg_recv: readv failed: 
> Connecti\
> on reset by peer (104)
> mpirun noticed that job rank 1 with PID 3361 on node uinta-0027 exited on 
> signa\
> l 15 (Terminated).
> 
> ompi_info:
> 
> Open MPI: 1.2.7
>Open MPI SVN revision: r19401
> Open RTE: 1.2.7
>Open RTE SVN revision: r19401
> OPAL: 1.2.7
>OPAL SVN revision: r19401
>   Prefix: /opt/libraries/openmpi/openmpi-1.2.7-pgi
>  Configured architecture: x86_64-unknown-linux-gnu
>Configured by: A00017402
>Configured on: Thu Sep 18 15:00:05 MDT 2008
>   Configure host: volvox.hpc.usu.edu
> Built by: A00017402
> Built on: Thu Sep 18 15:20:06 MDT 2008
>   Built host: volvox.hpc.usu.edu
>   C bindings: yes
> C++ bindings: yes
>   Fortran77 bindings: yes (all)
>   Fortran90 bindings: yes
>  Fortran90 bindings size: large
>   C compiler: pgcc
>  C compiler absolute: /opt/apps/pgi/linux86-64/7.2/bin/pgcc
> C++ compiler: pgCC
>C++ compiler absolute: /opt/apps/pgi/linux86-64/7.2/bin/pgCC
>   Fortran77 compiler: pgf77
>   Fortran77 compiler abs: /opt/apps/pgi/linux86-64/7.2/bin/pgf77
>   Fortran90 compiler: pgf90
>   Fortran90 compiler abs: /opt/apps/pgi/linux86-64/7.2/bin/pgf90
>  C profiling: yes
>C++ profiling: yes
>  Fortran77 profiling: yes
>  Fortran90 profiling: yes
>   C++ exceptions: no
>   Thread support: posix (mpi: no, progress: no)
>   Internal debug support: no
>  MPI parameter check: runtime
> Memory profiling support: no
> Memory debugging support: no
>  libltdl support: yes
>Heterogeneous support: yes
>  mpirun default --prefix: no
>MCA backtrace: execinfo (MCA v1.0, API v1.0, Component v1.2.7)
>   MCA memory: ptmalloc2 (MCA v1.0, API v1.0, Component v1.2.7)
>MCA paffinity: linux (MCA v1.0, API v1.0, Component v1.2.7)
>MCA maffinity: first_use (MCA v1.0, API v1.0, Component v1.2.7)
>MCA maffinity: libnuma (MCA v1.0, API v1.0, Component v1.2.7)
>MCA timer: linux (MCA v1.0, API v1.0, Component v1.2.7)
>  MCA installdirs: env (MCA v1.0, API v1.0, Component v1.2.7)
>  MCA installdirs: config (MCA v1.0, API v1.0, Component v1.2.7)
>MCA allocator: basic (MCA v1.0, API v1.0, Component v1.0)
>MCA allocator: bucket (MCA v1.0, API v1.0, Component v1.0)
> MCA coll: basic (MCA v1.0, API v1.0, Component v1.2.7)
> MCA coll: self (MCA v1.0, API v1.0, Component v1.2.7)
> MCA coll: sm (MCA v1.0, API v1.0, Component v1.2.7)
> MCA coll: tuned (MCA v1.0, API v1.0, Component v1.2.7)
>   MCA io: romio (MCA v1.0, API v1.0, Component v1.2.7)
>MCA mpool: rdma (MCA v1.0, API v1.0, Component v1.2.7)
>MCA mpool: sm (MCA v1.0, API v1.0, Component v1.2.7)
>  MCA pml: cm (MCA v1.0, API v1.0, Component v1.2.7)
>  MCA pml: ob1 (MCA v1.0, API v1.0, Component v1.2.7)
>  MCA bml: r2 (MCA v1.0, API v1.0, Component v1.2.7)
>   MCA rcache: vma (MCA v1.0, API v1.0, Component v1.2.7)
>  MCA btl: gm (MCA v1.0, API v1.0.1, Component v1.2.7)
>  MCA btl: self (MCA v1.0, API v1.0.1, Component v1.2.7)
>  MCA btl: sm (MCA v1.0, API v1.0.1, Component v1.2.7)
>  MCA btl: tcp (MCA v1.0, API v1.0.1, Component v1.0)
> MCA topo: unity (MCA v1.0, API v1.0, Component v1.2.7)
>  MCA osc: pt2pt (MCA v1.0, API v1.0, Component v1.2.7)
>   MCA errmgr: hnp (MCA v1.0, API v1.3, Component v1.2.7)
>   MCA errmgr: orted (MCA v1.0, API v1.3, Component v1.2.7)
>   MCA errmgr: proxy (MCA v1.0, API v1.3, Component v1.2.7)
>  MCA gpr: null (MCA v1.0, API v1.0, Component v1.2.7)
>  MCA gpr: proxy (MCA v1.0, API v1.0, Component v1.2.7)
> 

[OMPI users] MPI-IO Lustre driver update?

[Mark Dixon]

Hi,

I notice that there's been quite a bit of work recently on ROMIO's Lustre 
driver. As far as I can see from openmpi's SVN, this doesn't seem to have 
landed there yet (README indicates V04, yet V05 is in MPICH2 and 
MVAPICH2).


Is there a timescale for when this will be make it into a release, please?

Thanks,

Mark
--
-
Mark Dixon   Email: m.c.di...@leeds.ac.uk
HPC/Grid Systems Support Tel (int): 35429
Information Systems Services Tel (ext): +44(0)113 343 5429
University of Leeds, LS2 9JT, UK
-

Re: [OMPI users] cannot build Open MPI 1.5 on Linux x86_64 with Oracle/Sun C 5.11

[Terry Dontje]

This is ticket 2632 https://svn.open-mpi.org/trac/ompi/ticket/2632.  A 
fix has been put into the trunk last week.  We should be able to CMR 
this fix to the 1.5 and 1.4 branches later this week.The ticket 
actually has a workaround for 1.5 branch.


--td
On 11/29/2010 09:46 AM, Siegmar Gross wrote:

Hi,

in the meantime we have installed gcc-4.5.1 and now I get a different error,
when I try to build OpenMPI-1.5 with Oracle Studio 12 Update 2 on Linux.

linpc4 openmpi-1.5-Linux.x86_64.32_cc_gcc-4.5.1 121 head -18 config.log
...
   $ ../openmpi-1.5/configure --prefix=/usr/local/openmpi-1.5_32_cc
LDFLAGS=-m32 CC=cc CXX=CC F77=f77 FC=f95 CFLAGS=-m32 CXXFLAGS=-m32
FFLAGS=-m32 FCFLAGS=-m32 CXXLDFLAGS=-m32 CPPFLAGS= C_INCL_PATH=
C_INCLUDE_PATH= CPLUS_INCLUDE_PATH= OBJC_INCLUDE_PATH= MPICHHOME=
--without-udapl --without-openib --enable-mpi-f90
--with-mpi-f90-size=small --enable-heterogeneous
--enable-cxx-exceptions --enable-shared
--enable-orterun-prefix-by-default --with-threads=posix
--enable-mpi-threads --disable-progress-threads

## - ##
## Platform. ##
## - ##

hostname = linpc4
uname -m = x86_64
uname -r = 2.6.31.14-0.4-desktop
uname -s = Linux
uname -v = #1 SMP PREEMPT 2010-10-25 08:45:30 +0200



linpc4 openmpi-1.5-Linux.x86_64.32_cc_gcc-4.5.1 122 tail -20
   log.make.Linux.x86_64.32_cc
../../../../openmpi-1.5/ompi/mpi/f90/scripts/mpi_wtick_f90.f90.sh
/export2/src/openmpi-1.5/openmpi-1.5-Linux.x86_64.32_cc_gcc-4.5.1/ompi/mpi/f90>
mpi_wtick_f90.f90
   FC mpi_wtick_f90.lo
../../../../openmpi-1.5/ompi/mpi/f90/scripts/mpi_wtime_f90.f90.sh
/export2/src/openmpi-1.5/openmpi-1.5-Linux.x86_64.32_cc_gcc-4.5.1/ompi/mpi/f90>
mpi_wtime_f90.f90
   FC mpi_wtime_f90.lo
   FCLD   libmpi_f90.la
f90: Warning: Option -path passed to ld, if ld is invoked, ignored otherwise
f90: Warning: Option -path passed to ld, if ld is invoked, ignored otherwise
f90: Warning: Option -path passed to ld, if ld is invoked, ignored otherwise
f90: Warning: Option -soname passed to ld, if ld is invoked, ignored otherwise
/usr/bin/ld: unrecognized option '-path'
/usr/bin/ld: use the --help option for usage information
make[4]: *** [libmpi_f90.la] Error 2
make[4]: Leaving directory
`/export2/src/openmpi-1.5/openmpi-1.5-Linux.x86_64.32_cc_gcc-4.5.1/ompi/mpi/f90'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/export2/src/openmpi-1.5/openmpi-1.5-Linux.x86_64.32_cc_gcc-4.5.1/ompi/mpi/f90'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/export2/src/openmpi-1.5/openmpi-1.5-Linux.x86_64.32_cc_gcc-4.5.1/ompi/mpi/f90'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/export2/src/openmpi-1.5/openmpi-1.5-Linux.x86_64.32_cc_gcc-4.5.1/ompi'
make: *** [all-recursive] Error 1
linpc4 openmpi-1.5-Linux.x86_64.32_cc_gcc-4.5.1 123


In my opinion it is still a strange behaviour that building OpenMPI with
"cc" depends on the installed version of "gcc". Has anybody successfully
build OpenMPI-1.5 with Oracle Studio C on Linux? Which command line
options did you use? I get the same error if I try to build a 64-bit
version. I can build and install OpenMPI-1.5 in a 32- and 64-bit version
without Fortran support, if I replace
"--enable-mpi-f90 --with-mpi-f90-size=small" with
"--disable-mpi-f77 --disable-mpi-f90" in the above "configure"-command.

"make check" delivers "PASSED" for all tests in the 64-bit and one
"FAILED" in the 32-bit version.

...
make  check-TESTS
make[3]: Entering directory
`/export2/src/openmpi-1.5/openmpi-1.5-Linux.x86_64.32_cc_gcc-4.5.1_without_f90/te
st/util'
  Failure : Mismatch: input "/home/fd1026", expected:1 got:0

SUPPORT: OMPI Test failed: opal_path_nfs() (1 of 13 failed)
FAIL: opal_path_nfs

1 of 1 test failed
Please report to http://www.open-mpi.org/community/help/

make[3]: *** [check-TESTS] Error 1
make[3]: Leaving directory
`/export2/src/openmpi-1.5/openmpi-1.5-Linux.x86_64.32_cc_gc
c-4.5.1_without_f90/test/util'
make[2]: *** [check-am] Error 2
make[2]: Leaving directory
`/export2/src/openmpi-1.5/openmpi-1.5-Linux.x86_64.32_cc_gc
c-4.5.1_without_f90/test/util'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory
`/export2/src/openmpi-1.5/openmpi-1.5-Linux.x86_64.32_cc_gc
c-4.5.1_without_f90/test'
make: *** [check-recursive] Error 1
linpc4 openmpi-1.5-Linux.x86_64.32_cc_gcc-4.5.1_without_f90 131



I can also successfully build and run my small C test programs which I
mentioned in my earlier email with this OpenMPI package. Any ideas how
I can build Fortran support? Thank you very much for any suggestions in
advance.


Kind regards

Siegmar



   Sorry, but can you give us the config line, the config.log and the
full output of make preferrably with make V=1?

--td
On 10/29/2010 04:30 AM, Siegmar Gross wrote:

Hi,

I tried to build Open MPI 1.5 on Solaris X86 and x86_64 with Oracle
Studio 12.2. I can compile Open 

[OMPI users] cannot build Open MPI 1.5 on Linux x86_64 with Oracle/Sun C 5.11

[Siegmar Gross]

Hi,

in the meantime we have installed gcc-4.5.1 and now I get a different error,
when I try to build OpenMPI-1.5 with Oracle Studio 12 Update 2 on Linux.

linpc4 openmpi-1.5-Linux.x86_64.32_cc_gcc-4.5.1 121 head -18 config.log
...
  $ ../openmpi-1.5/configure --prefix=/usr/local/openmpi-1.5_32_cc
   LDFLAGS=-m32 CC=cc CXX=CC F77=f77 FC=f95 CFLAGS=-m32 CXXFLAGS=-m32
   FFLAGS=-m32 FCFLAGS=-m32 CXXLDFLAGS=-m32 CPPFLAGS= C_INCL_PATH=
   C_INCLUDE_PATH= CPLUS_INCLUDE_PATH= OBJC_INCLUDE_PATH= MPICHHOME=
   --without-udapl --without-openib --enable-mpi-f90
   --with-mpi-f90-size=small --enable-heterogeneous
   --enable-cxx-exceptions --enable-shared
   --enable-orterun-prefix-by-default --with-threads=posix
   --enable-mpi-threads --disable-progress-threads

## - ##
## Platform. ##
## - ##

hostname = linpc4
uname -m = x86_64
uname -r = 2.6.31.14-0.4-desktop
uname -s = Linux
uname -v = #1 SMP PREEMPT 2010-10-25 08:45:30 +0200



linpc4 openmpi-1.5-Linux.x86_64.32_cc_gcc-4.5.1 122 tail -20
  log.make.Linux.x86_64.32_cc
../../../../openmpi-1.5/ompi/mpi/f90/scripts/mpi_wtick_f90.f90.sh 
/export2/src/openmpi-1.5/openmpi-1.5-Linux.x86_64.32_cc_gcc-4.5.1/ompi/mpi/f90 
> 
mpi_wtick_f90.f90
  FC mpi_wtick_f90.lo
../../../../openmpi-1.5/ompi/mpi/f90/scripts/mpi_wtime_f90.f90.sh 
/export2/src/openmpi-1.5/openmpi-1.5-Linux.x86_64.32_cc_gcc-4.5.1/ompi/mpi/f90 
> 
mpi_wtime_f90.f90
  FC mpi_wtime_f90.lo
  FCLD   libmpi_f90.la
f90: Warning: Option -path passed to ld, if ld is invoked, ignored otherwise
f90: Warning: Option -path passed to ld, if ld is invoked, ignored otherwise
f90: Warning: Option -path passed to ld, if ld is invoked, ignored otherwise
f90: Warning: Option -soname passed to ld, if ld is invoked, ignored otherwise
/usr/bin/ld: unrecognized option '-path'
/usr/bin/ld: use the --help option for usage information
make[4]: *** [libmpi_f90.la] Error 2
make[4]: Leaving directory 
`/export2/src/openmpi-1.5/openmpi-1.5-Linux.x86_64.32_cc_gcc-4.5.1/ompi/mpi/f90'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory 
`/export2/src/openmpi-1.5/openmpi-1.5-Linux.x86_64.32_cc_gcc-4.5.1/ompi/mpi/f90'
make[2]: *** [all] Error 2
make[2]: Leaving directory 
`/export2/src/openmpi-1.5/openmpi-1.5-Linux.x86_64.32_cc_gcc-4.5.1/ompi/mpi/f90'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory 
`/export2/src/openmpi-1.5/openmpi-1.5-Linux.x86_64.32_cc_gcc-4.5.1/ompi'
make: *** [all-recursive] Error 1
linpc4 openmpi-1.5-Linux.x86_64.32_cc_gcc-4.5.1 123 


In my opinion it is still a strange behaviour that building OpenMPI with
"cc" depends on the installed version of "gcc". Has anybody successfully
build OpenMPI-1.5 with Oracle Studio C on Linux? Which command line
options did you use? I get the same error if I try to build a 64-bit
version. I can build and install OpenMPI-1.5 in a 32- and 64-bit version
without Fortran support, if I replace
"--enable-mpi-f90 --with-mpi-f90-size=small" with
"--disable-mpi-f77 --disable-mpi-f90" in the above "configure"-command.

"make check" delivers "PASSED" for all tests in the 64-bit and one
"FAILED" in the 32-bit version.

...
make  check-TESTS
make[3]: Entering directory 
`/export2/src/openmpi-1.5/openmpi-1.5-Linux.x86_64.32_cc_gcc-4.5.1_without_f90/te
st/util'
 Failure : Mismatch: input "/home/fd1026", expected:1 got:0

SUPPORT: OMPI Test failed: opal_path_nfs() (1 of 13 failed)
FAIL: opal_path_nfs

1 of 1 test failed
Please report to http://www.open-mpi.org/community/help/

make[3]: *** [check-TESTS] Error 1
make[3]: Leaving directory 
`/export2/src/openmpi-1.5/openmpi-1.5-Linux.x86_64.32_cc_gc
c-4.5.1_without_f90/test/util'
make[2]: *** [check-am] Error 2
make[2]: Leaving directory 
`/export2/src/openmpi-1.5/openmpi-1.5-Linux.x86_64.32_cc_gc
c-4.5.1_without_f90/test/util'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory 
`/export2/src/openmpi-1.5/openmpi-1.5-Linux.x86_64.32_cc_gc
c-4.5.1_without_f90/test'
make: *** [check-recursive] Error 1
linpc4 openmpi-1.5-Linux.x86_64.32_cc_gcc-4.5.1_without_f90 131 



I can also successfully build and run my small C test programs which I
mentioned in my earlier email with this OpenMPI package. Any ideas how
I can build Fortran support? Thank you very much for any suggestions in
advance.


Kind regards

Siegmar


> >   Sorry, but can you give us the config line, the config.log and the 
> > full output of make preferrably with make V=1?
> > 
> > --td
> > On 10/29/2010 04:30 AM, Siegmar Gross wrote:
> > > Hi,
> > >
> > > I tried to build Open MPI 1.5 on Solaris X86 and x86_64 with Oracle
> > > Studio 12.2. I can compile Open MPI with thread support, but I can
> > > only partly install it because "libtool" will not find "f95" although
> > > it is available. "make check" shows no failures.
> 
> I made a mistake the first time. I'm sorry for that. This weekend I
> rebuild everything 

Re: [OMPI users] PROBLEM WITH MPIRUN

[Tushar Andriyas]

and the openmpi-1.2.7-pgi??

On Mon, Nov 29, 2010 at 6:27 AM, Tushar Andriyas wrote:

> Hi there,
> The thing is I did not write the code myself and am just trying to get it
> to work. So, would it help if i change the version of the compiler or is
> that it happens with every pgi compiler suite??
>
>
> On Sun, Nov 28, 2010 at 11:45 PM, Simon Hammond 
> wrote:
>
>> Hi,
>>
>> This isn't usually an error - you get this by using conventional
>> Fortran exit methods. The Fortran stop means the program hit the exit
>> statements in the code. I have only had this with PGI.
>>
>>
>>
>>
>> --
>> Si Hammond
>>
>> Research Fellow & Knowledge Transfer Associate
>> Performance Computing & Visualisation
>> Department of Computer Science
>> University of Warwick, UK, CV4 7AL
>>
>> --
>>
>>
>>
>> On 29 November 2010 04:56, Tushar Andriyas 
>> wrote:
>> > Hi there,
>> > I have posted before about the problems that I am facing with mpirun. I
>> have
>> > gotten some help but right now i am stuck with an error
>> message.FORTRAN
>> > STOP when I invoke mpirun..can someone help PLEASE!!
>> > I m using openmpi-1.2.7-pgi and pgi-7.2 compiler.
>> > ___
>> > users mailing list
>> > us...@open-mpi.org
>> > http://www.open-mpi.org/mailman/listinfo.cgi/users
>> >
>> ___
>> users mailing list
>> us...@open-mpi.org
>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>>
>
>

Re: [OMPI users] PROBLEM WITH MPIRUN

[Tushar Andriyas]

Hi there,
The thing is I did not write the code myself and am just trying to get it to
work. So, would it help if i change the version of the compiler or is that
it happens with every pgi compiler suite??

On Sun, Nov 28, 2010 at 11:45 PM, Simon Hammond wrote:

> Hi,
>
> This isn't usually an error - you get this by using conventional
> Fortran exit methods. The Fortran stop means the program hit the exit
> statements in the code. I have only had this with PGI.
>
>
>
>
> --
> Si Hammond
>
> Research Fellow & Knowledge Transfer Associate
> Performance Computing & Visualisation
> Department of Computer Science
> University of Warwick, UK, CV4 7AL
>
> --
>
>
>
> On 29 November 2010 04:56, Tushar Andriyas  wrote:
> > Hi there,
> > I have posted before about the problems that I am facing with mpirun. I
> have
> > gotten some help but right now i am stuck with an error
> message.FORTRAN
> > STOP when I invoke mpirun..can someone help PLEASE!!
> > I m using openmpi-1.2.7-pgi and pgi-7.2 compiler.
> > ___
> > users mailing list
> > us...@open-mpi.org
> > http://www.open-mpi.org/mailman/listinfo.cgi/users
> >
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
>

Re: [OMPI users] PROBLEM WITH MPIRUN

[Simon Hammond]

Hi,

This isn't usually an error - you get this by using conventional
Fortran exit methods. The Fortran stop means the program hit the exit
statements in the code. I have only had this with PGI.



--
Si Hammond

Research Fellow & Knowledge Transfer Associate
Performance Computing & Visualisation
Department of Computer Science
University of Warwick, UK, CV4 7AL
--



On 29 November 2010 04:56, Tushar Andriyas  wrote:
> Hi there,
> I have posted before about the problems that I am facing with mpirun. I have
> gotten some help but right now i am stuck with an error message.FORTRAN
> STOP when I invoke mpirun..can someone help PLEASE!!
> I m using openmpi-1.2.7-pgi and pgi-7.2 compiler.
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
>