subject:"\[OMPI users\] OpenMPI \- compilation"

Re: [OMPI users] Openmpi compilation errors

2015-05-30 Thread Timothy Brown

> On May 30, 2015, at 4:34 AM, Jeff Squyres (jsquyres)  
> wrote:
> 
> On May 29, 2015, at 11:19 AM, Timothy Brown  
> wrote:
>> 
>> I've built Openmpi 1.8.5 with the following configure line:
>> 
>> ./configure  \
>> --prefix=/curc/tools/x86_64/rh6/software/openmpi/1.8.5/pgi/15.3 \
>> --with-threads=posix \
>> --enable-mpi-thread-multiple \
>> --with-slurm \
>> --with-pmi=/curc/slurm/slurm/current/
>> 
>> Please note, I am using the following environment variables:
>> CC=pgcc
>> FC=pgfortran
>> F90=pgf90
>> F77=pgf77
>> CXX=pgc++
> 
> Sweet -- thanks for the info, Tim.
> 
> One extremely minor tweak that I would recommend is to do this, instead:
> 
> ./configure  \
> CC=pgcc \
> FC=pgfortran \
> F90=pgf90 \
> F77=pgf77 \
> CXX=pgc++ \
> --prefix=/curc/tools/x86_64/rh6/software/openmpi/1.8.5/pgi/15.3 \
> --with-threads=posix \
> --enable-mpi-thread-multiple \
> --with-slurm \
> --with-pmi=/curc/slurm/slurm/current/
> 
> I.e., set those environment variables on the configure command line instead 
> of having them in your environment.
> 
> The end effect is exactly the same -- the only difference is that these 
> environment variables will be explicitly listed right at the top in the 
> config.log file that is generated when you run configure.  It's a very minor 
> thing -- just for helping your future self when remembering exactly how your 
> copy of Open MPI was built.

Hi Jeff,

Yes, I have often gone back to a build and tried to figure out how it was 
actually built. We're investigating using EasyBuild ( 
https://github.com/hpcugent/easybuild ) however we haven't taken the plunge yet.

