Re: [OMPI users] Query name of appfile

[Ralph Castain]

Never seen anyone ask for that info, but I imagine we could provide it as some 
envar

On Sep 17, 2013, at 6:26 AM, Reuti  wrote:

> Am 17.09.2013 um 14:35 schrieb Bontus, Claas:
> 
>> Starting an MPI run via
>> mpirun --app myappfile.app
>> is there any way to obtain at run-time the name of the appfile, the path and 
>> server name where it is saved.
> 
> As you have an appfile anyway, it's also possible to define environment 
> variables therein:
> 
> -x file=baz -x server=foobar
> 
> in each line and use these in each of the applications. Well, yes - this 
> would be hardcoded in some way.
> 
> -- Reuti
> 
> 
>> 
>> Thanks
>> claas
>> 
>> 
>> 
>> The information contained in this message may be confidential and legally 
>> protected under applicable law. The message is intended solely for the 
>> addressee(s). If you are not the intended recipient, you are hereby notified 
>> that any use, forwarding, dissemination, or reproduction of this message is 
>> strictly prohibited and may be unlawful. If you are not the intended 
>> recipient, please contact the sender by return e-mail and destroy all copies 
>> of the original message.
>> 
>> ___
>> 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] Query name of appfile

[Reuti]

Am 17.09.2013 um 14:35 schrieb Bontus, Claas:

> Starting an MPI run via
> mpirun --app myappfile.app
> is there any way to obtain at run-time the name of the appfile, the path and 
> server name where it is saved.

As you have an appfile anyway, it's also possible to define environment 
variables therein:

 -x file=baz -x server=foobar

in each line and use these in each of the applications. Well, yes - this would 
be hardcoded in some way.

-- Reuti


> 
> Thanks
> claas
> 
> 
> 
> The information contained in this message may be confidential and legally 
> protected under applicable law. The message is intended solely for the 
> addressee(s). If you are not the intended recipient, you are hereby notified 
> that any use, forwarding, dissemination, or reproduction of this message is 
> strictly prohibited and may be unlawful. If you are not the intended 
> recipient, please contact the sender by return e-mail and destroy all copies 
> of the original message.
> 
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users

Re: [OMPI users] Query name of appfile

[John Hearns]

Not a good answer to your question but you could look for the child
processes and look at /proc/$pid/cmdline and cwd

Or just use pgrep -P $pidofmpirun

This is not a good answer. I'm sitting at lunch - so an expert will be
along in a minute with a good answer.

[OMPI users] Query name of appfile

[Bontus, Claas]

Starting an MPI run via
mpirun --app myappfile.app
is there any way to obtain at run-time the name of the appfile, the path and 
server name where it is saved.

Thanks
claas



The information contained in this message may be confidential and legally 
protected under applicable law. The message is intended solely for the 
addressee(s). If you are not the intended recipient, you are hereby notified 
that any use, forwarding, dissemination, or reproduction of this message is 
strictly prohibited and may be unlawful. If you are not the intended recipient, 
please contact the sender by return e-mail and destroy all copies of the 
original message.

Re: [OMPI users] Error in openmpi-1.9a1r29179

[Jeff Squyres (jsquyres)]

This is definitely a bug.  I'm moving this thread over to the devel list so 
that developers can fix it (sorry; I should have asked you to post directly to 
devel rather than to the users list!).


On Sep 17, 2013, at 8:49 AM, Siegmar Gross 
 wrote:

> Hi,
> 
> I tried to install openmpi-1.9a1r29179 on "openSuSE Linux 12.1",
> "Solaris 10 x86_64", and "Solaris 10 sparc" with "Sun C 5.12" in
> 64-bit mode. Unfortunately "make" breaks with the same error on
> all platforms.
> 
> tail -15 log.make.Linux.x86_64.64_cc
> 
>  CCLD libshmem_c.la
> make[3]: Leaving directory 
> `/export2/src/openmpi-1.9/openmpi-1.9a1r29179-Linux.x86_64.64_cc/oshmem/shmem/c'
> make[2]: Leaving directory 
> `/export2/src/openmpi-1.9/openmpi-1.9a1r29179-Linux.x86_64.64_cc/oshmem/shmem/c'
> Making all in shmem/fortran
> make[2]: Entering directory 
> `/export2/src/openmpi-1.9/openmpi-1.9a1r29179-Linux.x86_64.64_cc/oshmem/shmem/fortran'
>  CC   start_pes_f.lo
> "../../../../openmpi-1.9a1r29179/oshmem/shmem/fortran/start_pes_f.c", line 
> 16: void function cannot return value
> "../../../../openmpi-1.9a1r29179/oshmem/shmem/fortran/start_pes_f.c", line 
> 16: void function cannot return value
> "../../../../openmpi-1.9a1r29179/oshmem/shmem/fortran/start_pes_f.c", line 
> 16: void function cannot return value
> cc: acomp failed for 
> ../../../../openmpi-1.9a1r29179/oshmem/shmem/fortran/start_pes_f.c
> make[2]: *** [start_pes_f.lo] Error 1
> make[2]: Leaving directory 
> `/export2/src/openmpi-1.9/openmpi-1.9a1r29179-Linux.x86_64.64_cc/oshmem/shmem/fortran'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory 
> `/export2/src/openmpi-1.9/openmpi-1.9a1r29179-Linux.x86_64.64_cc/oshmem'
> make: *** [all-recursive] Error 1
> 
> 
> I configured with the following command.
> 
> ../openmpi-1.9a1r29179/configure --prefix=/usr/local/openmpi-1.9_64_cc \
>  --libdir=/usr/local/openmpi-1.9_64_cc/lib64 \
>  --with-jdk-bindir=/usr/local/jdk1.7.0_07-64/bin \
>  --with-jdk-headers=/usr/local/jdk1.7.0_07-64/include \
>  JAVA_HOME=/usr/local/jdk1.7.0_07-64 \
>  LDFLAGS="-m64" \
>  CC="cc" CXX="CC" FC="f95" \
>  CFLAGS="-m64" CXXFLAGS="-m64 -library=stlport4" FCFLAGS="-m64" \
>  CPP="cpp" CXXCPP="cpp" \
>  CPPFLAGS="" CXXCPPFLAGS="" \
>  --enable-mpi-cxx \
>  --enable-cxx-exceptions \
>  --enable-mpi-java \
>  --enable-heterogeneous \
>  --enable-opal-multi-threads \
>  --enable-mpi-thread-multiple \
>  --with-threads=posix \
>  --with-hwloc=internal \
>  --without-verbs \
>  --without-udapl \
>  --without-sctp \
>  --with-wrapper-cflags=-m64 \
>  --enable-debug \
>  |& tee log.configure.$SYSTEM_ENV.$MACHINE_ENV.64_cc
> 
> 
> 
> I would be grateful if somebody can fix the bug. Thank you very
> much for any help in advance.
> 
> 
> Kind regards
> 
> Siegmar
> 
> 
> ___
> 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/

[OMPI users] Error in openmpi-1.9a1r29179

[Siegmar Gross]

Hi,

I tried to install openmpi-1.9a1r29179 on "openSuSE Linux 12.1",
"Solaris 10 x86_64", and "Solaris 10 sparc" with "Sun C 5.12" in
64-bit mode. Unfortunately "make" breaks with the same error on
all platforms.

tail -15 log.make.Linux.x86_64.64_cc

  CCLD libshmem_c.la
make[3]: Leaving directory 
`/export2/src/openmpi-1.9/openmpi-1.9a1r29179-Linux.x86_64.64_cc/oshmem/shmem/c'
make[2]: Leaving directory 
`/export2/src/openmpi-1.9/openmpi-1.9a1r29179-Linux.x86_64.64_cc/oshmem/shmem/c'
Making all in shmem/fortran
make[2]: Entering directory 
`/export2/src/openmpi-1.9/openmpi-1.9a1r29179-Linux.x86_64.64_cc/oshmem/shmem/fortran'
  CC   start_pes_f.lo
"../../../../openmpi-1.9a1r29179/oshmem/shmem/fortran/start_pes_f.c", line 16: 
void function cannot return value
"../../../../openmpi-1.9a1r29179/oshmem/shmem/fortran/start_pes_f.c", line 16: 
void function cannot return value
"../../../../openmpi-1.9a1r29179/oshmem/shmem/fortran/start_pes_f.c", line 16: 
void function cannot return value
cc: acomp failed for 
../../../../openmpi-1.9a1r29179/oshmem/shmem/fortran/start_pes_f.c
make[2]: *** [start_pes_f.lo] Error 1
make[2]: Leaving directory 
`/export2/src/openmpi-1.9/openmpi-1.9a1r29179-Linux.x86_64.64_cc/oshmem/shmem/fortran'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory 
`/export2/src/openmpi-1.9/openmpi-1.9a1r29179-Linux.x86_64.64_cc/oshmem'
make: *** [all-recursive] Error 1


I configured with the following command.

../openmpi-1.9a1r29179/configure --prefix=/usr/local/openmpi-1.9_64_cc \
  --libdir=/usr/local/openmpi-1.9_64_cc/lib64 \
  --with-jdk-bindir=/usr/local/jdk1.7.0_07-64/bin \
  --with-jdk-headers=/usr/local/jdk1.7.0_07-64/include \
  JAVA_HOME=/usr/local/jdk1.7.0_07-64 \
  LDFLAGS="-m64" \
  CC="cc" CXX="CC" FC="f95" \
  CFLAGS="-m64" CXXFLAGS="-m64 -library=stlport4" FCFLAGS="-m64" \
  CPP="cpp" CXXCPP="cpp" \
  CPPFLAGS="" CXXCPPFLAGS="" \
  --enable-mpi-cxx \
  --enable-cxx-exceptions \
  --enable-mpi-java \
  --enable-heterogeneous \
  --enable-opal-multi-threads \
  --enable-mpi-thread-multiple \
  --with-threads=posix \
  --with-hwloc=internal \
  --without-verbs \
  --without-udapl \
  --without-sctp \
  --with-wrapper-cflags=-m64 \
  --enable-debug \
  |& tee log.configure.$SYSTEM_ENV.$MACHINE_ENV.64_cc



I would be grateful if somebody can fix the bug. Thank you very
much for any help in advance.


Kind regards

Siegmar

Re: [OMPI users] compilation aborted for Handler.cpp (code 2)

[Jeff Squyres (jsquyres)]

On Sep 16, 2013, at 9:00 AM, Syed Ahsan Ali  wrote:

> I am trying to compile openmpi-1.6.5 on fc16.x86_64 with icc and ifort
> but getting the subject error. config.out and make.out is attached.
> Following command was used for configure
> 
> ./configure CC=icc CXX=icpc FC=ifort F77=ifort F90=ifort
> --prefix=/home/openmpi_gfortran -enable-mpi-f90 --enable-mpi-f77 |&
> tee config.out

I'm sorry; I can't open a .rar file.  Can you send the logs compressed with a 
conventional compression program like gzip, bzip2, or zip?

Thanks.

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