We do use Lmod ( https://github.com/TACC/Lmod ) and so I have modules loaded 
into our environment.

All this being said, I wrote a quick and dirty script that logs the modules 
loaded and the configure line from the config.log to a DB. The script also 
queries the DB and can produce the configure command (including module loads) 
and update the prefix based upon the source directory your in (it only does 
this for patch version updates only (i.e 1.8.4 -> 1.8.5), I decided anything 
larger than this you really should read the docs/configure options to see if 
your doing things correctly). It's an ugly script that I'm not proud of but it 
works!

Regards
Tim

Re: [OMPI users] Openmpi compilation errors

2015-05-30 Thread Jeff Squyres (jsquyres)

On May 29, 2015, at 11:19 AM, Timothy Brown  
wrote:
> 
> I've built Openmpi 1.8.5 with the following configure line:
> 
> ./configure  \
>  --prefix=/curc/tools/x86_64/rh6/software/openmpi/1.8.5/pgi/15.3 \
>  --with-threads=posix \
>  --enable-mpi-thread-multiple \
>  --with-slurm \
>  --with-pmi=/curc/slurm/slurm/current/
> 
> Please note, I am using the following environment variables:
> CC=pgcc
> FC=pgfortran
> F90=pgf90
> F77=pgf77
> CXX=pgc++

Sweet -- thanks for the info, Tim.

One extremely minor tweak that I would recommend is to do this, instead:

./configure  \
 CC=pgcc \
 FC=pgfortran \
 F90=pgf90 \
 F77=pgf77 \
 CXX=pgc++ \
 --prefix=/curc/tools/x86_64/rh6/software/openmpi/1.8.5/pgi/15.3 \
 --with-threads=posix \
 --enable-mpi-thread-multiple \
 --with-slurm \
 --with-pmi=/curc/slurm/slurm/current/

I.e., set those environment variables on the configure command line instead of 
having them in your environment.

The end effect is exactly the same -- the only difference is that these 
environment variables will be explicitly listed right at the top in the 
config.log file that is generated when you run configure.  It's a very minor 
thing -- just for helping your future self when remembering exactly how your 
copy of Open MPI was built.

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

Re: [OMPI users] Openmpi compilation errors

2015-05-29 Thread Timothy Brown


> On May 29, 2015, at 5:07 AM, Jeff Squyres (jsquyres)  
> wrote:
> 
> On May 29, 2015, at 6:54 AM, Bruno Queiros  wrote:
> 
>> The name of the binary is correct: pgf90 the name of the file is also 
>> correct .pgf90.rc i do have some doubts about the content of the file. Is 
>> this enough?
>> 
>> switch -pthread is replace(-lpthread) positional(linker)
> 
> I'm not a Portland customer -- I don't know.  You'll need to check their 
> documentation.
> 

Here I have a siterc file within the PGI bin directory, for example:

/some/long/path/pgi/15.3/bin/siterc

I have exactly the same line as you have specified. 

If you are unable to put it in the PGI installation bin directory you can put 
it in a file ${HOME}/.mypgf90rc, as is described in section 1.8.2 (page 14) of 
the PGI Compilers Users Guide ( http://www.pgroup.com/doc/pgiug.pdf ).
 

>> If i do a source .pgf90.rc i do get errors:
>> 
>> -bash: ./.pgf90.rc: line 1: syntax error near unexpected token `('
>> -bash: ./.pgf90.rc: line 1: `switch -pthread is replace(-lpthread) 
>> positional(linker)'
> 
> I'm guessing that this file is not intended to be sourced by the shell, but 
> rather noticed and read/used by the pgf90 compiler when it is invoked.
> 

Jeff, your right. It's not for your shell to source it'd for the compiler to 
read.


> Sidenote: isn't there a pgfortran compiler executable that is supposed to be 
> preferred over "pgf90" these days?  (remember my disclaimer: I'm not a 
> Portland customer, so I could be totally off base here...)  Have you tried 
> pgfortran to see if it accepts the -pthread option?  Sometimes the different 
> compiler executable entry points behave slightly differently...
> 

I've built Openmpi 1.8.5 with the following configure line:

./configure  \
  --prefix=/curc/tools/x86_64/rh6/software/openmpi/1.8.5/pgi/15.3 \
  --with-threads=posix \
  --enable-mpi-thread-multiple \
  --with-slurm \
  --with-pmi=/curc/slurm/slurm/current/

Please note, I am using the following environment variables:
CC=pgcc
FC=pgfortran
F90=pgf90
F77=pgf77
CXX=pgc++

I do not use pgprepro for CPP as I found it to be flaky.

Hope this helps.
Timothy

Re: [OMPI users] Openmpi compilation errors

2015-05-29 Thread Bruno Queiros

Luis

Can you point me to that documentation you're reading?

Em sex, 29 de mai de 2015 às 13:04, Luis Kornblueh <
luis.kornbl...@mpimet.mpg.de> escreveu:

> Hi,
>
> Bruno is using 10.4 as I ready only a second ago in one of his emails. I
> have no idea if the compiler resource file trick works with this old one.
>
> By the way it has to be .mypgf90rc not .pgf90rc at least following the
> current documentation.
>
> Cheerio,
> Luis
>
> On 29/05/15 13:07, Jeff Squyres (jsquyres) wrote:
> > On May 29, 2015, at 6:54 AM, Bruno Queiros  wrote:
> >>
> >> I understand that using Portland compiler isn't "advised" by Open Mpi,
> i was just wondering if there's a way of doing it, since i need Open Mpi
> compiled with PG fortran and not gfortran for example.
> >
> > A further clarification: the Portland compiler is a fine compiler; we
> certainly support it.  The only thing we recommend is avoiding mixing
> compiler suites whenever possible (e.g., using one compiler for C and
> another for Fortran).  It leads to complications like this.
> >
> > That being said, it looks like you have a Portland Fortran license, and
> no corresponding Portland C license, and therefore you're somewhat forced
> into this situation.
> >
> >> The name of the binary is correct: pgf90 the name of the file is also
> correct .pgf90.rc i do have some doubts about the content of the file. Is
> this enough?
> >>
> >> switch -pthread is replace(-lpthread) positional(linker)
> >
> > I'm not a Portland customer -- I don't know.  You'll need to check their
> documentation.
> >
> >> If i do a source .pgf90.rc i do get errors:
> >>
> >> -bash: ./.pgf90.rc: line 1: syntax error near unexpected token `('
> >> -bash: ./.pgf90.rc: line 1: `switch -pthread is replace(-lpthread)
> positional(linker)'
> >
> > I'm guessing that this file is not intended to be sourced by the shell,
> but rather noticed and read/used by the pgf90 compiler when it is invoked.
> >
> > Sidenote: isn't there a pgfortran compiler executable that is supposed
> to be preferred over "pgf90" these days?  (remember my disclaimer: I'm not
> a Portland customer, so I could be totally off base here...)  Have you
> tried pgfortran to see if it accepts the -pthread option?  Sometimes the
> different compiler executable entry points behave slightly differently...
> >
> >> Besides that i tried what you mentioned: pgf90 -pthread somefile.f90 ,
> and that gives the expected error:
> >>
> >> pgf90 -pthread helloworld.f90
> >> pgf90-Error-Unknown switch: -pthread
> >
> > Sounds like this file is somehow not yet correct, or you have a version
> of the Portland compiler that does not use this config file.  You should
> check the Portland Fortran compiler documentation.
> >
> > If you can't get this Portland config file workaround to work, you can
> also make your own "my_fortran_compiler" script that simply strips out the
> -pthread argv token and then invokes pgf90 (or pgfortran) with the rest of
> the argv.  Then you can:
> >
> > ./configure FC=my_fortran_compiler ...
> >
> > I.e., you're just intercepting Open MPI's invocation of the Fortran
> compiler, removing the CLI option that pgf90(pgfortran) won't understand,
> and then invoking pgf90(pgfortran).  Make sense?
> >
> >> My real question is, can i change Open Mpi configuration, to not use
> -pthread flag on fortran compiler?
> >
> > I'm sorry, no -- Open MPI requires threading support.
> >
> ___
> users mailing list
> us...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
> Link to this post:
> http://www.open-mpi.org/community/lists/users/2015/05/26975.php
>

Re: [OMPI users] Openmpi compilation errors

2015-05-29 Thread Bruno Queiros

Thank you Jeff for the clarification and help.

Em sex, 29 de mai de 2015 às 12:08, Jeff Squyres (jsquyres) <
jsquy...@cisco.com> escreveu:

> On May 29, 2015, at 6:54 AM, Bruno Queiros  wrote:
> >
> > I understand that using Portland compiler isn't "advised" by Open Mpi, i
> was just wondering if there's a way of doing it, since i need Open Mpi
> compiled with PG fortran and not gfortran for example.
>
> A further clarification: the Portland compiler is a fine compiler; we
> certainly support it.  The only thing we recommend is avoiding mixing
> compiler suites whenever possible (e.g., using one compiler for C and
> another for Fortran).  It leads to complications like this.
>
> That being said, it looks like you have a Portland Fortran license, and no
> corresponding Portland C license, and therefore you're somewhat forced into
> this situation.
>
> > The name of the binary is correct: pgf90 the name of the file is also
> correct .pgf90.rc i do have some doubts about the content of the file. Is
> this enough?
> >
> > switch -pthread is replace(-lpthread) positional(linker)
>
> I'm not a Portland customer -- I don't know.  You'll need to check their
> documentation.
>
> > If i do a source .pgf90.rc i do get errors:
> >
> > -bash: ./.pgf90.rc: line 1: syntax error near unexpected token `('
> > -bash: ./.pgf90.rc: line 1: `switch -pthread is replace(-lpthread)
> positional(linker)'
>
> I'm guessing that this file is not intended to be sourced by the shell,
> but rather noticed and read/used by the pgf90 compiler when it is invoked.
>
> Sidenote: isn't there a pgfortran compiler executable that is supposed to
> be preferred over "pgf90" these days?  (remember my disclaimer: I'm not a
> Portland customer, so I could be totally off base here...)  Have you tried
> pgfortran to see if it accepts the -pthread option?  Sometimes the
> different compiler executable entry points behave slightly differently...
>
> > Besides that i tried what you mentioned: pgf90 -pthread somefile.f90 ,
> and that gives the expected error:
> >
> > pgf90 -pthread helloworld.f90
> > pgf90-Error-Unknown switch: -pthread
>
> Sounds like this file is somehow not yet correct, or you have a version of
> the Portland compiler that does not use this config file.  You should check
> the Portland Fortran compiler documentation.
>
> If you can't get this Portland config file workaround to work, you can
> also make your own "my_fortran_compiler" script that simply strips out the
> -pthread argv token and then invokes pgf90 (or pgfortran) with the rest of
> the argv.  Then you can:
>
> ./configure FC=my_fortran_compiler ...
>
> I.e., you're just intercepting Open MPI's invocation of the Fortran
> compiler, removing the CLI option that pgf90(pgfortran) won't understand,
> and then invoking pgf90(pgfortran).  Make sense?
>
> > My real question is, can i change Open Mpi configuration, to not use
> -pthread flag on fortran compiler?
>
> I'm sorry, no -- Open MPI requires threading support.
>
> --
> 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
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
> Link to this post:
> http://www.open-mpi.org/community/lists/users/2015/05/26974.php
>

Re: [OMPI users] Openmpi compilation errors

2015-05-29 Thread Luis Kornblueh


Hi,

Bruno is using 10.4 as I ready only a second ago in one of his emails. I 
have no idea if the compiler resource file trick works with this old one.


By the way it has to be .mypgf90rc not .pgf90rc at least following the 
current documentation.


Cheerio,
Luis

On 29/05/15 13:07, Jeff Squyres (jsquyres) wrote:

On May 29, 2015, at 6:54 AM, Bruno Queiros  wrote:


I understand that using Portland compiler isn't "advised" by Open Mpi, i was 
just wondering if there's a way of doing it, since i need Open Mpi compiled with PG 
fortran and not gfortran for example.


A further clarification: the Portland compiler is a fine compiler; we certainly 
support it.  The only thing we recommend is avoiding mixing compiler suites 
whenever possible (e.g., using one compiler for C and another for Fortran).  It 
leads to complications like this.

That being said, it looks like you have a Portland Fortran license, and no 
corresponding Portland C license, and therefore you're somewhat forced into 
this situation.


The name of the binary is correct: pgf90 the name of the file is also correct 
.pgf90.rc i do have some doubts about the content of the file. Is this enough?

switch -pthread is replace(-lpthread) positional(linker)


I'm not a Portland customer -- I don't know.  You'll need to check their 
documentation.


If i do a source .pgf90.rc i do get errors:

-bash: ./.pgf90.rc: line 1: syntax error near unexpected token `('
-bash: ./.pgf90.rc: line 1: `switch -pthread is replace(-lpthread) 
positional(linker)'


I'm guessing that this file is not intended to be sourced by the shell, but 
rather noticed and read/used by the pgf90 compiler when it is invoked.

Sidenote: isn't there a pgfortran compiler executable that is supposed to be preferred 
over "pgf90" these days?  (remember my disclaimer: I'm not a Portland customer, 
so I could be totally off base here...)  Have you tried pgfortran to see if it accepts 
the -pthread option?  Sometimes the different compiler executable entry points behave 
slightly differently...


Besides that i tried what you mentioned: pgf90 -pthread somefile.f90 , and that 
gives the expected error:

pgf90 -pthread helloworld.f90
pgf90-Error-Unknown switch: -pthread


Sounds like this file is somehow not yet correct, or you have a version of the 
Portland compiler that does not use this config file.  You should check the 
Portland Fortran compiler documentation.

If you can't get this Portland config file workaround to work, you can also make your own 
"my_fortran_compiler" script that simply strips out the -pthread argv token and 
then invokes pgf90 (or pgfortran) with the rest of the argv.  Then you can:

./configure FC=my_fortran_compiler ...

I.e., you're just intercepting Open MPI's invocation of the Fortran compiler, 
removing the CLI option that pgf90(pgfortran) won't understand, and then 
invoking pgf90(pgfortran).  Make sense?


My real question is, can i change Open Mpi configuration, to not use -pthread 
flag on fortran compiler?


I'm sorry, no -- Open MPI requires threading support.

Re: [OMPI users] Openmpi compilation errors

2015-05-29 Thread Jeff Squyres (jsquyres)

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

A further clarification: the Portland compiler is a fine compiler; we certainly 
support it.  The only thing we recommend is avoiding mixing compiler suites 
whenever possible (e.g., using one compiler for C and another for Fortran).  It 
leads to complications like this.

That being said, it looks like you have a Portland Fortran license, and no 
corresponding Portland C license, and therefore you're somewhat forced into 
this situation.

> The name of the binary is correct: pgf90 the name of the file is also correct 
> .pgf90.rc i do have some doubts about the content of the file. Is this enough?
> 
> switch -pthread is replace(-lpthread) positional(linker)

I'm not a Portland customer -- I don't know.  You'll need to check their 
documentation.

> If i do a source .pgf90.rc i do get errors:
> 
> -bash: ./.pgf90.rc: line 1: syntax error near unexpected token `('
> -bash: ./.pgf90.rc: line 1: `switch -pthread is replace(-lpthread) 
> positional(linker)'

I'm guessing that this file is not intended to be sourced by the shell, but 
rather noticed and read/used by the pgf90 compiler when it is invoked.

Sidenote: isn't there a pgfortran compiler executable that is supposed to be 
preferred over "pgf90" these days?  (remember my disclaimer: I'm not a Portland 
customer, so I could be totally off base here...)  Have you tried pgfortran to 
see if it accepts the -pthread option?  Sometimes the different compiler 
executable entry points behave slightly differently...

> Besides that i tried what you mentioned: pgf90 -pthread somefile.f90 , and 
> that gives the expected error:
> 
> pgf90 -pthread helloworld.f90 
> pgf90-Error-Unknown switch: -pthread

Sounds like this file is somehow not yet correct, or you have a version of the 
Portland compiler that does not use this config file.  You should check the 
Portland Fortran compiler documentation.

If you can't get this Portland config file workaround to work, you can also 
make your own "my_fortran_compiler" script that simply strips out the -pthread 
argv token and then invokes pgf90 (or pgfortran) with the rest of the argv.  
Then you can:

./configure FC=my_fortran_compiler ...

I.e., you're just intercepting Open MPI's invocation of the Fortran compiler, 
removing the CLI option that pgf90(pgfortran) won't understand, and then 
invoking pgf90(pgfortran).  Make sense?

> My real question is, can i change Open Mpi configuration, to not use -pthread 
> flag on fortran compiler?

I'm sorry, no -- Open MPI requires threading support.

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

Re: [OMPI users] Openmpi compilation errors

2015-05-29 Thread Bruno Queiros

Hello Jeff

I understand that using Portland compiler isn't "advised" by Open Mpi, i
was just wondering if there's a way of doing it, since i need Open Mpi
compiled with PG fortran and not gfortran for example.

The name of the binary is correct: pgf90 the name of the file is also
correct .pgf90.rc i do have some doubts about the content of the file. Is
this enough?

switch -pthread is replace(-lpthread) positional(linker)

If i do a source .pgf90.rc i do get errors:

-bash: ./.pgf90.rc: line 1: syntax error near unexpected token `('
-bash: ./.pgf90.rc: line 1: `switch -pthread is replace(-lpthread)
positional(linker)'

Besides that i tried what you mentioned: pgf90 -pthread somefile.f90 , and
that gives the expected error:

pgf90 -pthread helloworld.f90
pgf90-Error-Unknown switch: -pthread


My real question is, can i change Open Mpi configuration, to not use
-pthread flag on fortran compiler?



Em sex, 29 de mai de 2015 às 11:36, Jeff Squyres (jsquyres) <
jsquy...@cisco.com> escreveu:

> Just to clarify: the underlying issue here is that Open MPI's configure
> script is assuming that whatever linker flags it discovers for the C
> compiler are also valid for the Fortran compiler.  This is apparently not
> true when you mix the GCC and Portland compilers -- bummer (i.e., Open
> MPI's configure script is determining that -pthread works with gcc and
> assumes that it works with pgf90... but it apparently doesn't, which is why
> Luis's solution is particularly clever).
>
> If the portland-config-script-in-your-$HOME solution isn't work, I'd
> double check that you have the file named correctly (e.g., I thought the
> Portland Fortran compiler's name was pgf90, not pfg90 -- I would assume
> that the config filename is representative of the compiler's executable
> name...?), that it is actually being seen by the Portland compiler, etc.
>
> You can easily test whether this Portland config trick is working: just
> invoke "pgf90 -pthread somefile.f90" and see if it compiles that
> somefile.f90 file or if it complains about the -pthread option.  If the
> Portland config trick is working, (assuming somefile.f90 is a valid Fortran
> file), it'll compile without complaining about -pthread. The Open MPI will
> likely be able to build, too.
>
>
> > On May 29, 2015, at 6:14 AM, Bruno Queiros  wrote:
> >
> > Thank you for the help Luis
> >
> > I did as you told me, i created a .pfg90.rc on the home directory of my
> user with:
> >
> > switch -pthread is replace(-lpthread) positional(linker)
> >
> > i tried to compile openmpi with make, but i still got the same error.
> >
> > Am i doing something wrong? How can i overcome this -pthread error?
> >
> >
> > Em qui, 28 de mai de 2015 às 18:36, Luis Kornblueh <
> luis.kornbl...@mpimet.mpg.de> escreveu:
> > Hi Bruno,
> >
> > once more: it might be the case that the file needs to be named .pgf90rc
> >
> > Sorry,
> > Luis
> >
> > On 28/05/15 19:08, Bruno Queiros wrote:
> > > Thomas
> > >
> > > I did get a configure successfull, but make fails with
> > >
> > > pgf90-Error-Unknown switch: -pthread
> > > make[2]: *** [libmpi_usempi.la ] Error 1
> > >
> > > I have tried and did a fake pgf90 has mentioned on the mailing list
> > >
> > > #! /bin/bash
> > > newargs='echo $@ | sed s/-pthread//g -'
> > > #echo "/opt/pgi/linux86-64/10.4/bin/pgf90  $newargs"
> > > /opt/pgi/linux86-64/10.4/bin/pgf90  $newargs
> > > exit
> > >
> > > But for some reason this doesn't work, the make just stops.
> > >
> > > Can you point me in the right direction?
> > >
> > > Em qui, 28 de mai de 2015 às 14:10, Bruno Queiros  > > > escreveu:
> > >
> > > Thank you very much Thomas
> > >
> > > I will try this
> > >
> > > Em qui, 28 de mai de 2015 às 12:25, Thomas Jahns  > > > escreveu:
> > >
> > > On 05/28/15 12:20, Jeff Squyres (jsquyres) wrote:
> > >  > Sounds like your pgcc compiler installation is busted.
> > > You'll need to get that fixed to compile/install Open MPI.
> > >
> > > An alternative might be to use a system compiler (which is
> > > probably gcc or
> > > clang) for C and C++ and only use pgfortran for the Fortran
> > > parts of OpenMPI,
> > > i.e. try something like
> > >
> > > ./configure CC=gcc CXX=g++ FC=pgf90 F77=pgf77 F90=pgf90
> > > --prefix=/opt/openmpi-1.8.5_pgf90
> > >
> > > Regards, Thomas Jahns
> > >
> > >
> > > ___
> > > users mailing list
> > > us...@open-mpi.org 
> > > Subscription:
> http://www.open-mpi.org/mailman/listinfo.cgi/users
> > > Link to this post:
> > >
> http://www.open-mpi.org/community/lists/users/2015/05/26963.php
> > >
> > >
> > >
> > > ___
> > > users mailing list
> > > us...@open-mpi.org
> > > Subscription: http://www.open-mpi.org/mailman/li

Re: [OMPI users] Openmpi compilation errors

2015-05-29 Thread Jeff Squyres (jsquyres)

Just to clarify: the underlying issue here is that Open MPI's configure script 
is assuming that whatever linker flags it discovers for the C compiler are also 
valid for the Fortran compiler.  This is apparently not true when you mix the 
GCC and Portland compilers -- bummer (i.e., Open MPI's configure script is 
determining that -pthread works with gcc and assumes that it works with 
pgf90... but it apparently doesn't, which is why Luis's solution is 
particularly clever).

If the portland-config-script-in-your-$HOME solution isn't work, I'd double 
check that you have the file named correctly (e.g., I thought the Portland 
Fortran compiler's name was pgf90, not pfg90 -- I would assume that the config 
filename is representative of the compiler's executable name...?), that it is 
actually being seen by the Portland compiler, etc.

You can easily test whether this Portland config trick is working: just invoke 
"pgf90 -pthread somefile.f90" and see if it compiles that somefile.f90 file or 
if it complains about the -pthread option.  If the Portland config trick is 
working, (assuming somefile.f90 is a valid Fortran file), it'll compile without 
complaining about -pthread. The Open MPI will likely be able to build, too.

> On May 29, 2015, at 6:14 AM, Bruno Queiros  wrote:
> 
> Thank you for the help Luis
> 
> I did as you told me, i created a .pfg90.rc on the home directory of my user 
> with:
> 
> switch -pthread is replace(-lpthread) positional(linker)
> 
> i tried to compile openmpi with make, but i still got the same error.
> 
> Am i doing something wrong? How can i overcome this -pthread error?
> 
> 
> Em qui, 28 de mai de 2015 às 18:36, Luis Kornblueh 
>  escreveu:
> Hi Bruno,
> 
> once more: it might be the case that the file needs to be named .pgf90rc
> 
> Sorry,
> Luis
> 
> On 28/05/15 19:08, Bruno Queiros wrote:
> > Thomas
> >
> > I did get a configure successfull, but make fails with
> >
> > pgf90-Error-Unknown switch: -pthread
> > make[2]: *** [libmpi_usempi.la ] Error 1
> >
> > I have tried and did a fake pgf90 has mentioned on the mailing list
> >
> > #! /bin/bash
> > newargs='echo $@ | sed s/-pthread//g -'
> > #echo "/opt/pgi/linux86-64/10.4/bin/pgf90  $newargs"
> > /opt/pgi/linux86-64/10.4/bin/pgf90  $newargs
> > exit
> >
> > But for some reason this doesn't work, the make just stops.
> >
> > Can you point me in the right direction?
> >
> > Em qui, 28 de mai de 2015 às 14:10, Bruno Queiros  > > escreveu:
> >
> > Thank you very much Thomas
> >
> > I will try this
> >
> > Em qui, 28 de mai de 2015 às 12:25, Thomas Jahns  > > escreveu:
> >
> > On 05/28/15 12:20, Jeff Squyres (jsquyres) wrote:
> >  > Sounds like your pgcc compiler installation is busted.
> > You'll need to get that fixed to compile/install Open MPI.
> >
> > An alternative might be to use a system compiler (which is
> > probably gcc or
> > clang) for C and C++ and only use pgfortran for the Fortran
> > parts of OpenMPI,
> > i.e. try something like
> >
> > ./configure CC=gcc CXX=g++ FC=pgf90 F77=pgf77 F90=pgf90
> > --prefix=/opt/openmpi-1.8.5_pgf90
> >
> > Regards, Thomas Jahns
> >
> >
> > ___
> > users mailing list
> > us...@open-mpi.org 
> > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
> > Link to this post:
> > http://www.open-mpi.org/community/lists/users/2015/05/26963.php
> >
> >
> >
> > ___
> > users mailing list
> > us...@open-mpi.org
> > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
> > Link to this post: 
> > http://www.open-mpi.org/community/lists/users/2015/05/26967.php
> >
> ___
> users mailing list
> us...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
> Link to this post: 
> http://www.open-mpi.org/community/lists/users/2015/05/26969.php
> ___
> users mailing list
> us...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
> Link to this post: 
> http://www.open-mpi.org/community/lists/users/2015/05/26971.php

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

Re: [OMPI users] Openmpi compilation errors

2015-05-29 Thread Bruno Queiros

Thank you for the help Luis

I did as you told me, i created a .pfg90.rc on the home directory of my
user with:

switch -pthread is replace(-lpthread) positional(linker)

i tried to compile openmpi with make, but i still got the same error.

Am i doing something wrong? How can i overcome this -pthread error?


Em qui, 28 de mai de 2015 às 18:36, Luis Kornblueh <
luis.kornbl...@mpimet.mpg.de> escreveu:

> Hi Bruno,
>
> once more: it might be the case that the file needs to be named .pgf90rc
>
> Sorry,
> Luis
>
> On 28/05/15 19:08, Bruno Queiros wrote:
> > Thomas
> >
> > I did get a configure successfull, but make fails with
> >
> > pgf90-Error-Unknown switch: -pthread
> > make[2]: *** [libmpi_usempi.la ] Error 1
> >
> > I have tried and did a fake pgf90 has mentioned on the mailing list
> >
> > #! /bin/bash
> > newargs='echo $@ | sed s/-pthread//g -'
> > #echo "/opt/pgi/linux86-64/10.4/bin/pgf90  $newargs"
> > /opt/pgi/linux86-64/10.4/bin/pgf90  $newargs
> > exit
> >
> > But for some reason this doesn't work, the make just stops.
> >
> > Can you point me in the right direction?
> >
> > Em qui, 28 de mai de 2015 às 14:10, Bruno Queiros  > > escreveu:
> >
> > Thank you very much Thomas
> >
> > I will try this
> >
> > Em qui, 28 de mai de 2015 às 12:25, Thomas Jahns  > > escreveu:
> >
> > On 05/28/15 12:20, Jeff Squyres (jsquyres) wrote:
> >  > Sounds like your pgcc compiler installation is busted.
> > You'll need to get that fixed to compile/install Open MPI.
> >
> > An alternative might be to use a system compiler (which is
> > probably gcc or
> > clang) for C and C++ and only use pgfortran for the Fortran
> > parts of OpenMPI,
> > i.e. try something like
> >
> > ./configure CC=gcc CXX=g++ FC=pgf90 F77=pgf77 F90=pgf90
> > --prefix=/opt/openmpi-1.8.5_pgf90
> >
> > Regards, Thomas Jahns
> >
> >
> > ___
> > users mailing list
> > us...@open-mpi.org 
> > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
> > Link to this post:
> > http://www.open-mpi.org/community/lists/users/2015/05/26963.php
> >
> >
> >
> > ___
> > users mailing list
> > us...@open-mpi.org
> > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
> > Link to this post:
> http://www.open-mpi.org/community/lists/users/2015/05/26967.php
> >
> ___
> users mailing list
> us...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
> Link to this post:
> http://www.open-mpi.org/community/lists/users/2015/05/26969.php
>

Re: [OMPI users] Openmpi compilation errors

2015-05-28 Thread Luis Kornblueh


Hi Bruno,

once more: it might be the case that the file needs to be named .pgf90rc

Sorry,
Luis

On 28/05/15 19:08, Bruno Queiros wrote:

Thomas

I did get a configure successfull, but make fails with

pgf90-Error-Unknown switch: -pthread
make[2]: *** [libmpi_usempi.la ] Error 1

I have tried and did a fake pgf90 has mentioned on the mailing list

#! /bin/bash
newargs='echo $@ | sed s/-pthread//g -'
#echo "/opt/pgi/linux86-64/10.4/bin/pgf90  $newargs"
/opt/pgi/linux86-64/10.4/bin/pgf90  $newargs
exit

But for some reason this doesn't work, the make just stops.

Can you point me in the right direction?

Em qui, 28 de mai de 2015 às 14:10, Bruno Queiros mailto:bquei...@gmail.com>> escreveu:

Thank you very much Thomas

I will try this

Em qui, 28 de mai de 2015 às 12:25, Thomas Jahns mailto:ja...@dkrz.de>> escreveu:

On 05/28/15 12:20, Jeff Squyres (jsquyres) wrote:
 > Sounds like your pgcc compiler installation is busted.
You'll need to get that fixed to compile/install Open MPI.

An alternative might be to use a system compiler (which is
probably gcc or
clang) for C and C++ and only use pgfortran for the Fortran
parts of OpenMPI,
i.e. try something like

./configure CC=gcc CXX=g++ FC=pgf90 F77=pgf77 F90=pgf90
--prefix=/opt/openmpi-1.8.5_pgf90

Regards, Thomas Jahns


___
users mailing list
us...@open-mpi.org 
Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
Link to this post:
http://www.open-mpi.org/community/lists/users/2015/05/26963.php



___
users mailing list
us...@open-mpi.org
Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
Link to this post: 
http://www.open-mpi.org/community/lists/users/2015/05/26967.php

Re: [OMPI users] Openmpi compilation errors

2015-05-28 Thread Luis Kornblueh


Hi Bruno,
just add a file

$HOME/.mypgfortranrc

with the following contents:

switch -pthread is replace(-lpthread) positional(linker)

That solve your problem.

CHeerio,
Luis


On 28/05/15 19:08, Bruno Queiros wrote:

Thomas

I did get a configure successfull, but make fails with

pgf90-Error-Unknown switch: -pthread
make[2]: *** [libmpi_usempi.la ] Error 1

I have tried and did a fake pgf90 has mentioned on the mailing list

#! /bin/bash
newargs='echo $@ | sed s/-pthread//g -'
#echo "/opt/pgi/linux86-64/10.4/bin/pgf90  $newargs"
/opt/pgi/linux86-64/10.4/bin/pgf90  $newargs
exit

But for some reason this doesn't work, the make just stops.

Can you point me in the right direction?

Em qui, 28 de mai de 2015 às 14:10, Bruno Queiros mailto:bquei...@gmail.com>> escreveu:

Thank you very much Thomas

I will try this

Em qui, 28 de mai de 2015 às 12:25, Thomas Jahns mailto:ja...@dkrz.de>> escreveu:

On 05/28/15 12:20, Jeff Squyres (jsquyres) wrote:
 > Sounds like your pgcc compiler installation is busted.
You'll need to get that fixed to compile/install Open MPI.

An alternative might be to use a system compiler (which is
probably gcc or
clang) for C and C++ and only use pgfortran for the Fortran
parts of OpenMPI,
i.e. try something like

./configure CC=gcc CXX=g++ FC=pgf90 F77=pgf77 F90=pgf90
--prefix=/opt/openmpi-1.8.5_pgf90

Regards, Thomas Jahns


___
users mailing list
us...@open-mpi.org 
Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
Link to this post:
http://www.open-mpi.org/community/lists/users/2015/05/26963.php



___
users mailing list
us...@open-mpi.org
Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
Link to this post: 
http://www.open-mpi.org/community/lists/users/2015/05/26967.php

Re: [OMPI users] Openmpi compilation errors

2015-05-28 Thread Bruno Queiros

Thomas

I did get a configure successfull, but make fails with

pgf90-Error-Unknown switch: -pthread
make[2]: *** [libmpi_usempi.la] Error 1

I have tried and did a fake pgf90 has mentioned on the mailing list

#! /bin/bash
newargs='echo $@ | sed s/-pthread//g -'
#echo "/opt/pgi/linux86-64/10.4/bin/pgf90  $newargs"
/opt/pgi/linux86-64/10.4/bin/pgf90  $newargs
exit

But for some reason this doesn't work, the make just stops.

Can you point me in the right direction?

Em qui, 28 de mai de 2015 às 14:10, Bruno Queiros 
escreveu:

> Thank you very much Thomas
>
> I will try this
>
> Em qui, 28 de mai de 2015 às 12:25, Thomas Jahns  escreveu:
>
>> On 05/28/15 12:20, Jeff Squyres (jsquyres) wrote:
>> > Sounds like your pgcc compiler installation is busted.  You'll need to
>> get that fixed to compile/install Open MPI.
>>
>> An alternative might be to use a system compiler (which is probably gcc or
>> clang) for C and C++ and only use pgfortran for the Fortran parts of
>> OpenMPI,
>> i.e. try something like
>>
>> ./configure CC=gcc CXX=g++ FC=pgf90 F77=pgf77 F90=pgf90
>> --prefix=/opt/openmpi-1.8.5_pgf90
>>
>> Regards, Thomas Jahns
>>
>>
>> ___
>> users mailing list
>> us...@open-mpi.org
>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
>> Link to this post:
>> http://www.open-mpi.org/community/lists/users/2015/05/26963.php
>
>

Re: [OMPI users] Openmpi compilation errors

2015-05-28 Thread Bruno Queiros

Thank you very much Thomas

I will try this

Em qui, 28 de mai de 2015 às 12:25, Thomas Jahns  escreveu:

> On 05/28/15 12:20, Jeff Squyres (jsquyres) wrote:
> > Sounds like your pgcc compiler installation is busted.  You'll need to
> get that fixed to compile/install Open MPI.
>
> An alternative might be to use a system compiler (which is probably gcc or
> clang) for C and C++ and only use pgfortran for the Fortran parts of
> OpenMPI,
> i.e. try something like
>
> ./configure CC=gcc CXX=g++ FC=pgf90 F77=pgf77 F90=pgf90
> --prefix=/opt/openmpi-1.8.5_pgf90
>
> Regards, Thomas Jahns
>
>
> ___
> users mailing list
> us...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
> Link to this post:
> http://www.open-mpi.org/community/lists/users/2015/05/26963.php

Re: [OMPI users] Openmpi compilation errors

2015-05-28 Thread Thomas Jahns


On 05/28/15 12:20, Jeff Squyres (jsquyres) wrote:

Sounds like your pgcc compiler installation is busted.  You'll need to get that 
fixed to compile/install Open MPI.


An alternative might be to use a system compiler (which is probably gcc or 
clang) for C and C++ and only use pgfortran for the Fortran parts of OpenMPI, 
i.e. try something like


./configure CC=gcc CXX=g++ FC=pgf90 F77=pgf77 F90=pgf90 
--prefix=/opt/openmpi-1.8.5_pgf90


Regards, Thomas Jahns




smime.p7s
Description: S/MIME Cryptographic Signature

Re: [OMPI users] Openmpi compilation errors

2015-05-28 Thread Jeff Squyres (jsquyres)

Sounds like your pgcc compiler installation is busted.  You'll need to get that 
fixed to compile/install Open MPI.



> On May 28, 2015, at 5:29 AM, Bruno Queiros  wrote:
> 
> Hello David
> 
> $> pgf90 hello.f90
> 
> Works OK.
> 
> $> pgcc hello.c
> 
> Gives that license error:
> 
> pgi-cc-lin64: LICENSE MANAGER PROBLEM: No such feature exists.
> Feature:   pgi-cc-lin64
> License path:  /opt/pgi/license.dat:
> FLEXnet Licensing error:-5,357
> For further information, refer to the FLEXnet Licensing documentation,
> available at "www.acresso.com".
> 
> 
> $> pgCC hello.cpp
> 
> Gives some weird compilation errors:
> 
> "/opt/pgi/linux86-64/10.4/include/bits/types.h", line 159: error: identifier
>   "__SWBLK_T_TYPE" is undefined
>   __STD_TYPE __SWBLK_T_TYPE __swblk_t;/* Type of a swap block maybe?  
> */
>  ^
> 
> "/usr/include/time.h", line 123: error: identifier "__syscall_slong_t" is
>   undefined
>   __syscall_slong_t tv_nsec;  /* Nanoseconds.  */
>   ^
> 
> 2 errors detected in the compilation of "hello.cpp".
> 
> 
> 
> 
> Em qua, 27 de mai de 2015 às 18:28, David Shrader  
> escreveu:
> Yes, exactly like that. Given your configure line, all of the Portland 
> Group's compilers need to work:
> 
> $> pgf90 hello.f90
> $> pgcc hello.c
> $> pgCC hello.cpp
> 
> What of those commands work for you?
> 
> Thanks,
> David
> 
> 
> On 05/27/2015 11:01 AM, Bruno Queiros wrote:
>> David
>> 
>> Do you mean if Portland Fortran compiler works? Like pgf90 hello.f ?
>> 
>> Bruno
>> 
>> 
>> Em qua, 27 de mai de 2015 às 17:40, David Shrader  
>> escreveu:
>> Looking at the config.log, I see this:
>> 
>> pgi-cc-lin64: LICENSE MANAGER PROBLEM: No such feature exists.
>> Feature:   pgi-cc-lin64
>> 
>> It looks like there is a problem with the PGI license. Does it work with a 
>> regular file (e.g., hello_world)? If it does, how do you get it to work (env 
>> variables, license file, etc.)?
>> 
>> Thanks,
>> David
>> 
>> 
>> On 05/27/2015 10:25 AM, Bruno Queiros wrote:
>>> Hello
>>> 
>>> I'm trying to compile openmpi-1.8.5 with portland fortran 10.4 64bits on a 
>>> CentOS7 64bits.
>>> 
>>> This is the output i get:
>>> 
>>> ./configure CC=pgcc CXX=pgCC FC=pgf90 F77=pgf77 F90=pgf90 
>>> --prefix=/opt/openmpi-1.8.5_pgf90
>>> 
>>> 
>>> == Configuring Open MPI
>>> 
>>> 
>>> *** Startup tests
>>> checking build system type... x86_64-unknown-linux-gnu
>>> checking host system type... x86_64-unknown-linux-gnu
>>> checking target system type... x86_64-unknown-linux-gnu
>>> checking for gcc... pgcc
>>> checking whether the C compiler works... no
>>> configure: error: in `/root/TransferArea/openmpi-1.8.5':
>>> configure: error: C compiler cannot create executables
>>> See `config.log' for more details
>>> 
>>> The config.log goes as an attachment
>>> 
>>> 
>>> ___
>>> users mailing list
>>> 
>>> us...@open-mpi.org
>>> 
>>> Subscription: 
>>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>>> 
>>> Link to this post: 
>>> http://www.open-mpi.org/community/lists/users/2015/05/26954.php
>> 
>> -- 
>> David Shrader
>> HPC-3 High Performance Computer Systems
>> Los Alamos National Lab
>> Email: dshrader  
>> lanl.gov
>> ___
>> users mailing list
>> us...@open-mpi.org
>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
>> Link to this post: 
>> http://www.open-mpi.org/community/lists/users/2015/05/26955.php
>> 
>> 
>> ___
>> users mailing list
>> 
>> us...@open-mpi.org
>> 
>> Subscription: 
>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>> Link to this post: 
>> http://www.open-mpi.org/community/lists/users/2015/05/26957.php
> 
> -- 
> David Shrader
> HPC-3 High Performance Computer Systems
> Los Alamos National Lab
> Email: dshrader  
> lanl.gov
> ___
> users mailing list
> us...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
> Link to this post: 
> http://www.open-mpi.org/community/lists/users/2015/05/26958.php
> ___
> users mailing list
> us...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
> Link to this post: 
> http://www.open-mpi.org/community/lists/users/2015/05/26961.php


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

Re: [OMPI users] Openmpi compilation errors

2015-05-28 Thread Bruno Queiros

Hello David

$> pgf90 hello.f90

Works OK.

$> pgcc hello.c

Gives that license error:

pgi-cc-lin64: LICENSE MANAGER PROBLEM: No such feature exists.
Feature:   pgi-cc-lin64
License path:  /opt/pgi/license.dat:
FLEXnet Licensing error:-5,357
For further information, refer to the FLEXnet Licensing documentation,
available at "www.acresso.com".


$> pgCC hello.cpp

Gives some weird compilation errors:

"/opt/pgi/linux86-64/10.4/include/bits/types.h", line 159: error: identifier
  "__SWBLK_T_TYPE" is undefined
  __STD_TYPE __SWBLK_T_TYPE __swblk_t; /* Type of a swap block maybe?  */
 ^

"/usr/include/time.h", line 123: error: identifier "__syscall_slong_t" is
  undefined
  __syscall_slong_t tv_nsec; /* Nanoseconds.  */
  ^

2 errors detected in the compilation of "hello.cpp".




Em qua, 27 de mai de 2015 às 18:28, David Shrader 
escreveu:

>  Yes, exactly like that. Given your configure line, all of the Portland
> Group's compilers need to work:
>
> $> pgf90 hello.f90
> $> pgcc hello.c
> $> pgCC hello.cpp
>
> What of those commands work for you?
>
> Thanks,
> David
>
>
> On 05/27/2015 11:01 AM, Bruno Queiros wrote:
>
> David
>
>  Do you mean if Portland Fortran compiler works? Like pgf90 hello.f ?
>
> Bruno
>
>
>  Em qua, 27 de mai de 2015 às 17:40, David Shrader 
> escreveu:
>
>>  Looking at the config.log, I see this:
>>
>> pgi-cc-lin64: LICENSE MANAGER PROBLEM: No such feature exists.
>> Feature:   pgi-cc-lin64
>>
>> It looks like there is a problem with the PGI license. Does it work with
>> a regular file (e.g., hello_world)? If it does, how do you get it to work
>> (env variables, license file, etc.)?
>>
>> Thanks,
>> David
>>
>>
>> On 05/27/2015 10:25 AM, Bruno Queiros wrote:
>>
>> Hello
>>
>>  I'm trying to compile openmpi-1.8.5 with portland fortran 10.4 64bits
>> on a CentOS7 64bits.
>>
>>  This is the output i get:
>>
>>  ./configure CC=pgcc CXX=pgCC FC=pgf90 F77=pgf77 F90=pgf90
>> --prefix=/opt/openmpi-1.8.5_pgf90
>>
>>
>> 
>> == Configuring Open MPI
>>
>> 
>>
>>  *** Startup tests
>> checking build system type... x86_64-unknown-linux-gnu
>> checking host system type... x86_64-unknown-linux-gnu
>> checking target system type... x86_64-unknown-linux-gnu
>> checking for gcc... pgcc
>> checking whether the C compiler works... no
>> configure: error: in `/root/TransferArea/openmpi-1.8.5':
>> configure: error: C compiler cannot create executables
>> See `config.log' for more details
>>
>>  The config.log goes as an attachment
>>
>>
>>   ___
>> users mailing listus...@open-mpi.org
>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
>> Link to this post: 
>> http://www.open-mpi.org/community/lists/users/2015/05/26954.php
>>
>>
>> --
>> David Shrader
>> HPC-3 High Performance Computer Systems
>> Los Alamos National Lab
>> Email: dshrader  lanl.gov
>>
>>  ___
>> users mailing list
>> us...@open-mpi.org
>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
>> Link to this post:
>> http://www.open-mpi.org/community/lists/users/2015/05/26955.php
>
>
>
> ___
> users mailing listus...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
>
>
> Link to this post: 
> http://www.open-mpi.org/community/lists/users/2015/05/26957.php
>
>
> --
> David Shrader
> HPC-3 High Performance Computer Systems
> Los Alamos National Lab
> Email: dshrader  lanl.gov
>
>  ___
> users mailing list
> us...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
> Link to this post:
> http://www.open-mpi.org/community/lists/users/2015/05/26958.php

Re: [OMPI users] Openmpi compilation errors

2015-05-27 Thread David Shrader

Yes, exactly like that. Given your configure line, all of the Portland 
Group's compilers need to work:


$> pgf90 hello.f90
$> pgcc hello.c
$> pgCC hello.cpp

What of those commands work for you?

Thanks,
David

On 05/27/2015 11:01 AM, Bruno Queiros wrote:

David

Do you mean if Portland Fortran compiler works? Like pgf90 hello.f ?

Bruno


Em qua, 27 de mai de 2015 às 17:40, David Shrader > escreveu:


Looking at the config.log, I see this:

pgi-cc-lin64: LICENSE MANAGER PROBLEM: No such feature exists.
Feature:   pgi-cc-lin64

It looks like there is a problem with the PGI license. Does it
work with a regular file (e.g., hello_world)? If it does, how do
you get it to work (env variables, license file, etc.)?

Thanks,
David


On 05/27/2015 10:25 AM, Bruno Queiros wrote:

Hello

I'm trying to compile openmpi-1.8.5 with portland fortran 10.4
64bits on a CentOS7 64bits.

This is the output i get:

./configure CC=pgcc CXX=pgCC FC=pgf90 F77=pgf77 F90=pgf90
--prefix=/opt/openmpi-1.8.5_pgf90


== Configuring Open MPI


*** Startup tests
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
checking for gcc... pgcc
checking whether the C compiler works... no
configure: error: in `/root/TransferArea/openmpi-1.8.5':
configure: error: C compiler cannot create executables
See `config.log' for more details

The config.log goes as an attachment


___
users mailing list
us...@open-mpi.org  
Subscription:http://www.open-mpi.org/mailman/listinfo.cgi/users
Link to this 
post:http://www.open-mpi.org/community/lists/users/2015/05/26954.php


-- 
David Shrader

HPC-3 High Performance Computer Systems
Los Alamos National Lab
Email: dshrader lanl.gov  

___
users mailing list
us...@open-mpi.org 
Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
Link to this post:
http://www.open-mpi.org/community/lists/users/2015/05/26955.php



___
users mailing list
us...@open-mpi.org
Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
Link to this post: 
http://www.open-mpi.org/community/lists/users/2015/05/26957.php


--
David Shrader
HPC-3 High Performance Computer Systems
Los Alamos National Lab
Email: dshrader  lanl.gov

Re: [OMPI users] Openmpi compilation errors

2015-05-27 Thread Bruno Queiros

David

Do you mean if Portland Fortran compiler works? Like pgf90 hello.f ?

Bruno


Em qua, 27 de mai de 2015 às 17:40, David Shrader 
escreveu:

>  Looking at the config.log, I see this:
>
> pgi-cc-lin64: LICENSE MANAGER PROBLEM: No such feature exists.
> Feature:   pgi-cc-lin64
>
> It looks like there is a problem with the PGI license. Does it work with a
> regular file (e.g., hello_world)? If it does, how do you get it to work
> (env variables, license file, etc.)?
>
> Thanks,
> David
>
>
> On 05/27/2015 10:25 AM, Bruno Queiros wrote:
>
> Hello
>
>  I'm trying to compile openmpi-1.8.5 with portland fortran 10.4 64bits on
> a CentOS7 64bits.
>
>  This is the output i get:
>
>  ./configure CC=pgcc CXX=pgCC FC=pgf90 F77=pgf77 F90=pgf90
> --prefix=/opt/openmpi-1.8.5_pgf90
>
>
> 
> == Configuring Open MPI
>
> 
>
>  *** Startup tests
> checking build system type... x86_64-unknown-linux-gnu
> checking host system type... x86_64-unknown-linux-gnu
> checking target system type... x86_64-unknown-linux-gnu
> checking for gcc... pgcc
> checking whether the C compiler works... no
> configure: error: in `/root/TransferArea/openmpi-1.8.5':
> configure: error: C compiler cannot create executables
> See `config.log' for more details
>
>  The config.log goes as an attachment
>
>
> ___
> users mailing listus...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
> Link to this post: 
> http://www.open-mpi.org/community/lists/users/2015/05/26954.php
>
>
> --
> David Shrader
> HPC-3 High Performance Computer Systems
> Los Alamos National Lab
> Email: dshrader  lanl.gov
>
>  ___
> users mailing list
> us...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
> Link to this post:
> http://www.open-mpi.org/community/lists/users/2015/05/26955.php

Re: [OMPI users] Openmpi compilation errors

2015-05-27 Thread David Shrader


Looking at the config.log, I see this:

pgi-cc-lin64: LICENSE MANAGER PROBLEM: No such feature exists.
Feature:   pgi-cc-lin64

It looks like there is a problem with the PGI license. Does it work with 
a regular file (e.g., hello_world)? If it does, how do you get it to 
work (env variables, license file, etc.)?


Thanks,
David

On 05/27/2015 10:25 AM, Bruno Queiros wrote:

Hello

I'm trying to compile openmpi-1.8.5 with portland fortran 10.4 64bits 
on a CentOS7 64bits.


This is the output i get:

./configure CC=pgcc CXX=pgCC FC=pgf90 F77=pgf77 F90=pgf90 
--prefix=/opt/openmpi-1.8.5_pgf90



== Configuring Open MPI


*** Startup tests
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
checking for gcc... pgcc
checking whether the C compiler works... no
configure: error: in `/root/TransferArea/openmpi-1.8.5':
configure: error: C compiler cannot create executables
See `config.log' for more details

The config.log goes as an attachment


___
users mailing list
us...@open-mpi.org
Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
Link to this post: 
http://www.open-mpi.org/community/lists/users/2015/05/26954.php


--
David Shrader
HPC-3 High Performance Computer Systems
Los Alamos National Lab
Email: dshrader  lanl.gov

[OMPI users] Openmpi compilation errors

2015-05-27 Thread Bruno Queiros

Hello

I'm trying to compile openmpi-1.8.5 with portland fortran 10.4 64bits on a
CentOS7 64bits.

This is the output i get:

./configure CC=pgcc CXX=pgCC FC=pgf90 F77=pgf77 F90=pgf90
--prefix=/opt/openmpi-1.8.5_pgf90


== Configuring Open MPI


*** Startup tests
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
checking for gcc... pgcc
checking whether the C compiler works... no
configure: error: in `/root/TransferArea/openmpi-1.8.5':
configure: error: C compiler cannot create executables
See `config.log' for more details

The config.log goes as an attachment


config.log.tar.bz2
Description: application/bzip

Re: [OMPI users] OpenMPI Compilation Error

2014-06-05 Thread George Bosilca

A fix has been pushed in the trunk (r31955). Once reviewed it will
make it to the next release 1.8.2.

  George.


On Thu, Jun 5, 2014 at 11:29 AM, Jeff Squyres (jsquyres)
 wrote:
> George and I are together at the MPI Forum this week -- we just looked at 
> this in more detail; it looks like this is a more pervasive problem.
>
> Let us look at this a bit more...
>
>
> On Jun 5, 2014, at 10:37 AM, George Bosilca  wrote:
>
>> Alan,
>>
>> I think we forgot to cleanup after a merge and as a result we have
>> c_destweights and c_sourceweights defined twice. Please try the
>> following patch and let us know if this fixes your issue.
>>
>> Index: ompi/mpi/fortran/mpif-h/dist_graph_create_adjacent_f.c
>> ===
>> --- ompi/mpi/fortran/mpif-h/dist_graph_create_adjacent_f.c (revision 31954)
>> +++ ompi/mpi/fortran/mpif-h/dist_graph_create_adjacent_f.c (working copy)
>> @@ -72,8 +72,6 @@
>> {
>> MPI_Info c_info;
>> MPI_Comm c_comm_old, c_comm_graph;
>> -const int *c_destweights, *c_sourceweights;
>> -
>> OMPI_ARRAY_NAME_DECL(sources);
>> OMPI_ARRAY_NAME_DECL(sourceweights);
>> OMPI_ARRAY_NAME_DECL(destinations);
>>
>>  George.
>>
>>
>> On Thu, Jun 5, 2014 at 12:34 AM, Alan Sang Loon  wrote:
>>> Hello,
>>>
>>> I have downloaded OpenMPI-1.8.1 and compiled it using Intel Compilers (Intel
>>> Composer XE Suites 2013) and the command used is as follow:
>>>
>>> [Code]
>>> ./configure --prefix=/opt/openmpi-1.8.1 CC=icc CXX=icpc F77=ifort FC=ifort
>>> make all install
>>> [/code]
>>>
>>> Everything works just fine except I realized that the MPI library was built
>>> for 32-bit integers (fort integer size=4)
>>>
>>> Then I reconfigured it using this command:
>>>
>>> [Code]
>>> ./configure --prefix=/opt/openmpi-1.8.1 CC=icc CXX=icpc F77=ifort FC=ifort
>>> FFLAGS=-i8 FCFLAGS=-i8
>>> [/code]
>>>
>>> However, when I tried to compile it using the make all install command, some
>>> errors appeared at the end of the compilation which is described as
>>> followed:
>>>
>>> [qoute]
>>> ... ...
>>>  CC   pdist_graph_create_adjacent_f.lo
>>> pdist_graph_create_adjacent_f.c(79): error: "c_sourceweights" has already
>>> been declared in the current scope
>>>  OMPI_ARRAY_NAME_DECL(sourceweights);
>>>  ^
>>>
>>> pdist_graph_create_adjacent_f.c(81): error: "c_destweights" has already been
>>> declared in the current scope
>>>  OMPI_ARRAY_NAME_DECL(destweights);
>>>  ^
>>>
>>> compilation aborted for pdist_graph_create_adjacent_f.c (code 2)
>>> make[3]: *** [pdist_graph_create_adjacent_f.lo] Error 1
>>> make[3]: Leaving directory
>>> `/opt/openmpi-1.8.1/ompi/mpi/fortran/mpif-h/profile'
>>> make[2]: *** [all-recursive] Error 1
>>> make[2]: Leaving directory `/opt/openmpi-1.8.1/ompi/mpi/fortran/mpif-h'
>>> make[1]: *** [all-recursive] Error 1
>>> make[1]: Leaving directory `/opt/openmpi-1.8.1/ompi'
>>> make: *** [all-recursive] Error 1
>>> [/qoute]
>>>
>>> I have no idea of what is happening. Would anyone please help me to solve
>>> the problem if it is possible?
>>>
>>> Thank you very much.
>>>
>>> ___
>>> 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
>
>
> --
> 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

Re: [OMPI users] OpenMPI Compilation Error

2014-06-05 Thread Jeff Squyres (jsquyres)

George and I are together at the MPI Forum this week -- we just looked at this 
in more detail; it looks like this is a more pervasive problem.

Let us look at this a bit more...


On Jun 5, 2014, at 10:37 AM, George Bosilca  wrote:

> Alan,
> 
> I think we forgot to cleanup after a merge and as a result we have
> c_destweights and c_sourceweights defined twice. Please try the
> following patch and let us know if this fixes your issue.
> 
> Index: ompi/mpi/fortran/mpif-h/dist_graph_create_adjacent_f.c
> ===
> --- ompi/mpi/fortran/mpif-h/dist_graph_create_adjacent_f.c (revision 31954)
> +++ ompi/mpi/fortran/mpif-h/dist_graph_create_adjacent_f.c (working copy)
> @@ -72,8 +72,6 @@
> {
> MPI_Info c_info;
> MPI_Comm c_comm_old, c_comm_graph;
> -const int *c_destweights, *c_sourceweights;
> -
> OMPI_ARRAY_NAME_DECL(sources);
> OMPI_ARRAY_NAME_DECL(sourceweights);
> OMPI_ARRAY_NAME_DECL(destinations);
> 
>  George.
> 
> 
> On Thu, Jun 5, 2014 at 12:34 AM, Alan Sang Loon  wrote:
>> Hello,
>> 
>> I have downloaded OpenMPI-1.8.1 and compiled it using Intel Compilers (Intel
>> Composer XE Suites 2013) and the command used is as follow:
>> 
>> [Code]
>> ./configure --prefix=/opt/openmpi-1.8.1 CC=icc CXX=icpc F77=ifort FC=ifort
>> make all install
>> [/code]
>> 
>> Everything works just fine except I realized that the MPI library was built
>> for 32-bit integers (fort integer size=4)
>> 
>> Then I reconfigured it using this command:
>> 
>> [Code]
>> ./configure --prefix=/opt/openmpi-1.8.1 CC=icc CXX=icpc F77=ifort FC=ifort
>> FFLAGS=-i8 FCFLAGS=-i8
>> [/code]
>> 
>> However, when I tried to compile it using the make all install command, some
>> errors appeared at the end of the compilation which is described as
>> followed:
>> 
>> [qoute]
>> ... ...
>>  CC   pdist_graph_create_adjacent_f.lo
>> pdist_graph_create_adjacent_f.c(79): error: "c_sourceweights" has already
>> been declared in the current scope
>>  OMPI_ARRAY_NAME_DECL(sourceweights);
>>  ^
>> 
>> pdist_graph_create_adjacent_f.c(81): error: "c_destweights" has already been
>> declared in the current scope
>>  OMPI_ARRAY_NAME_DECL(destweights);
>>  ^
>> 
>> compilation aborted for pdist_graph_create_adjacent_f.c (code 2)
>> make[3]: *** [pdist_graph_create_adjacent_f.lo] Error 1
>> make[3]: Leaving directory
>> `/opt/openmpi-1.8.1/ompi/mpi/fortran/mpif-h/profile'
>> make[2]: *** [all-recursive] Error 1
>> make[2]: Leaving directory `/opt/openmpi-1.8.1/ompi/mpi/fortran/mpif-h'
>> make[1]: *** [all-recursive] Error 1
>> make[1]: Leaving directory `/opt/openmpi-1.8.1/ompi'
>> make: *** [all-recursive] Error 1
>> [/qoute]
>> 
>> I have no idea of what is happening. Would anyone please help me to solve
>> the problem if it is possible?
>> 
>> Thank you very much.
>> 
>> ___
>> 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


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

Re: [OMPI users] OpenMPI Compilation Error

2014-06-05 Thread George Bosilca

Alan,

I think we forgot to cleanup after a merge and as a result we have
c_destweights and c_sourceweights defined twice. Please try the
following patch and let us know if this fixes your issue.

Index: ompi/mpi/fortran/mpif-h/dist_graph_create_adjacent_f.c
===
--- ompi/mpi/fortran/mpif-h/dist_graph_create_adjacent_f.c (revision 31954)
+++ ompi/mpi/fortran/mpif-h/dist_graph_create_adjacent_f.c (working copy)
@@ -72,8 +72,6 @@
 {
 MPI_Info c_info;
 MPI_Comm c_comm_old, c_comm_graph;
-const int *c_destweights, *c_sourceweights;
-
 OMPI_ARRAY_NAME_DECL(sources);
 OMPI_ARRAY_NAME_DECL(sourceweights);
 OMPI_ARRAY_NAME_DECL(destinations);

  George.


On Thu, Jun 5, 2014 at 12:34 AM, Alan Sang Loon  wrote:
> Hello,
>
> I have downloaded OpenMPI-1.8.1 and compiled it using Intel Compilers (Intel
> Composer XE Suites 2013) and the command used is as follow:
>
> [Code]
> ./configure --prefix=/opt/openmpi-1.8.1 CC=icc CXX=icpc F77=ifort FC=ifort
> make all install
> [/code]
>
> Everything works just fine except I realized that the MPI library was built
> for 32-bit integers (fort integer size=4)
>
> Then I reconfigured it using this command:
>
> [Code]
> ./configure --prefix=/opt/openmpi-1.8.1 CC=icc CXX=icpc F77=ifort FC=ifort
> FFLAGS=-i8 FCFLAGS=-i8
> [/code]
>
> However, when I tried to compile it using the make all install command, some
> errors appeared at the end of the compilation which is described as
> followed:
>
> [qoute]
> ... ...
>   CC   pdist_graph_create_adjacent_f.lo
> pdist_graph_create_adjacent_f.c(79): error: "c_sourceweights" has already
> been declared in the current scope
>   OMPI_ARRAY_NAME_DECL(sourceweights);
>   ^
>
> pdist_graph_create_adjacent_f.c(81): error: "c_destweights" has already been
> declared in the current scope
>   OMPI_ARRAY_NAME_DECL(destweights);
>   ^
>
> compilation aborted for pdist_graph_create_adjacent_f.c (code 2)
> make[3]: *** [pdist_graph_create_adjacent_f.lo] Error 1
> make[3]: Leaving directory
> `/opt/openmpi-1.8.1/ompi/mpi/fortran/mpif-h/profile'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/opt/openmpi-1.8.1/ompi/mpi/fortran/mpif-h'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/opt/openmpi-1.8.1/ompi'
> make: *** [all-recursive] Error 1
> [/qoute]
>
> I have no idea of what is happening. Would anyone please help me to solve
> the problem if it is possible?
>
> Thank you very much.
>
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users

[OMPI users] OpenMPI Compilation Error

2014-06-05 Thread Alan Sang Loon

Hello,

I have downloaded OpenMPI-1.8.1 and compiled it using Intel Compilers
(Intel Composer XE Suites 2013) and the command used is as follow:

[Code]
./configure --prefix=/opt/openmpi-1.8.1 CC=icc CXX=icpc F77=ifort FC=ifort
make all install
[/code]

Everything works just fine except I realized that the MPI library was built
for 32-bit integers (fort integer size=4)

Then I reconfigured it using this command:

[Code]
./configure --prefix=/opt/openmpi-1.8.1 CC=icc CXX=icpc F77=ifort FC=ifort
FFLAGS=-i8 FCFLAGS=-i8
[/code]

However, when I tried to compile it using the make all install command,
some errors appeared at the end of the compilation which is described as
followed:

[qoute]
... ...
  CC   pdist_graph_create_adjacent_f.lo
pdist_graph_create_adjacent_f.c(79): error: "c_sourceweights" has already
been declared in the current scope
  OMPI_ARRAY_NAME_DECL(sourceweights);
  ^

pdist_graph_create_adjacent_f.c(81): error: "c_destweights" has already
been declared in the current scope
  OMPI_ARRAY_NAME_DECL(destweights);
  ^

compilation aborted for pdist_graph_create_adjacent_f.c (code 2)
make[3]: *** [pdist_graph_create_adjacent_f.lo] Error 1
make[3]: Leaving directory
`/opt/openmpi-1.8.1/ompi/mpi/fortran/mpif-h/profile'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/opt/openmpi-1.8.1/ompi/mpi/fortran/mpif-h'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/opt/openmpi-1.8.1/ompi'
make: *** [all-recursive] Error 1
[/qoute]

I have no idea of what is happening. Would anyone please help me to solve
the problem if it is possible?

Thank you very much.

Re: [OMPI users] OpenMPI - compilation

2007-11-16 Thread Brian W. Barrett


On Thu, 15 Nov 2007, Tim Prins wrote:


I have seen situations where after installing Open MPI, the wrapper
compilers did not create any executables, and seemed to do nothing.

I was never able to figure out why the wrappers were broken, and
reinstalling Open MPI always seemed to make it work.

If I recall correctly, when this happened 'mpicc --showme' returned nothing.

FWIW, I only ever saw this on old versions of Open MPI, so I would
second Jeff in recommending an upgrade.


There was a bug in the wrapper compilers for the v1.2 series of releases 
where if the data file describing what the wrapper compilers should do, it 
would silently exit (returning non-zero exit status, but silently).  This 
was "not good" and fixed in v1.2.  Generally, the underlying issue is 
either 1) an incomplete Open MPI installation or 2) the installation being 
moved from the prefix specified when configuring Open MPI.


So, as others have said, upgrading will at least make the issues more 
obvious.


Brian

Re: [OMPI users] OpenMPI - compilation

2007-11-15 Thread Tim Prins

I have seen situations where after installing Open MPI, the wrapper 
compilers did not create any executables, and seemed to do nothing.


I was never able to figure out why the wrappers were broken, and 
reinstalling Open MPI always seemed to make it work.


If I recall correctly, when this happened 'mpicc --showme' returned nothing.

FWIW, I only ever saw this on old versions of Open MPI, so I would 
second Jeff in recommending an upgrade.


Tim

Jeff Squyres wrote:

On Nov 14, 2007, at 10:48 PM, Sajjad wrote:


No i didn't find any executable after the issued the command "mpicc
mpitest1.c -o mpitest1"


If you're not finding the executable at all, then something else is  
very wrong.  The "mpicc" command is just a "wrapper" compiler, meaning  
that it takes your command line, adds some more flags, and then  
invokes the underlying compiler (e.g., gcc).  You can use the "-- 
showme" flag to see exactly what command mpicc actually invokes:


 mpicc mpitest1.c -o mpitest1 --showme

Then try running the command that that shows manually and see what  
happens.  If your compiler is not producing executables at all, then  
you have some other (non-MPI) system-level issue.


And sorry for dumping such an irrelevant chunk of data to  the  
mailing list.



We actually request the output from ompi_info from users who are  
having run-time problems.  See the "getting help" page on the OMPI web  
site.


Also, I still strongly recommend upgrading to the latest stable  
version of Open MPI if possible.  The version you have (v1.1) should  
not be responsible for you not being able to create executables,  
though -- you may need to fix that independently of upgrading Open MPI.

Re: [OMPI users] OpenMPI - compilation

2007-11-15 Thread Jeff Squyres


On Nov 14, 2007, at 10:48 PM, Sajjad wrote:


No i didn't find any executable after the issued the command "mpicc
mpitest1.c -o mpitest1"


If you're not finding the executable at all, then something else is  
very wrong.  The "mpicc" command is just a "wrapper" compiler, meaning  
that it takes your command line, adds some more flags, and then  
invokes the underlying compiler (e.g., gcc).  You can use the "-- 
showme" flag to see exactly what command mpicc actually invokes:


mpicc mpitest1.c -o mpitest1 --showme

Then try running the command that that shows manually and see what  
happens.  If your compiler is not producing executables at all, then  
you have some other (non-MPI) system-level issue.


And sorry for dumping such an irrelevant chunk of data to  the  
mailing list.



We actually request the output from ompi_info from users who are  
having run-time problems.  See the "getting help" page on the OMPI web  
site.


Also, I still strongly recommend upgrading to the latest stable  
version of Open MPI if possible.  The version you have (v1.1) should  
not be responsible for you not being able to create executables,  
though -- you may need to fix that independently of upgrading Open MPI.


--
Jeff Squyres
Cisco Systems

[OMPI users] OpenMPI - compilation

2007-11-15 Thread Sajjad

Hello Jeff,

No i didn't find any executable after the issued the command "mpicc
mpitest1.c -o mpitest1"


And sorry for dumping such an irrelevant chunk of data to  the mailing list.


Sajjad

Re: [OMPI users] OpenMPI - compilation

2007-11-15 Thread Jeff Squyres

You didn't answer my question as to whether the "mpitest1" executable  
was available on all nodes or not.  :-)  That is the real problem here.


But unrelated to that, you are running an ancient version of Open MPI  
(v1.1).  Is there any chance that you can upgrade to the latest stable  
release (v1.2.4)?




On Nov 14, 2007, at 10:20 PM, Sajjad wrote:


Hello Jeff,

I thought that the following information will be helpful to track   
the issue.



***


sajjad@sajjad:~$ ompi_info
   Open MPI: 1.1
  Open MPI SVN revision: r10477
   Open RTE: 1.1
  Open RTE SVN revision: r10477
   OPAL: 1.1
  OPAL SVN revision: r10477
 Prefix: /usr
Configured architecture: x86_64-pc-linux-gnu
  Configured by: buildd
  Configured on: Tue May  1 15:04:40 GMT 2007
 Configure host: yellow
   Built by: buildd
   Built on: Tue May  1 15:19:17 GMT 2007
 Built host: yellow
 C bindings: yes
   C++ bindings: yes
 Fortran77 bindings: yes (single underscore)
 Fortran90 bindings: yes
Fortran90 bindings size: small
 C compiler: gcc
C compiler absolute: /usr/bin/gcc
   C++ compiler: g++
  C++ compiler absolute: /usr/bin/g++
 Fortran77 compiler: gfortran
 Fortran77 compiler abs: /usr/bin/gfortran
 Fortran90 compiler: gfortran
 Fortran90 compiler abs: /usr/bin/gfortran
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
 MCA memory: ptmalloc2 (MCA v1.0, API v1.0, Component  
v1.1)

  MCA paffinity: linux (MCA v1.0, API v1.0, Component v1.1)
  MCA maffinity: first_use (MCA v1.0, API v1.0, Component  
v1.1)

  MCA timer: linux (MCA v1.0, API v1.0, Component v1.1)
  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.1)
   MCA coll: hierarch (MCA v1.0, API v1.0, Component v1.1)
   MCA coll: self (MCA v1.0, API v1.0, Component v1.1)
   MCA coll: sm (MCA v1.0, API v1.0, Component v1.1)
   MCA coll: tuned (MCA v1.0, API v1.0, Component v1.1)
 MCA io: romio (MCA v1.0, API v1.0, Component v1.1)
  MCA mpool: openib (MCA v1.0, API v1.0, Component v1.1)
  MCA mpool: sm (MCA v1.0, API v1.0, Component v1.1)
MCA pml: ob1 (MCA v1.0, API v1.0, Component v1.1)
MCA bml: r2 (MCA v1.0, API v1.0, Component v1.1)
 MCA rcache: rb (MCA v1.0, API v1.0, Component v1.1)
MCA btl: openib (MCA v1.0, API v1.0, Component v1.1)
MCA btl: self (MCA v1.0, API v1.0, Component v1.1)
MCA btl: sm (MCA v1.0, API v1.0, Component v1.1)
MCA btl: tcp (MCA v1.0, API v1.0, Component v1.0)
   MCA topo: unity (MCA v1.0, API v1.0, Component v1.1)
MCA osc: pt2pt (MCA v1.0, API v1.0, Component v1.0)
MCA gpr: null (MCA v1.0, API v1.0, Component v1.1)
MCA gpr: proxy (MCA v1.0, API v1.0, Component v1.1)
MCA gpr: replica (MCA v1.0, API v1.0, Component v1.1)
MCA iof: proxy (MCA v1.0, API v1.0, Component v1.1)
MCA iof: svc (MCA v1.0, API v1.0, Component v1.1)
 MCA ns: proxy (MCA v1.0, API v1.0, Component v1.1)
 MCA ns: replica (MCA v1.0, API v1.0, Component v1.1)
MCA oob: tcp (MCA v1.0, API v1.0, Component v1.0)
MCA ras: dash_host (MCA v1.0, API v1.0, Component  
v1.1)

MCA ras: hostfile (MCA v1.0, API v1.0, Component v1.1)
MCA ras: localhost (MCA v1.0, API v1.0, Component  
v1.1)

MCA ras: slurm (MCA v1.0, API v1.0, Component v1.1)
MCA rds: hostfile (MCA v1.0, API v1.0, Component v1.1)
MCA rds: resfile (MCA v1.0, API v1.0, Component v1.1)
  MCA rmaps: round_robin (MCA v1.0, API v1.0, Component  
v1.1)

   MCA rmgr: proxy (MCA v1.0, API v1.0, Component v1.1)
   MCA rmgr: urm (MCA v1.0, API v1.0, Component v1.1)
MCA rml: oob (MCA v1.0, API v1.0, Component v1.1)
MCA pls: fork (MCA v1.0, API v1.0, Component v1.1)
MCA pls: rsh (MCA v1.0, API v1.0, Component v1.1)
MCA pls: slurm (MCA v1.0, API v1.0, Component v1.1)
MCA sds: env (MCA v1.0, API v1.0, Component v1.1)
MCA sds: pipe (MCA v1.0, API v1.0, Component v1.1)
MCA sds:

[OMPI users] OpenMPI - compilation

2007-11-15 Thread Sajjad

Hello Jeff,

I thought that the following information will be helpful to track  the issue.


***


sajjad@sajjad:~$ ompi_info
Open MPI: 1.1
   Open MPI SVN revision: r10477
Open RTE: 1.1
   Open RTE SVN revision: r10477
OPAL: 1.1
   OPAL SVN revision: r10477
  Prefix: /usr
 Configured architecture: x86_64-pc-linux-gnu
   Configured by: buildd
   Configured on: Tue May  1 15:04:40 GMT 2007
  Configure host: yellow
Built by: buildd
Built on: Tue May  1 15:19:17 GMT 2007
  Built host: yellow
  C bindings: yes
C++ bindings: yes
  Fortran77 bindings: yes (single underscore)
  Fortran90 bindings: yes
 Fortran90 bindings size: small
  C compiler: gcc
 C compiler absolute: /usr/bin/gcc
C++ compiler: g++
   C++ compiler absolute: /usr/bin/g++
  Fortran77 compiler: gfortran
  Fortran77 compiler abs: /usr/bin/gfortran
  Fortran90 compiler: gfortran
  Fortran90 compiler abs: /usr/bin/gfortran
 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
  MCA memory: ptmalloc2 (MCA v1.0, API v1.0, Component v1.1)
   MCA paffinity: linux (MCA v1.0, API v1.0, Component v1.1)
   MCA maffinity: first_use (MCA v1.0, API v1.0, Component v1.1)
   MCA timer: linux (MCA v1.0, API v1.0, Component v1.1)
   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.1)
MCA coll: hierarch (MCA v1.0, API v1.0, Component v1.1)
MCA coll: self (MCA v1.0, API v1.0, Component v1.1)
MCA coll: sm (MCA v1.0, API v1.0, Component v1.1)
MCA coll: tuned (MCA v1.0, API v1.0, Component v1.1)
  MCA io: romio (MCA v1.0, API v1.0, Component v1.1)
   MCA mpool: openib (MCA v1.0, API v1.0, Component v1.1)
   MCA mpool: sm (MCA v1.0, API v1.0, Component v1.1)
 MCA pml: ob1 (MCA v1.0, API v1.0, Component v1.1)
 MCA bml: r2 (MCA v1.0, API v1.0, Component v1.1)
  MCA rcache: rb (MCA v1.0, API v1.0, Component v1.1)
 MCA btl: openib (MCA v1.0, API v1.0, Component v1.1)
 MCA btl: self (MCA v1.0, API v1.0, Component v1.1)
 MCA btl: sm (MCA v1.0, API v1.0, Component v1.1)
 MCA btl: tcp (MCA v1.0, API v1.0, Component v1.0)
MCA topo: unity (MCA v1.0, API v1.0, Component v1.1)
 MCA osc: pt2pt (MCA v1.0, API v1.0, Component v1.0)
 MCA gpr: null (MCA v1.0, API v1.0, Component v1.1)
 MCA gpr: proxy (MCA v1.0, API v1.0, Component v1.1)
 MCA gpr: replica (MCA v1.0, API v1.0, Component v1.1)
 MCA iof: proxy (MCA v1.0, API v1.0, Component v1.1)
 MCA iof: svc (MCA v1.0, API v1.0, Component v1.1)
  MCA ns: proxy (MCA v1.0, API v1.0, Component v1.1)
  MCA ns: replica (MCA v1.0, API v1.0, Component v1.1)
 MCA oob: tcp (MCA v1.0, API v1.0, Component v1.0)
 MCA ras: dash_host (MCA v1.0, API v1.0, Component v1.1)
 MCA ras: hostfile (MCA v1.0, API v1.0, Component v1.1)
 MCA ras: localhost (MCA v1.0, API v1.0, Component v1.1)
 MCA ras: slurm (MCA v1.0, API v1.0, Component v1.1)
 MCA rds: hostfile (MCA v1.0, API v1.0, Component v1.1)
 MCA rds: resfile (MCA v1.0, API v1.0, Component v1.1)
   MCA rmaps: round_robin (MCA v1.0, API v1.0, Component v1.1)
MCA rmgr: proxy (MCA v1.0, API v1.0, Component v1.1)
MCA rmgr: urm (MCA v1.0, API v1.0, Component v1.1)
 MCA rml: oob (MCA v1.0, API v1.0, Component v1.1)
 MCA pls: fork (MCA v1.0, API v1.0, Component v1.1)
 MCA pls: rsh (MCA v1.0, API v1.0, Component v1.1)
 MCA pls: slurm (MCA v1.0, API v1.0, Component v1.1)
 MCA sds: env (MCA v1.0, API v1.0, Component v1.1)
 MCA sds: pipe (MCA v1.0, API v1.0, Component v1.1)
 MCA sds: seed (MCA v1.0, API v1.0, Component v1.1)
 MCA sds: singleton (MCA v1.0, API v1.0, Component v1.1)
 MCA sds: slurm (MCA v1.0, API v1.0, Component v1.1)

Re: [OMPI users] OpenMPI - compilation

2007-11-14 Thread Jeff Squyres

What version of Open MPI are you using?  I see that particular error  
listed in the "rmgr" part of the code base, not the "pls" part of the  
code base in the current release (1.2.4).  Meaning: I'm guessing that  
the fact that this help message is not found in your version has been  
fixed in a later version.


As George pointed out, the real issue is that the "mpitest1"  
executable was not found when OMPI tried to run it.  Do you have  
mpitest1 available on all nodes where you tried to run it?  (e.g., via  
NFS or some global filesystem)



On Nov 14, 2007, at 5:08 PM, George Bosilca wrote:

The real error message hidden behind the argv0-not-accesible is:  
Failed to find or execute the following executable:


 george.

On Nov 14, 2007, at 4:08 PM, Sajjad wrote:


Hello Brock,

I renamed the whole file as mpitest1.c and issued the following  
command


mpicc mpitest1.c -o mpitest1
mpirun -np 4 ./mpitest1

then i got the following output:

--
Sorry!  You were supposed to get help about:
  argv0-not-accessible
from the file:
  help-pls-base.txt
But I couldn't find any file matching that name.  Sorry!
--

Could not  actually follow what does that mean,

Any idea?



Regards
Sajjad
___
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



--
Jeff Squyres
Cisco Systems

Re: [OMPI users] OpenMPI - compilation

2007-11-14 Thread George Bosilca

The real error message hidden behind the argv0-not-accesible is:  
Failed to find or execute the following executable:


  george.

On Nov 14, 2007, at 4:08 PM, Sajjad wrote:


Hello Brock,

I renamed the whole file as mpitest1.c and issued the following  
command


mpicc mpitest1.c -o mpitest1
mpirun -np 4 ./mpitest1

then i got the following output:

--
Sorry!  You were supposed to get help about:
   argv0-not-accessible
from the file:
   help-pls-base.txt
But I couldn't find any file matching that name.  Sorry!
--

Could not  actually follow what does that mean,

Any idea?



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




smime.p7s
Description: S/MIME cryptographic signature

[OMPI users] OpenMPI - compilation

2007-11-14 Thread Sajjad

Hello Brock,

I renamed the whole file as mpitest1.c and issued the following command

 mpicc mpitest1.c -o mpitest1
 mpirun -np 4 ./mpitest1

then i got the following output:

--
Sorry!  You were supposed to get help about:
argv0-not-accessible
from the file:
help-pls-base.txt
But I couldn't find any file matching that name.  Sorry!
--

Could not  actually follow what does that mean,

Any idea?



Regards
Sajjad

Re: [OMPI users] OpenMPI - compilation

2007-11-14 Thread Brock Palen

Dont use the name 'test'  test is a unix command and it causes  
problems when you name things 'test'


If you try
mpirun -np 4 ./test

it will work because that will use the test you just created not the  
regular 'test'

But really dont use the name test and it will work as expected.

Brock Palen
Center for Advanced Computing
bro...@umich.edu
(734)936-1985


On Nov 14, 2007, at 10:07 AM, Sajjad wrote:


Hello,

I have installed openmpi from the ubuntu repository for the 64-bit
dual core AMD processor.

and i tried to compile the simple test program with the help of the
tutorial page but nothing seems to happen.

#include 
#include 

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

MPI_Init(&argc,&argv);
MPI_Comm_rank(MPI_COMM_WORLD, &rank);
printf("my rank=%d\n",rank);
MPI_Finalize();

return 0;
}


then from the console i issued the following command

mpicc test.c -o test
mpirun -np 4 test

nothing happens. actually after the command "mpicc test.c -o test"
shouldnt i be having a .o file?

I do not understand how do i get to know if my current installation is
fine or not.


Any suggestion?



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

[OMPI users] OpenMPI - compilation

2007-11-14 Thread Sajjad

Hello,

I have installed openmpi from the ubuntu repository for the 64-bit
dual core AMD processor.

and i tried to compile the simple test program with the help of the
tutorial page but nothing seems to happen.

#include 
#include 

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

MPI_Init(&argc,&argv);
MPI_Comm_rank(MPI_COMM_WORLD, &rank);
printf("my rank=%d\n",rank);
MPI_Finalize();

return 0;
}


then from the console i issued the following command

mpicc test.c -o test
mpirun -np 4 test

nothing happens. actually after the command "mpicc test.c -o test"
shouldnt i be having a .o file?

I do not understand how do i get to know if my current installation is
fine or not.


Any suggestion?



Regards
Sajjad

Re: [OMPI users] Openmpi compilation errors

Re: [OMPI users] Openmpi compilation errors

Re: [OMPI users] Openmpi compilation errors

Re: [OMPI users] Openmpi compilation errors

Re: [OMPI users] Openmpi compilation errors

Re: [OMPI users] Openmpi compilation errors

Re: [OMPI users] Openmpi compilation errors

Re: [OMPI users] Openmpi compilation errors

Re: [OMPI users] Openmpi compilation errors

Re: [OMPI users] Openmpi compilation errors

Re: [OMPI users] Openmpi compilation errors

Re: [OMPI users] Openmpi compilation errors

Re: [OMPI users] Openmpi compilation errors

Re: [OMPI users] Openmpi compilation errors

Re: [OMPI users] Openmpi compilation errors

Re: [OMPI users] Openmpi compilation errors

Re: [OMPI users] Openmpi compilation errors

Re: [OMPI users] Openmpi compilation errors

Re: [OMPI users] Openmpi compilation errors

Re: [OMPI users] Openmpi compilation errors

[OMPI users] Openmpi compilation errors

Re: [OMPI users] OpenMPI Compilation Error

Re: [OMPI users] OpenMPI Compilation Error

Re: [OMPI users] OpenMPI Compilation Error

[OMPI users] OpenMPI Compilation Error

Re: [OMPI users] OpenMPI - compilation

Re: [OMPI users] OpenMPI - compilation

Re: [OMPI users] OpenMPI - compilation

[OMPI users] OpenMPI - compilation

Re: [OMPI users] OpenMPI - compilation

[OMPI users] OpenMPI - compilation

Re: [OMPI users] OpenMPI - compilation

Re: [OMPI users] OpenMPI - compilation

[OMPI users] OpenMPI - compilation

Re: [OMPI users] OpenMPI - compilation

[OMPI users] OpenMPI - compilation

36 matches

Site Navigation

Mail list logo

Footer information