Discussion:
[OMPI users] openmpi-1.10.3 cross compile configure options for arm-openwrt-linux-muslgnueabi on x86_64-linux-gnu
Mahesh Nanavalla
2016-10-18 04:48:39 UTC
Permalink
Hi everyone,

I'm trying to cross compile openmpi-1.10.3 for arm-openwrt-linux-muslgnueabi
on x86_64-linux-gnu with below configure options...


./configure --enable-orterun-prefix-by-default
--prefix="/home/nmahesh/Workspace/ARM_MPI/openmpi"
--build=x86_64-linux-gnu
--host=x86_64-linux-gnu
--target=arm-openwrt-linux-muslgnueabi
--enable-script-wrapper-compilers
--disable-mpi-fortran
--enable-shared
--disable-mmap-shmem
--disable-posix-shmem
--disable-sysv-shmem
--disable-dlopen
configuring,make &make install successfully.
I added
$export PATH="$PATH:/home/$USER/Workspace/ARM_MPI/openmpi/bin/"
$export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/home/$USER/Workspace/
ARM_MPI/openmpi/lib/"

$export PATH="$PATH:/home/$USER/Workspace/ARM_MPI/openmpi/bin/" >>
/home/$USER/.bashrc
$export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/home/$USER/Workspace/ARM_MPI/openmpi/lib/"
/home/$USER/.bashrc

But while compiling as below i'am getting error

*$ /home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
-L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c *
Possible unintended interpolation of @ORTE_WRAPPER_EXTRA_CXXFLAGS_PREFIX in
string at /home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc line 40.
Possible unintended interpolation of @libdir in string at
/home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc line 43.
Name "main::ORTE_WRAPPER_EXTRA_CXXFLAGS_PREFIX" used only once: possible
typo at /home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc line 40.
Name "main::libdir" used only once: possible typo at
/home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc line 43.
/home/nmahesh/Workspace/ARM_MPI/openmpi/lib/libmpi.so: file not recognized:
File format not recognized
collect2: error: ld returned 1 exit status

*can anybody help..*
Gilles Gouaillardet
2016-10-18 08:07:47 UTC
Permalink
Hi,


can you please give the patch below a try ?

Cheers,

Gilles

diff --git a/ompi/tools/wrappers/ompi_wrapper_script.in
b/ompi/tools/wrappers/ompi_wrapper_script.in
index d87649f..b66fec3 100644
--- a/ompi/tools/wrappers/ompi_wrapper_script.in
+++ b/ompi/tools/wrappers/ompi_wrapper_script.in
@@ -35,12 +35,12 @@ my $FC = "@FC@";
Post by Mahesh Nanavalla
Hi everyone,
I'm trying to cross compile openmpi-1.10.3
for arm-openwrt-linux-muslgnueabi on x86_64-linux-gnu with below
configure options...
./configure --enable-orterun-prefix-by-default
--prefix="/home/nmahesh/Workspace/ARM_MPI/openmpi"
--build=x86_64-linux-gnu
--host=x86_64-linux-gnu
--target=arm-openwrt-linux-muslgnueabi
--enable-script-wrapper-compilers
--disable-mpi-fortran
--enable-shared
--disable-mmap-shmem
--disable-posix-shmem
--disable-sysv-shmem
--disable-dlopen
configuring,make &make install successfully.
I added
$export PATH="$PATH:/home/$USER/Workspace/ARM_MPI/openmpi/bin/"
$export
LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/home/$USER/Workspace/ARM_MPI/openmpi/lib/"
$export PATH="$PATH:/home/$USER/Workspace/ARM_MPI/openmpi/bin/" >>
/home/$USER/.bashrc
$export
LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/home/$USER/Workspace/ARM_MPI/openmpi/lib/" >>
/home/$USER/.bashrc
But while compiling as below i'am getting error
*$ /home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
-L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c *
Possible unintended interpolation of
@ORTE_WRAPPER_EXTRA_CXXFLAGS_PREFIX in string at
/home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc line 40.
/home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc line 43.
possible typo at /home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
line 40.
Name "main::libdir" used only once: possible typo at
/home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc line 43.
/home/nmahesh/Workspace/ARM_MPI/openmpi/lib/libmpi.so: file not
recognized: File format not recognized
collect2: error: ld returned 1 exit status
*can anybody help..*
_______________________________________________
users mailing list
https://rfd.newmexicoconsortium.org/mailman/listinfo/users
Mahesh Nanavalla
2016-10-18 10:20:57 UTC
Permalink
Hi Gilles,

Thanks for responding me.....
i did as mention previous mail ,but am getting below error as mpicc not
found...........

****@nmahesh-H81MLV3:~/Workspace/ARM_MPI/mpi$
/home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
-L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c *
*bash: /home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc: No such file or
directory*


but i cheak in folder as follow

****@nmahesh-H81MLV3:~/Workspace/ARM_MPI/openmpi/bin$ lltotal
35460drwxrwxr-x 2 nmahesh nmahesh 4096 Oct 18 15:34 ./drwxrwxr-x 7
nmahesh nmahesh 4096 Oct 18 15:34 ../-rwxr-xr-x 1 nmahesh nmahesh
22961 Oct 18 15:34 arm-openwrt-linux-muslgnueabi-ompi_info*-rwxr-xr-x 1
nmahesh nmahesh 5661 Oct 18 15:34
arm-openwrt-linux-muslgnueabi-ompi_wrapper_script*-rwxr-xr-x 1 nmahesh
nmahesh 14699 Oct 18 15:34
arm-openwrt-linux-muslgnueabi-orte-clean*-rwxr-xr-x 1 nmahesh nmahesh
8770 Oct 18 15:34 arm-openwrt-linux-muslgnueabi-orted*-rwxr-xr-x 1 nmahesh
nmahesh 56800 Oct 18 15:34
arm-openwrt-linux-muslgnueabi-orte-dvm*-rwxr-xr-x 1 nmahesh nmahesh 35191
Oct 18 15:34 arm-openwrt-linux-muslgnueabi-orte-info*-rwxr-xr-x 1 nmahesh
nmahesh 23939 Oct 18 15:34
arm-openwrt-linux-muslgnueabi-orte-ps*-rwxr-xr-x 1 nmahesh nmahesh 124520
Oct 18 15:34 arm-openwrt-linux-muslgnueabi-orterun*-rwxr-xr-x 1 nmahesh
nmahesh 15429 Oct 18 15:34
arm-openwrt-linux-muslgnueabi-orte-server*-rwxr-xr-x 1 nmahesh nmahesh
79807 Oct 18 15:34 arm-openwrt-linux-muslgnueabi-orte-submit*-rwxr-xr-x 1
nmahesh nmahesh 30514 Oct 18 15:34
arm-openwrt-linux-muslgnueabi-orte-top*-rwxr-xr-x 1 nmahesh nmahesh 23032
Oct 18 15:34 arm-openwrt-linux-muslgnueabi-oshmem_info*-rwxr-xr-x 1 nmahesh
nmahesh 980414 Oct 18 15:34
arm-openwrt-linux-muslgnueabi-otfaux*-rwxr-xr-x 1 nmahesh nmahesh 40607
Oct 18 15:34 arm-openwrt-linux-muslgnueabi-otfcompress*-rwxr-xr-x 1 nmahesh
nmahesh 20915 Oct 18 15:34
arm-openwrt-linux-muslgnueabi-otfconfig*-rwxr-xr-x 1 nmahesh nmahesh
94717 Oct 18 15:34 arm-openwrt-linux-muslgnueabi-otfinfo*-rwxr-xr-x 1
nmahesh nmahesh 115276 Oct 18 15:34
arm-openwrt-linux-muslgnueabi-otfmerge*-rwxr-xr-x 1 nmahesh nmahesh 122985
Oct 18 15:34 arm-openwrt-linux-muslgnueabi-otfmerge-mpi*-rwxr-xr-x 1
nmahesh nmahesh 231420 Oct 18 15:34
arm-openwrt-linux-muslgnueabi-otfprint*-rwxr-xr-x 1 nmahesh nmahesh 6356996
Oct 18 15:34 arm-openwrt-linux-muslgnueabi-otfprofile*-rwxr-xr-x 1 nmahesh
nmahesh 7037080 Oct 18 15:34
arm-openwrt-linux-muslgnueabi-otfprofile-mpi*-rwxr-xr-x 1 nmahesh nmahesh
417971 Oct 18 15:34 arm-openwrt-linux-muslgnueabi-otfshrink*lrwxrwxrwx 1
nmahesh nmahesh 19 Oct 18 15:34 mpic++ ->
ompi_wrapper_scriptlrwxrwxrwx 1 nmahesh nmahesh 19 Oct 18 15:34 mpicc
-> ompi_wrapper_scriptlrwxrwxrwx 1 nmahesh nmahesh 19 Oct 18 15:34
mpiCC -> ompi_wrapper_scriptlrwxrwxrwx 1 nmahesh nmahesh 19 Oct 18
15:34 mpicxx -> ompi_wrapper_scriptlrwxrwxrwx 1 nmahesh nmahesh 7 Oct
18 15:34 mpiexec -> orterunlrwxrwxrwx 1 nmahesh nmahesh 19 Oct 18
15:34 mpif77 -> ompi_wrapper_scriptlrwxrwxrwx 1 nmahesh nmahesh 19 Oct
18 15:34 mpif90 -> ompi_wrapper_scriptlrwxrwxrwx 1 nmahesh nmahesh 19
Oct 18 15:34 mpifort -> ompi_wrapper_scriptlrwxrwxrwx 1 nmahesh nmahesh
7 Oct 18 15:34 mpirun -> orterunlrwxrwxrwx 1 nmahesh nmahesh 10 Oct
18 15:34 ompi-clean -> orte-cleanlrwxrwxrwx 1 nmahesh nmahesh 7 Oct
18 15:34 ompi-ps -> orte-pslrwxrwxrwx 1 nmahesh nmahesh 11 Oct 18
15:34 ompi-server -> orte-serverlrwxrwxrwx 1 nmahesh nmahesh 8 Oct 18
15:34 ompi-top -> orte-top-rwxr-xr-x 1 nmahesh nmahesh 1766460 Oct 18 15:34
opari*lrwxrwxrwx 1 nmahesh nmahesh 5 Oct 18 15:34 oshcc ->
mpicclrwxrwxrwx 1 nmahesh nmahesh 7 Oct 18 15:34 oshfort ->
mpifortlrwxrwxrwx 1 nmahesh nmahesh 6 Oct 18 15:34 oshrun ->
mpirunlrwxrwxrwx 1 nmahesh nmahesh 11 Oct 18 15:34 otfdecompress ->
otfcompresslrwxrwxrwx 1 nmahesh nmahesh 5 Oct 18 15:34 shmemcc ->
mpicclrwxrwxrwx 1 nmahesh nmahesh 7 Oct 18 15:34 shmemfort ->
mpifortlrwxrwxrwx 1 nmahesh nmahesh 6 Oct 18 15:34 shmemrun ->
mpirunlrwxrwxrwx 1 nmahesh nmahesh 9 Oct 18 15:34 vtc++ ->
vtwrapper*lrwxrwxrwx 1 nmahesh nmahesh 9 Oct 18 15:34 vtcc ->
vtwrapper*lrwxrwxrwx 1 nmahesh nmahesh 9 Oct 18 15:34 vtCC ->
vtwrapper*lrwxrwxrwx 1 nmahesh nmahesh 9 Oct 18 15:34 vtcxx ->
vtwrapper*lrwxrwxrwx 1 nmahesh nmahesh 9 Oct 18 15:34 vtf77 ->
vtwrapper*lrwxrwxrwx 1 nmahesh nmahesh 9 Oct 18 15:34 vtf90 ->
vtwrapper*-rwxr-xr-x 1 nmahesh nmahesh 2928026 Oct 18 15:34
vtfilter*lrwxrwxrwx 1 nmahesh nmahesh 8 Oct 18 15:34 vtfiltergen ->
vtfilter*lrwxrwxrwx 1 nmahesh nmahesh 12 Oct 18 15:34 vtfiltergen-mpi
-> vtfilter-mpi*-rwxr-xr-x 1 nmahesh nmahesh 3100359 Oct 18 15:34
vtfilter-mpi*lrwxrwxrwx 1 nmahesh nmahesh 9 Oct 18 15:34 vtfort ->
vtwrapper*-rwxr-xr-x 1 nmahesh nmahesh 9031 Oct 18 15:34
vtrun*-rwxr-xr-x 1 nmahesh nmahesh 5623609 Oct 18 15:34 vtunify*-rwxr-xr-x
1 nmahesh nmahesh 6177733 Oct 18 15:34 vtunify-mpi*-rwxr-xr-x 1 nmahesh
nmahesh 774064 Oct 18 15:34 vtwrapper**
*kindly Respond me.*
Post by Gilles Gouaillardet
Hi,
can you please give the patch below a try ?
Cheers,
Gilles
diff --git a/ompi/tools/wrappers/ompi_wrapper_script.in
b/ompi/tools/wrappers/ompi_wrapper_script.in
index d87649f..b66fec3 100644
--- a/ompi/tools/wrappers/ompi_wrapper_script.in
+++ b/ompi/tools/wrappers/ompi_wrapper_script.in
@@ -35,12 +35,12 @@ my $FC = "@FC@";
Hi everyone,
I'm trying to cross compile openmpi-1.10.3 for arm-openwrt-linux-muslgnueabi
on x86_64-linux-gnu with below configure options...
./configure --enable-orterun-prefix-by-default
--prefix="/home/nmahesh/Workspace/ARM_MPI/openmpi"
--build=x86_64-linux-gnu
--host=x86_64-linux-gnu
--target=arm-openwrt-linux-muslgnueabi
--enable-script-wrapper-compilers
--disable-mpi-fortran
--enable-shared
--disable-mmap-shmem
--disable-posix-shmem
--disable-sysv-shmem
--disable-dlopen
configuring,make &make install successfully.
I added
$export PATH="$PATH:/home/$USER/Workspace/ARM_MPI/openmpi/bin/"
$export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/home/$USER/Workspace/ARM_
MPI/openmpi/lib/"
$export PATH="$PATH:/home/$USER/Workspace/ARM_MPI/openmpi/bin/" >>
/home/$USER/.bashrc
$export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/home/$USER/Workspace/ARM_MPI/openmpi/lib/" >>
/home/$USER/.bashrc
But while compiling as below i'am getting error
*$ /home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
-L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c *
in string at /home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc line 40.
/home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc line 43.
Name "main::ORTE_WRAPPER_EXTRA_CXXFLAGS_PREFIX" used only once: possible
typo at /home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc line 40.
Name "main::libdir" used only once: possible typo at
/home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc line 43.
/home/nmahesh/Workspace/ARM_MPI/openmpi/lib/libmpi.so: file not
recognized: File format not recognized
collect2: error: ld returned 1 exit status
*can anybody help..*
_______________________________________________
_______________________________________________
users mailing list
https://rfd.newmexicoconsortium.org/mailman/listinfo/users
Mahesh Nanavalla
2016-10-18 10:30:24 UTC
Permalink
Hi all,

How to cross compile *openmpi *for* arm *on* x86_64 pc.*

*Kindly provide configure options for above...*

Thanks&regards,
Mahesh.N
Gilles Gouaillardet
2016-10-18 10:45:33 UTC
Permalink
You can try
configure --host=arm... CC=gcc_cross_compiler CXX=g++_cross_compiler

On Tuesday, October 18, 2016, Mahesh Nanavalla <
Post by Mahesh Nanavalla
Hi all,
How to cross compile *openmpi *for* arm *on* x86_64 pc.*
*Kindly provide configure options for above...*
Thanks&regards,
Mahesh.N
Kawashima, Takahiro
2016-10-18 11:39:55 UTC
Permalink
Hi,
Post by Mahesh Nanavalla
How to cross compile *openmpi *for* arm *on* x86_64 pc.*
*Kindly provide configure options for above...*
You should pass your arm architecture name to the --host option.

Example of my configure options for Open MPI, run on sparc64,
built on x86_64:

--prefix=...
--host=sparc64-unknown-linux-gnu
--build=x86_64-cross-linux-gnu
--disable-mpi-fortran
CC=your_c_cross_compiler_command
CXX=your_cxx_cross_compiler_command

If you need Fortran support, it's a bit complex. You need to
prepare a special file and pass it to the --with-cross option.

A cross mpicc command is not built automatically with the
options above. There are (at least) three options to compile
your MPI programs.

(A) Manually add -L, -I, and -l options to the cross gcc command
(or another compiler) when you compile a MPI program.
The options you should pass is written in
$installdir/share/openmpi/mpicc-wrapper-data.txt.
In most cases, -I$installdir/include -L$installdir/lib -lmpi
will be sufficient.

(B) Use the --enable-script-wrapper-compilers option on configure
time, as you tried. This method may not be maintained well
in the Open MPI team so you may encounter problems.
But you can ask them on this mailing list.

(C) Build Open MPI for x86_64 natively, copy the opal_wrapper
command, and write wrapper-data.txt file.
This is a bit complex task. I'll write the procedure on
GitHub Wiki when I have a time.
Mahesh Nanavalla
2016-10-18 12:13:52 UTC
Permalink
Hi all,

Thank you for responding me....

Below is my configure options.......

./configure --enable-orterun-prefix-by-default
--prefix="/home/nmahesh/Workspace/ARM_MPI/openmpi" \
CC=arm-openwrt-linux-muslgnueabi-gcc \
CXX=arm-openwrt-linux-muslgnueabi-g++ \
--host=arm-openwrt-linux-muslgnueabi \
--enable-script-wrapper-compilers
--disable-mpi-fortran \
--enable-shared \
--disable-mmap-shmem \
--disable-posix-shmem \
--disable-sysv-shmem \
--disable-dlopen \

it's configured ,make & make install successfully.....

i compiled *helloworld.c *programm got executable for *arm* as below(by
checking the readelf *armhelloworld*),


****@nmahesh-H81MLV3:~/Workspace/ARM_MPI/mpi$
/home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
-L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c -o armhelloworld*

***@nmahesh-H81MLV3:~/Workspace/ARM_MPI/mpi$ ls
a.out *armhelloworld * helloworld.c openmpi-1.10.3 openmpi-1.10.3.tar.gz

But ,while i run using mpirun on target board as below

****@OpenWrt:/# mpirun --allow-run-as-root -np 1 armhelloworld *





*--------------------------------------------------------------------------It
looks like opal_init failed for some reason; your parallel process islikely
to abort. There are many reasons that a parallel process canfail during
opal_init; some of which are due to configuration orenvironment problems.
This failure appears to be an internal failure;here's some additional
information (which may only be relevant to anOpen MPI developer):
opal_shmem_base_select failed --> Returned value -1 instead of
OPAL_SUCCESS--------------------------------------------------------------------------***@OpenWrt:/#
Kindly
help me.......Thanks and Regards,Mahesh .N*

On Tue, Oct 18, 2016 at 5:09 PM, Kawashima, Takahiro <
Post by Kawashima, Takahiro
Hi,
Post by Mahesh Nanavalla
How to cross compile *openmpi *for* arm *on* x86_64 pc.*
*Kindly provide configure options for above...*
You should pass your arm architecture name to the --host option.
Example of my configure options for Open MPI, run on sparc64,
--prefix=...
--host=sparc64-unknown-linux-gnu
--build=x86_64-cross-linux-gnu
--disable-mpi-fortran
CC=your_c_cross_compiler_command
CXX=your_cxx_cross_compiler_command
If you need Fortran support, it's a bit complex. You need to
prepare a special file and pass it to the --with-cross option.
A cross mpicc command is not built automatically with the
options above. There are (at least) three options to compile
your MPI programs.
(A) Manually add -L, -I, and -l options to the cross gcc command
(or another compiler) when you compile a MPI program.
The options you should pass is written in
$installdir/share/openmpi/mpicc-wrapper-data.txt.
In most cases, -I$installdir/include -L$installdir/lib -lmpi
will be sufficient.
(B) Use the --enable-script-wrapper-compilers option on configure
time, as you tried. This method may not be maintained well
in the Open MPI team so you may encounter problems.
But you can ask them on this mailing list.
(C) Build Open MPI for x86_64 natively, copy the opal_wrapper
command, and write wrapper-data.txt file.
This is a bit complex task. I'll write the procedure on
GitHub Wiki when I have a time.
_______________________________________________
users mailing list
https://rfd.newmexicoconsortium.org/mailman/listinfo/users
Mahesh Nanavalla
2016-10-18 14:02:35 UTC
Permalink
Hi Gilles,

Thank you for reply,

After doing below config options also

./configure --enable-orterun-prefix-by-default
--prefix="/home/nmahesh//home/nmahesh/Workspace/ARM_MPI/armmpi/openmpi"
CC=arm-openwrt-linux-muslgnueabi-gcc
CXX=arm-openwrt-linux-muslgnueabi-g++
--host=arm-openwrt-linux-muslgnueabi
--enable-script-wrapper-compilers
--disable-mpi-fortran
--enable-shared
--disable-dlopen

it's configured ,make & make install successfully.....

i compiled *helloworld.c *programm got executable for *arm* as below(by
checking the readelf *armhelloworld*),


****@nmahesh-H81MLV3:~/Workspace/ARM_MPI/mpi$
/home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
-L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c -o helloworld*

But ,while i run using mpirun on target board as below

***@OpenWrt:/# mpirun --allow-run-as-root -np 1 helloworld
--------------------------------------------------------------------------
It looks like opal_init failed for some reason; your parallel process is
likely to abort. There are many reasons that a parallel process can
fail during opal_init; some of which are due to configuration or
environment problems. This failure appears to be an internal failure;
here's some additional information (which may only be relevant to an
Open MPI developer):

opal_shmem_base_select failed
--> Returned value -1 instead of OPAL_SUCCESS

Kindly help me.........

On Tue, Oct 18, 2016 at 7:31 PM, Mahesh Nanavalla <
Post by Mahesh Nanavalla
Hi Gilles,
Thank you for reply,
After doing below config options also
./configure --enable-orterun-prefix-by-default
--prefix="/home/nmahesh//home/nmahesh/Workspace/ARM_MPI/armmpi/openmpi"
CC=arm-openwrt-linux-muslgnueabi-gcc
CXX=arm-openwrt-linux-muslgnueabi-g++
--host=arm-openwrt-linux-muslgnueabi
--enable-script-wrapper-compilers
--disable-mpi-fortran
--enable-shared
--disable-dlopen
it's configured ,make & make install successfully.....
i compiled *helloworld.c *programm got executable for *arm* as below(by
checking the readelf *armhelloworld*),
/home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
-L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c -o helloworld*
But ,while i run using mpirun on target board as below
--------------------------------------------------------------------------
It looks like opal_init failed for some reason; your parallel process is
likely to abort. There are many reasons that a parallel process can
fail during opal_init; some of which are due to configuration or
environment problems. This failure appears to be an internal failure;
here's some additional information (which may only be relevant to an
opal_shmem_base_select failed
--> Returned value -1 instead of OPAL_SUCCESS
Kindly help me.........
On Tue, Oct 18, 2016 at 5:51 PM, Gilles Gouaillardet <
3 shmem components are available in v1.10, and you explicitly
blacklisted all of them with
--disable-mmap-shmem \
--disable-posix-shmem \
--disable-sysv-shmem
as a consequence, Open MPI will not start.
unless you have a good reason, you should build all of them and let
the runtime decide which is best
Cheers,
Gilles
On Tue, Oct 18, 2016 at 9:13 PM, Mahesh Nanavalla
Post by Mahesh Nanavalla
Hi all,
Thank you for responding me....
Below is my configure options.......
./configure --enable-orterun-prefix-by-default
--prefix="/home/nmahesh/Workspace/ARM_MPI/openmpi" \
CC=arm-openwrt-linux-muslgnueabi-gcc \
CXX=arm-openwrt-linux-muslgnueabi-g++ \
--host=arm-openwrt-linux-muslgnueabi \
--enable-script-wrapper-compilers
--disable-mpi-fortran \
--enable-shared \
--disable-mmap-shmem \
--disable-posix-shmem \
--disable-sysv-shmem \
--disable-dlopen \
it's configured ,make & make install successfully.....
i compiled helloworld.c programm got executable for arm as below(by
checking the readelf armhelloworld),
/home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
-L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c -o
armhelloworld
Post by Mahesh Nanavalla
a.out armhelloworld helloworld.c openmpi-1.10.3
openmpi-1.10.3.tar.gz
Post by Mahesh Nanavalla
But ,while i run using mpirun on target board as below
------------------------------------------------------------
--------------
Post by Mahesh Nanavalla
It looks like opal_init failed for some reason; your parallel process is
likely to abort. There are many reasons that a parallel process can
fail during opal_init; some of which are due to configuration or
environment problems. This failure appears to be an internal failure;
here's some additional information (which may only be relevant to an
opal_shmem_base_select failed
--> Returned value -1 instead of OPAL_SUCCESS
------------------------------------------------------------
--------------
Post by Mahesh Nanavalla
Kindly help me.......
Thanks and Regards,
Mahesh .N
On Tue, Oct 18, 2016 at 5:09 PM, Kawashima, Takahiro
Post by Kawashima, Takahiro
Hi,
Post by Mahesh Nanavalla
How to cross compile *openmpi *for* arm *on* x86_64 pc.*
*Kindly provide configure options for above...*
You should pass your arm architecture name to the --host option.
Example of my configure options for Open MPI, run on sparc64,
--prefix=...
--host=sparc64-unknown-linux-gnu
--build=x86_64-cross-linux-gnu
--disable-mpi-fortran
CC=your_c_cross_compiler_command
CXX=your_cxx_cross_compiler_command
If you need Fortran support, it's a bit complex. You need to
prepare a special file and pass it to the --with-cross option.
A cross mpicc command is not built automatically with the
options above. There are (at least) three options to compile
your MPI programs.
(A) Manually add -L, -I, and -l options to the cross gcc command
(or another compiler) when you compile a MPI program.
The options you should pass is written in
$installdir/share/openmpi/mpicc-wrapper-data.txt.
In most cases, -I$installdir/include -L$installdir/lib -lmpi
will be sufficient.
(B) Use the --enable-script-wrapper-compilers option on configure
time, as you tried. This method may not be maintained well
in the Open MPI team so you may encounter problems.
But you can ask them on this mailing list.
(C) Build Open MPI for x86_64 natively, copy the opal_wrapper
command, and write wrapper-data.txt file.
This is a bit complex task. I'll write the procedure on
GitHub Wiki when I have a time.
_______________________________________________
users mailing list
https://rfd.newmexicoconsortium.org/mailman/listinfo/users
Kawashima, Takahiro
2016-10-18 14:53:51 UTC
Permalink
Hi,

You did *not* specify the following options to configure, right?
Specifying all these will cause a problem.

--disable-mmap-shmem
--disable-posix-shmem
--disable-sysv-shmem

Please send the output of the following command.

mpirun --allow-run-as-root -np 1 --mca shmem_base_verbose 100 helloworld

And, give us the config.log file which is output in the
top directory where configure is executed.
Put it on the web or send the compressed (xz or bzip2 is better) file.

Regards,
Takahiro Kawashima
Post by Mahesh Nanavalla
Hi Gilles,
Thank you for reply,
After doing below config options also
./configure --enable-orterun-prefix-by-default
--prefix="/home/nmahesh//home/nmahesh/Workspace/ARM_MPI/armmpi/openmpi"
CC=arm-openwrt-linux-muslgnueabi-gcc
CXX=arm-openwrt-linux-muslgnueabi-g++
--host=arm-openwrt-linux-muslgnueabi
--enable-script-wrapper-compilers
--disable-mpi-fortran
--enable-shared
--disable-dlopen
it's configured ,make & make install successfully.....
i compiled *helloworld.c *programm got executable for *arm* as below(by
checking the readelf *armhelloworld*),
/home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
-L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c -o helloworld*
But ,while i run using mpirun on target board as below
--------------------------------------------------------------------------
It looks like opal_init failed for some reason; your parallel process is
likely to abort. There are many reasons that a parallel process can
fail during opal_init; some of which are due to configuration or
environment problems. This failure appears to be an internal failure;
here's some additional information (which may only be relevant to an
opal_shmem_base_select failed
--> Returned value -1 instead of OPAL_SUCCESS
Kindly help me.........
On Tue, Oct 18, 2016 at 7:31 PM, Mahesh Nanavalla <
Post by Mahesh Nanavalla
Hi Gilles,
Thank you for reply,
After doing below config options also
./configure --enable-orterun-prefix-by-default
--prefix="/home/nmahesh//home/nmahesh/Workspace/ARM_MPI/armmpi/openmpi"
CC=arm-openwrt-linux-muslgnueabi-gcc
CXX=arm-openwrt-linux-muslgnueabi-g++
--host=arm-openwrt-linux-muslgnueabi
--enable-script-wrapper-compilers
--disable-mpi-fortran
--enable-shared
--disable-dlopen
it's configured ,make & make install successfully.....
i compiled *helloworld.c *programm got executable for *arm* as below(by
checking the readelf *armhelloworld*),
/home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
-L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c -o helloworld*
But ,while i run using mpirun on target board as below
--------------------------------------------------------------------------
It looks like opal_init failed for some reason; your parallel process is
likely to abort. There are many reasons that a parallel process can
fail during opal_init; some of which are due to configuration or
environment problems. This failure appears to be an internal failure;
here's some additional information (which may only be relevant to an
opal_shmem_base_select failed
--> Returned value -1 instead of OPAL_SUCCESS
Kindly help me.........
On Tue, Oct 18, 2016 at 5:51 PM, Gilles Gouaillardet <
3 shmem components are available in v1.10, and you explicitly
blacklisted all of them with
--disable-mmap-shmem \
--disable-posix-shmem \
--disable-sysv-shmem
as a consequence, Open MPI will not start.
unless you have a good reason, you should build all of them and let
the runtime decide which is best
Cheers,
Gilles
On Tue, Oct 18, 2016 at 9:13 PM, Mahesh Nanavalla
Post by Mahesh Nanavalla
Hi all,
Thank you for responding me....
Below is my configure options.......
./configure --enable-orterun-prefix-by-default
--prefix="/home/nmahesh/Workspace/ARM_MPI/openmpi" \
CC=arm-openwrt-linux-muslgnueabi-gcc \
CXX=arm-openwrt-linux-muslgnueabi-g++ \
--host=arm-openwrt-linux-muslgnueabi \
--enable-script-wrapper-compilers
--disable-mpi-fortran \
--enable-shared \
--disable-mmap-shmem \
--disable-posix-shmem \
--disable-sysv-shmem \
--disable-dlopen \
it's configured ,make & make install successfully.....
i compiled helloworld.c programm got executable for arm as below(by
checking the readelf armhelloworld),
/home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
-L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c -o
armhelloworld
Post by Mahesh Nanavalla
a.out armhelloworld helloworld.c openmpi-1.10.3
openmpi-1.10.3.tar.gz
Post by Mahesh Nanavalla
But ,while i run using mpirun on target board as below
------------------------------------------------------------
--------------
Post by Mahesh Nanavalla
It looks like opal_init failed for some reason; your parallel process is
likely to abort. There are many reasons that a parallel process can
fail during opal_init; some of which are due to configuration or
environment problems. This failure appears to be an internal failure;
here's some additional information (which may only be relevant to an
opal_shmem_base_select failed
--> Returned value -1 instead of OPAL_SUCCESS
------------------------------------------------------------
--------------
Post by Mahesh Nanavalla
Kindly help me.......
Thanks and Regards,
Mahesh .N
On Tue, Oct 18, 2016 at 5:09 PM, Kawashima, Takahiro
Post by Kawashima, Takahiro
Hi,
Post by Mahesh Nanavalla
How to cross compile *openmpi *for* arm *on* x86_64 pc.*
*Kindly provide configure options for above...*
You should pass your arm architecture name to the --host option.
Example of my configure options for Open MPI, run on sparc64,
--prefix=...
--host=sparc64-unknown-linux-gnu
--build=x86_64-cross-linux-gnu
--disable-mpi-fortran
CC=your_c_cross_compiler_command
CXX=your_cxx_cross_compiler_command
If you need Fortran support, it's a bit complex. You need to
prepare a special file and pass it to the --with-cross option.
A cross mpicc command is not built automatically with the
options above. There are (at least) three options to compile
your MPI programs.
(A) Manually add -L, -I, and -l options to the cross gcc command
(or another compiler) when you compile a MPI program.
The options you should pass is written in
$installdir/share/openmpi/mpicc-wrapper-data.txt.
In most cases, -I$installdir/include -L$installdir/lib -lmpi
will be sufficient.
(B) Use the --enable-script-wrapper-compilers option on configure
time, as you tried. This method may not be maintained well
in the Open MPI team so you may encounter problems.
But you can ask them on this mailing list.
(C) Build Open MPI for x86_64 natively, copy the opal_wrapper
command, and write wrapper-data.txt file.
This is a bit complex task. I'll write the procedure on
GitHub Wiki when I have a time.
Mahesh Nanavalla
2016-10-19 06:41:54 UTC
Permalink
Hi all

it's working.........

I forget to copy all openmpi libs and bin to target board....

Now it's working fine.......

Thank u all.........

Thank u very much for your support....

***@OpenWrt:/# cp /openmpi/lib/libopen-rte.so.12 /usr/lib/
***@OpenWrt:/# cp /openmpi/lib/libopen-pal.so.13 /usr/lib/
***@OpenWrt:/# /openmpi/bin/mpirun -np 1 helloworld
--------------------------------------------------------------------------
mpirun has detected an attempt to run as root.
Running at root is *strongly* discouraged as any mistake (e.g., in
defining TMPDIR) or bug can result in catastrophic damage to the OS
file system, leaving your system in an unusable state.

You can override this protection by adding the --allow-run-as-root
option to your cmd line. However, we reiterate our strong advice
against doing so - please do so at your own risk.
--------------------------------------------------------------------------
***@OpenWrt:/# /openmpi/bin/mpirun --allow-run-as-root -np 1 helloworld
Hello world from processor OpenWrt, rank 0 1
***@OpenWrt:/# /openmpi/bin/mpirun --allow-run-as-root -np 2 helloworld
Hello world from processor OpenWrt, rank 1 2
Hello world from processor OpenWrt, rank 0 2
***@OpenWrt:/# /openmpi/bin/mpirun --allow-run-as-root -np 4 helloworld
Hello world from processor OpenWrt, rank 0 4
Hello world from processor OpenWrt, rank 2 4
Hello world from processor OpenWrt, rank 3 4
Hello world from processor OpenWrt, rank 1 4


On Tue, Oct 18, 2016 at 8:23 PM, Kawashima, Takahiro <
Post by Kawashima, Takahiro
Hi,
You did *not* specify the following options to configure, right?
Specifying all these will cause a problem.
--disable-mmap-shmem
--disable-posix-shmem
--disable-sysv-shmem
Please send the output of the following command.
mpirun --allow-run-as-root -np 1 --mca shmem_base_verbose 100 helloworld
And, give us the config.log file which is output in the
top directory where configure is executed.
Put it on the web or send the compressed (xz or bzip2 is better) file.
Regards,
Takahiro Kawashima
Post by Mahesh Nanavalla
Hi Gilles,
Thank you for reply,
After doing below config options also
./configure --enable-orterun-prefix-by-default
--prefix="/home/nmahesh//home/nmahesh/Workspace/ARM_MPI/armmpi/openmpi"
CC=arm-openwrt-linux-muslgnueabi-gcc
CXX=arm-openwrt-linux-muslgnueabi-g++
--host=arm-openwrt-linux-muslgnueabi
--enable-script-wrapper-compilers
--disable-mpi-fortran
--enable-shared
--disable-dlopen
it's configured ,make & make install successfully.....
i compiled *helloworld.c *programm got executable for *arm* as below(by
checking the readelf *armhelloworld*),
/home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
-L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c -o
helloworld*
Post by Mahesh Nanavalla
But ,while i run using mpirun on target board as below
------------------------------------------------------------
--------------
Post by Mahesh Nanavalla
It looks like opal_init failed for some reason; your parallel process is
likely to abort. There are many reasons that a parallel process can
fail during opal_init; some of which are due to configuration or
environment problems. This failure appears to be an internal failure;
here's some additional information (which may only be relevant to an
opal_shmem_base_select failed
--> Returned value -1 instead of OPAL_SUCCESS
Kindly help me.........
On Tue, Oct 18, 2016 at 7:31 PM, Mahesh Nanavalla <
Post by Mahesh Nanavalla
Hi Gilles,
Thank you for reply,
After doing below config options also
./configure --enable-orterun-prefix-by-default
--prefix="/home/nmahesh//home/nmahesh/Workspace/ARM_MPI/
armmpi/openmpi"
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
CC=arm-openwrt-linux-muslgnueabi-gcc
CXX=arm-openwrt-linux-muslgnueabi-g++
--host=arm-openwrt-linux-muslgnueabi
--enable-script-wrapper-compilers
--disable-mpi-fortran
--enable-shared
--disable-dlopen
it's configured ,make & make install successfully.....
i compiled *helloworld.c *programm got executable for *arm* as
below(by
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
checking the readelf *armhelloworld*),
/home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
-L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c -o
helloworld*
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
But ,while i run using mpirun on target board as below
------------------------------------------------------------
--------------
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
It looks like opal_init failed for some reason; your parallel process
is
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
likely to abort. There are many reasons that a parallel process can
fail during opal_init; some of which are due to configuration or
environment problems. This failure appears to be an internal failure;
here's some additional information (which may only be relevant to an
opal_shmem_base_select failed
--> Returned value -1 instead of OPAL_SUCCESS
Kindly help me.........
On Tue, Oct 18, 2016 at 5:51 PM, Gilles Gouaillardet <
3 shmem components are available in v1.10, and you explicitly
blacklisted all of them with
--disable-mmap-shmem \
--disable-posix-shmem \
--disable-sysv-shmem
as a consequence, Open MPI will not start.
unless you have a good reason, you should build all of them and let
the runtime decide which is best
Cheers,
Gilles
On Tue, Oct 18, 2016 at 9:13 PM, Mahesh Nanavalla
Post by Mahesh Nanavalla
Hi all,
Thank you for responding me....
Below is my configure options.......
./configure --enable-orterun-prefix-by-default
--prefix="/home/nmahesh/Workspace/ARM_MPI/openmpi" \
CC=arm-openwrt-linux-muslgnueabi-gcc \
CXX=arm-openwrt-linux-muslgnueabi-g++ \
--host=arm-openwrt-linux-muslgnueabi \
--enable-script-wrapper-compilers
--disable-mpi-fortran \
--enable-shared \
--disable-mmap-shmem \
--disable-posix-shmem \
--disable-sysv-shmem \
--disable-dlopen \
it's configured ,make & make install successfully.....
i compiled helloworld.c programm got executable for arm as below(by
checking the readelf armhelloworld),
/home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
-L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c -o
armhelloworld
Post by Mahesh Nanavalla
a.out armhelloworld helloworld.c openmpi-1.10.3
openmpi-1.10.3.tar.gz
Post by Mahesh Nanavalla
But ,while i run using mpirun on target board as below
------------------------------------------------------------
--------------
Post by Mahesh Nanavalla
It looks like opal_init failed for some reason; your parallel
process is
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
likely to abort. There are many reasons that a parallel process can
fail during opal_init; some of which are due to configuration or
environment problems. This failure appears to be an internal
failure;
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
here's some additional information (which may only be relevant to an
opal_shmem_base_select failed
--> Returned value -1 instead of OPAL_SUCCESS
------------------------------------------------------------
--------------
Post by Mahesh Nanavalla
Kindly help me.......
Thanks and Regards,
Mahesh .N
On Tue, Oct 18, 2016 at 5:09 PM, Kawashima, Takahiro
Post by Kawashima, Takahiro
Hi,
Post by Mahesh Nanavalla
How to cross compile *openmpi *for* arm *on* x86_64 pc.*
*Kindly provide configure options for above...*
You should pass your arm architecture name to the --host option.
Example of my configure options for Open MPI, run on sparc64,
--prefix=...
--host=sparc64-unknown-linux-gnu
--build=x86_64-cross-linux-gnu
--disable-mpi-fortran
CC=your_c_cross_compiler_command
CXX=your_cxx_cross_compiler_command
If you need Fortran support, it's a bit complex. You need to
prepare a special file and pass it to the --with-cross option.
A cross mpicc command is not built automatically with the
options above. There are (at least) three options to compile
your MPI programs.
(A) Manually add -L, -I, and -l options to the cross gcc command
(or another compiler) when you compile a MPI program.
The options you should pass is written in
$installdir/share/openmpi/mpicc-wrapper-data.txt.
In most cases, -I$installdir/include -L$installdir/lib -lmpi
will be sufficient.
(B) Use the --enable-script-wrapper-compilers option on configure
time, as you tried. This method may not be maintained well
in the Open MPI team so you may encounter problems.
But you can ask them on this mailing list.
(C) Build Open MPI for x86_64 natively, copy the opal_wrapper
command, and write wrapper-data.txt file.
This is a bit complex task. I'll write the procedure on
GitHub Wiki when I have a time.
_______________________________________________
users mailing list
https://rfd.newmexicoconsortium.org/mailman/listinfo/users
Mahesh Nanavalla
2016-10-19 10:28:52 UTC
Permalink
Hi all,

can any one tell purpose and importance of *--disable-vt*

*Thanks&Regards,*
*Mahesh.N*

On Wed, Oct 19, 2016 at 12:11 PM, Mahesh Nanavalla <
Post by Mahesh Nanavalla
Hi all
it's working.........
I forget to copy all openmpi libs and bin to target board....
Now it's working fine.......
Thank u all.........
Thank u very much for your support....
--------------------------------------------------------------------------
mpirun has detected an attempt to run as root.
Running at root is *strongly* discouraged as any mistake (e.g., in
defining TMPDIR) or bug can result in catastrophic damage to the OS
file system, leaving your system in an unusable state.
You can override this protection by adding the --allow-run-as-root
option to your cmd line. However, we reiterate our strong advice
against doing so - please do so at your own risk.
--------------------------------------------------------------------------
Hello world from processor OpenWrt, rank 0 1
Hello world from processor OpenWrt, rank 1 2
Hello world from processor OpenWrt, rank 0 2
Hello world from processor OpenWrt, rank 0 4
Hello world from processor OpenWrt, rank 2 4
Hello world from processor OpenWrt, rank 3 4
Hello world from processor OpenWrt, rank 1 4
On Tue, Oct 18, 2016 at 8:23 PM, Kawashima, Takahiro <
Post by Kawashima, Takahiro
Hi,
You did *not* specify the following options to configure, right?
Specifying all these will cause a problem.
--disable-mmap-shmem
--disable-posix-shmem
--disable-sysv-shmem
Please send the output of the following command.
mpirun --allow-run-as-root -np 1 --mca shmem_base_verbose 100 helloworld
And, give us the config.log file which is output in the
top directory where configure is executed.
Put it on the web or send the compressed (xz or bzip2 is better) file.
Regards,
Takahiro Kawashima
Post by Mahesh Nanavalla
Hi Gilles,
Thank you for reply,
After doing below config options also
./configure --enable-orterun-prefix-by-default
--prefix="/home/nmahesh//home/nmahesh/Workspace/ARM_MPI/armmpi/openmpi"
CC=arm-openwrt-linux-muslgnueabi-gcc
CXX=arm-openwrt-linux-muslgnueabi-g++
--host=arm-openwrt-linux-muslgnueabi
--enable-script-wrapper-compilers
--disable-mpi-fortran
--enable-shared
--disable-dlopen
it's configured ,make & make install successfully.....
i compiled *helloworld.c *programm got executable for *arm* as below(by
checking the readelf *armhelloworld*),
/home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
-L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c -o
helloworld*
Post by Mahesh Nanavalla
But ,while i run using mpirun on target board as below
------------------------------------------------------------
--------------
Post by Mahesh Nanavalla
It looks like opal_init failed for some reason; your parallel process is
likely to abort. There are many reasons that a parallel process can
fail during opal_init; some of which are due to configuration or
environment problems. This failure appears to be an internal failure;
here's some additional information (which may only be relevant to an
opal_shmem_base_select failed
--> Returned value -1 instead of OPAL_SUCCESS
Kindly help me.........
On Tue, Oct 18, 2016 at 7:31 PM, Mahesh Nanavalla <
Post by Mahesh Nanavalla
Hi Gilles,
Thank you for reply,
After doing below config options also
./configure --enable-orterun-prefix-by-default
--prefix="/home/nmahesh//home/nmahesh/Workspace/ARM_MPI/armm
pi/openmpi"
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
CC=arm-openwrt-linux-muslgnueabi-gcc
CXX=arm-openwrt-linux-muslgnueabi-g++
--host=arm-openwrt-linux-muslgnueabi
--enable-script-wrapper-compilers
--disable-mpi-fortran
--enable-shared
--disable-dlopen
it's configured ,make & make install successfully.....
i compiled *helloworld.c *programm got executable for *arm* as
below(by
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
checking the readelf *armhelloworld*),
/home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
-L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c -o
helloworld*
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
But ,while i run using mpirun on target board as below
------------------------------------------------------------
--------------
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
It looks like opal_init failed for some reason; your parallel process
is
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
likely to abort. There are many reasons that a parallel process can
fail during opal_init; some of which are due to configuration or
environment problems. This failure appears to be an internal failure;
here's some additional information (which may only be relevant to an
opal_shmem_base_select failed
--> Returned value -1 instead of OPAL_SUCCESS
Kindly help me.........
On Tue, Oct 18, 2016 at 5:51 PM, Gilles Gouaillardet <
3 shmem components are available in v1.10, and you explicitly
blacklisted all of them with
--disable-mmap-shmem \
--disable-posix-shmem \
--disable-sysv-shmem
as a consequence, Open MPI will not start.
unless you have a good reason, you should build all of them and let
the runtime decide which is best
Cheers,
Gilles
On Tue, Oct 18, 2016 at 9:13 PM, Mahesh Nanavalla
Post by Mahesh Nanavalla
Hi all,
Thank you for responding me....
Below is my configure options.......
./configure --enable-orterun-prefix-by-default
--prefix="/home/nmahesh/Workspace/ARM_MPI/openmpi" \
CC=arm-openwrt-linux-muslgnueabi-gcc \
CXX=arm-openwrt-linux-muslgnueabi-g++ \
--host=arm-openwrt-linux-muslgnueabi \
--enable-script-wrapper-compilers
--disable-mpi-fortran \
--enable-shared \
--disable-mmap-shmem \
--disable-posix-shmem \
--disable-sysv-shmem \
--disable-dlopen \
it's configured ,make & make install successfully.....
i compiled helloworld.c programm got executable for arm as
below(by
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
checking the readelf armhelloworld),
/home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
-L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c -o
armhelloworld
Post by Mahesh Nanavalla
a.out armhelloworld helloworld.c openmpi-1.10.3
openmpi-1.10.3.tar.gz
Post by Mahesh Nanavalla
But ,while i run using mpirun on target board as below
------------------------------------------------------------
--------------
Post by Mahesh Nanavalla
It looks like opal_init failed for some reason; your parallel
process is
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
likely to abort. There are many reasons that a parallel process
can
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
fail during opal_init; some of which are due to configuration or
environment problems. This failure appears to be an internal
failure;
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
here's some additional information (which may only be relevant to
an
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
opal_shmem_base_select failed
--> Returned value -1 instead of OPAL_SUCCESS
------------------------------------------------------------
--------------
Post by Mahesh Nanavalla
Kindly help me.......
Thanks and Regards,
Mahesh .N
On Tue, Oct 18, 2016 at 5:09 PM, Kawashima, Takahiro
Post by Kawashima, Takahiro
Hi,
Post by Mahesh Nanavalla
How to cross compile *openmpi *for* arm *on* x86_64 pc.*
*Kindly provide configure options for above...*
You should pass your arm architecture name to the --host option.
Example of my configure options for Open MPI, run on sparc64,
--prefix=...
--host=sparc64-unknown-linux-gnu
--build=x86_64-cross-linux-gnu
--disable-mpi-fortran
CC=your_c_cross_compiler_command
CXX=your_cxx_cross_compiler_command
If you need Fortran support, it's a bit complex. You need to
prepare a special file and pass it to the --with-cross option.
A cross mpicc command is not built automatically with the
options above. There are (at least) three options to compile
your MPI programs.
(A) Manually add -L, -I, and -l options to the cross gcc command
(or another compiler) when you compile a MPI program.
The options you should pass is written in
$installdir/share/openmpi/mpicc-wrapper-data.txt.
In most cases, -I$installdir/include -L$installdir/lib -lmpi
will be sufficient.
(B) Use the --enable-script-wrapper-compilers option on configure
time, as you tried. This method may not be maintained well
in the Open MPI team so you may encounter problems.
But you can ask them on this mailing list.
(C) Build Open MPI for x86_64 natively, copy the opal_wrapper
command, and write wrapper-data.txt file.
This is a bit complex task. I'll write the procedure on
GitHub Wiki when I have a time.
_______________________________________________
users mailing list
https://rfd.newmexicoconsortium.org/mailman/listinfo/users
Gilles Gouaillardet
2016-10-19 10:36:24 UTC
Permalink
vt is a contrib that produces traces to be used by VaMPIr
IIRC, this has been removed from Open MPI starting v2.0.0

Worst case scenario is it will fail to build, and most likely case is you
do not need it, so you can save some build time with --disable-vet

Cheers,

Gilles

On Wednesday, October 19, 2016, Mahesh Nanavalla <
Post by Mahesh Nanavalla
Hi all,
can any one tell purpose and importance of *--disable-vt*
*Thanks&Regards,*
*Mahesh.N*
On Wed, Oct 19, 2016 at 12:11 PM, Mahesh Nanavalla <
Post by Mahesh Nanavalla
Hi all
it's working.........
I forget to copy all openmpi libs and bin to target board....
Now it's working fine.......
Thank u all.........
Thank u very much for your support....
------------------------------------------------------------
--------------
mpirun has detected an attempt to run as root.
Running at root is *strongly* discouraged as any mistake (e.g., in
defining TMPDIR) or bug can result in catastrophic damage to the OS
file system, leaving your system in an unusable state.
You can override this protection by adding the --allow-run-as-root
option to your cmd line. However, we reiterate our strong advice
against doing so - please do so at your own risk.
------------------------------------------------------------
--------------
Hello world from processor OpenWrt, rank 0 1
Hello world from processor OpenWrt, rank 1 2
Hello world from processor OpenWrt, rank 0 2
Hello world from processor OpenWrt, rank 0 4
Hello world from processor OpenWrt, rank 2 4
Hello world from processor OpenWrt, rank 3 4
Hello world from processor OpenWrt, rank 1 4
On Tue, Oct 18, 2016 at 8:23 PM, Kawashima, Takahiro <
Post by Kawashima, Takahiro
Hi,
You did *not* specify the following options to configure, right?
Specifying all these will cause a problem.
--disable-mmap-shmem
--disable-posix-shmem
--disable-sysv-shmem
Please send the output of the following command.
mpirun --allow-run-as-root -np 1 --mca shmem_base_verbose 100 helloworld
And, give us the config.log file which is output in the
top directory where configure is executed.
Put it on the web or send the compressed (xz or bzip2 is better) file.
Regards,
Takahiro Kawashima
Post by Mahesh Nanavalla
Hi Gilles,
Thank you for reply,
After doing below config options also
./configure --enable-orterun-prefix-by-default
--prefix="/home/nmahesh//home/nmahesh/Workspace/ARM_MPI/armm
pi/openmpi"
Post by Mahesh Nanavalla
CC=arm-openwrt-linux-muslgnueabi-gcc
CXX=arm-openwrt-linux-muslgnueabi-g++
--host=arm-openwrt-linux-muslgnueabi
--enable-script-wrapper-compilers
--disable-mpi-fortran
--enable-shared
--disable-dlopen
it's configured ,make & make install successfully.....
i compiled *helloworld.c *programm got executable for *arm* as
below(by
Post by Mahesh Nanavalla
checking the readelf *armhelloworld*),
/home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
-L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c -o
helloworld*
Post by Mahesh Nanavalla
But ,while i run using mpirun on target board as below
------------------------------------------------------------
--------------
Post by Mahesh Nanavalla
It looks like opal_init failed for some reason; your parallel process
is
Post by Mahesh Nanavalla
likely to abort. There are many reasons that a parallel process can
fail during opal_init; some of which are due to configuration or
environment problems. This failure appears to be an internal failure;
here's some additional information (which may only be relevant to an
opal_shmem_base_select failed
--> Returned value -1 instead of OPAL_SUCCESS
Kindly help me.........
On Tue, Oct 18, 2016 at 7:31 PM, Mahesh Nanavalla <
Post by Mahesh Nanavalla
Hi Gilles,
Thank you for reply,
After doing below config options also
./configure --enable-orterun-prefix-by-default
--prefix="/home/nmahesh//home/nmahesh/Workspace/ARM_MPI/armm
pi/openmpi"
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
CC=arm-openwrt-linux-muslgnueabi-gcc
CXX=arm-openwrt-linux-muslgnueabi-g++
--host=arm-openwrt-linux-muslgnueabi
--enable-script-wrapper-compilers
--disable-mpi-fortran
--enable-shared
--disable-dlopen
it's configured ,make & make install successfully.....
i compiled *helloworld.c *programm got executable for *arm* as
below(by
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
checking the readelf *armhelloworld*),
/home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
-L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c -o
helloworld*
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
But ,while i run using mpirun on target board as below
------------------------------------------------------------
--------------
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
It looks like opal_init failed for some reason; your parallel
process is
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
likely to abort. There are many reasons that a parallel process can
fail during opal_init; some of which are due to configuration or
environment problems. This failure appears to be an internal
failure;
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
here's some additional information (which may only be relevant to an
opal_shmem_base_select failed
--> Returned value -1 instead of OPAL_SUCCESS
Kindly help me.........
On Tue, Oct 18, 2016 at 5:51 PM, Gilles Gouaillardet <
3 shmem components are available in v1.10, and you explicitly
blacklisted all of them with
--disable-mmap-shmem \
--disable-posix-shmem \
--disable-sysv-shmem
as a consequence, Open MPI will not start.
unless you have a good reason, you should build all of them and let
the runtime decide which is best
Cheers,
Gilles
On Tue, Oct 18, 2016 at 9:13 PM, Mahesh Nanavalla
Post by Mahesh Nanavalla
Hi all,
Thank you for responding me....
Below is my configure options.......
./configure --enable-orterun-prefix-by-default
--prefix="/home/nmahesh/Workspace/ARM_MPI/openmpi" \
CC=arm-openwrt-linux-muslgnueabi-gcc \
CXX=arm-openwrt-linux-muslgnueabi-g++ \
--host=arm-openwrt-linux-muslgnueabi \
--enable-script-wrapper-compilers
--disable-mpi-fortran \
--enable-shared \
--disable-mmap-shmem \
--disable-posix-shmem \
--disable-sysv-shmem \
--disable-dlopen \
it's configured ,make & make install successfully.....
i compiled helloworld.c programm got executable for arm as
below(by
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
checking the readelf armhelloworld),
/home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
-L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c -o
armhelloworld
Post by Mahesh Nanavalla
a.out armhelloworld helloworld.c openmpi-1.10.3
openmpi-1.10.3.tar.gz
Post by Mahesh Nanavalla
But ,while i run using mpirun on target board as below
------------------------------------------------------------
--------------
Post by Mahesh Nanavalla
It looks like opal_init failed for some reason; your parallel
process is
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
likely to abort. There are many reasons that a parallel process
can
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
fail during opal_init; some of which are due to configuration or
environment problems. This failure appears to be an internal
failure;
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
here's some additional information (which may only be relevant to
an
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
opal_shmem_base_select failed
--> Returned value -1 instead of OPAL_SUCCESS
------------------------------------------------------------
--------------
Post by Mahesh Nanavalla
Kindly help me.......
Thanks and Regards,
Mahesh .N
On Tue, Oct 18, 2016 at 5:09 PM, Kawashima, Takahiro
Post by Kawashima, Takahiro
Hi,
Post by Mahesh Nanavalla
How to cross compile *openmpi *for* arm *on* x86_64 pc.*
*Kindly provide configure options for above...*
You should pass your arm architecture name to the --host option.
Example of my configure options for Open MPI, run on sparc64,
--prefix=...
--host=sparc64-unknown-linux-gnu
--build=x86_64-cross-linux-gnu
--disable-mpi-fortran
CC=your_c_cross_compiler_command
CXX=your_cxx_cross_compiler_command
If you need Fortran support, it's a bit complex. You need to
prepare a special file and pass it to the --with-cross option.
A cross mpicc command is not built automatically with the
options above. There are (at least) three options to compile
your MPI programs.
(A) Manually add -L, -I, and -l options to the cross gcc command
(or another compiler) when you compile a MPI program.
The options you should pass is written in
$installdir/share/openmpi/mpicc-wrapper-data.txt.
In most cases, -I$installdir/include -L$installdir/lib -lmpi
will be sufficient.
(B) Use the --enable-script-wrapper-compilers option on
configure
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Kawashima, Takahiro
time, as you tried. This method may not be maintained well
in the Open MPI team so you may encounter problems.
But you can ask them on this mailing list.
(C) Build Open MPI for x86_64 natively, copy the opal_wrapper
command, and write wrapper-data.txt file.
This is a bit complex task. I'll write the procedure on
GitHub Wiki when I have a time.
_______________________________________________
users mailing list
https://rfd.newmexicoconsortium.org/mailman/listinfo/users
Mahesh Nanavalla
2016-10-19 11:00:02 UTC
Permalink
Hi Gilles,

Thanks for reply,

If i do *--disable-vt *while configuring the openmpi-1.10.3 ,

the size of the installation directory reduced 70MB to 9MB.

will it effect anything........?


On Wed, Oct 19, 2016 at 4:06 PM, Gilles Gouaillardet <
Post by Gilles Gouaillardet
vt is a contrib that produces traces to be used by VaMPIr
IIRC, this has been removed from Open MPI starting v2.0.0
Worst case scenario is it will fail to build, and most likely case is you
do not need it, so you can save some build time with --disable-vet
Cheers,
Gilles
On Wednesday, October 19, 2016, Mahesh Nanavalla <
Post by Mahesh Nanavalla
Hi all,
can any one tell purpose and importance of *--disable-vt*
*Thanks&Regards,*
*Mahesh.N*
On Wed, Oct 19, 2016 at 12:11 PM, Mahesh Nanavalla <
Post by Mahesh Nanavalla
Hi all
it's working.........
I forget to copy all openmpi libs and bin to target board....
Now it's working fine.......
Thank u all.........
Thank u very much for your support....
------------------------------------------------------------
--------------
mpirun has detected an attempt to run as root.
Running at root is *strongly* discouraged as any mistake (e.g., in
defining TMPDIR) or bug can result in catastrophic damage to the OS
file system, leaving your system in an unusable state.
You can override this protection by adding the --allow-run-as-root
option to your cmd line. However, we reiterate our strong advice
against doing so - please do so at your own risk.
------------------------------------------------------------
--------------
Hello world from processor OpenWrt, rank 0 1
Hello world from processor OpenWrt, rank 1 2
Hello world from processor OpenWrt, rank 0 2
Hello world from processor OpenWrt, rank 0 4
Hello world from processor OpenWrt, rank 2 4
Hello world from processor OpenWrt, rank 3 4
Hello world from processor OpenWrt, rank 1 4
On Tue, Oct 18, 2016 at 8:23 PM, Kawashima, Takahiro <
Post by Kawashima, Takahiro
Hi,
You did *not* specify the following options to configure, right?
Specifying all these will cause a problem.
--disable-mmap-shmem
--disable-posix-shmem
--disable-sysv-shmem
Please send the output of the following command.
mpirun --allow-run-as-root -np 1 --mca shmem_base_verbose 100 helloworld
And, give us the config.log file which is output in the
top directory where configure is executed.
Put it on the web or send the compressed (xz or bzip2 is better) file.
Regards,
Takahiro Kawashima
Post by Mahesh Nanavalla
Hi Gilles,
Thank you for reply,
After doing below config options also
./configure --enable-orterun-prefix-by-default
--prefix="/home/nmahesh//home/nmahesh/Workspace/ARM_MPI/armm
pi/openmpi"
Post by Mahesh Nanavalla
CC=arm-openwrt-linux-muslgnueabi-gcc
CXX=arm-openwrt-linux-muslgnueabi-g++
--host=arm-openwrt-linux-muslgnueabi
--enable-script-wrapper-compilers
--disable-mpi-fortran
--enable-shared
--disable-dlopen
it's configured ,make & make install successfully.....
i compiled *helloworld.c *programm got executable for *arm* as
below(by
Post by Mahesh Nanavalla
checking the readelf *armhelloworld*),
/home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
-L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c -o
helloworld*
Post by Mahesh Nanavalla
But ,while i run using mpirun on target board as below
------------------------------------------------------------
--------------
Post by Mahesh Nanavalla
It looks like opal_init failed for some reason; your parallel process
is
Post by Mahesh Nanavalla
likely to abort. There are many reasons that a parallel process can
fail during opal_init; some of which are due to configuration or
environment problems. This failure appears to be an internal failure;
here's some additional information (which may only be relevant to an
opal_shmem_base_select failed
--> Returned value -1 instead of OPAL_SUCCESS
Kindly help me.........
On Tue, Oct 18, 2016 at 7:31 PM, Mahesh Nanavalla <
Post by Mahesh Nanavalla
Hi Gilles,
Thank you for reply,
After doing below config options also
./configure --enable-orterun-prefix-by-default
--prefix="/home/nmahesh//home/nmahesh/Workspace/ARM_MPI/armm
pi/openmpi"
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
CC=arm-openwrt-linux-muslgnueabi-gcc
CXX=arm-openwrt-linux-muslgnueabi-g++
--host=arm-openwrt-linux-muslgnueabi
--enable-script-wrapper-compilers
--disable-mpi-fortran
--enable-shared
--disable-dlopen
it's configured ,make & make install successfully.....
i compiled *helloworld.c *programm got executable for *arm* as
below(by
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
checking the readelf *armhelloworld*),
/home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
-L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c -o
helloworld*
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
But ,while i run using mpirun on target board as below
------------------------------------------------------------
--------------
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
It looks like opal_init failed for some reason; your parallel
process is
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
likely to abort. There are many reasons that a parallel process can
fail during opal_init; some of which are due to configuration or
environment problems. This failure appears to be an internal
failure;
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
here's some additional information (which may only be relevant to an
opal_shmem_base_select failed
--> Returned value -1 instead of OPAL_SUCCESS
Kindly help me.........
On Tue, Oct 18, 2016 at 5:51 PM, Gilles Gouaillardet <
3 shmem components are available in v1.10, and you explicitly
blacklisted all of them with
--disable-mmap-shmem \
--disable-posix-shmem \
--disable-sysv-shmem
as a consequence, Open MPI will not start.
unless you have a good reason, you should build all of them and let
the runtime decide which is best
Cheers,
Gilles
On Tue, Oct 18, 2016 at 9:13 PM, Mahesh Nanavalla
Post by Mahesh Nanavalla
Hi all,
Thank you for responding me....
Below is my configure options.......
./configure --enable-orterun-prefix-by-default
--prefix="/home/nmahesh/Workspace/ARM_MPI/openmpi" \
CC=arm-openwrt-linux-muslgnueabi-gcc \
CXX=arm-openwrt-linux-muslgnueabi-g++ \
--host=arm-openwrt-linux-muslgnueabi \
--enable-script-wrapper-compilers
--disable-mpi-fortran \
--enable-shared \
--disable-mmap-shmem \
--disable-posix-shmem \
--disable-sysv-shmem \
--disable-dlopen \
it's configured ,make & make install successfully.....
i compiled helloworld.c programm got executable for arm as
below(by
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
checking the readelf armhelloworld),
/home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
-L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c -o
armhelloworld
Post by Mahesh Nanavalla
a.out armhelloworld helloworld.c openmpi-1.10.3
openmpi-1.10.3.tar.gz
Post by Mahesh Nanavalla
But ,while i run using mpirun on target board as below
------------------------------------------------------------
--------------
Post by Mahesh Nanavalla
It looks like opal_init failed for some reason; your parallel
process is
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
likely to abort. There are many reasons that a parallel process
can
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
fail during opal_init; some of which are due to configuration or
environment problems. This failure appears to be an internal
failure;
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
here's some additional information (which may only be relevant
to an
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
opal_shmem_base_select failed
--> Returned value -1 instead of OPAL_SUCCESS
------------------------------------------------------------
--------------
Post by Mahesh Nanavalla
Kindly help me.......
Thanks and Regards,
Mahesh .N
On Tue, Oct 18, 2016 at 5:09 PM, Kawashima, Takahiro
Post by Kawashima, Takahiro
Hi,
Post by Mahesh Nanavalla
How to cross compile *openmpi *for* arm *on* x86_64 pc.*
*Kindly provide configure options for above...*
You should pass your arm architecture name to the --host option.
Example of my configure options for Open MPI, run on sparc64,
--prefix=...
--host=sparc64-unknown-linux-gnu
--build=x86_64-cross-linux-gnu
--disable-mpi-fortran
CC=your_c_cross_compiler_command
CXX=your_cxx_cross_compiler_command
If you need Fortran support, it's a bit complex. You need to
prepare a special file and pass it to the --with-cross option.
A cross mpicc command is not built automatically with the
options above. There are (at least) three options to compile
your MPI programs.
(A) Manually add -L, -I, and -l options to the cross gcc command
(or another compiler) when you compile a MPI program.
The options you should pass is written in
$installdir/share/openmpi/mpicc-wrapper-data.txt.
In most cases, -I$installdir/include -L$installdir/lib -lmpi
will be sufficient.
(B) Use the --enable-script-wrapper-compilers option on
configure
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Kawashima, Takahiro
time, as you tried. This method may not be maintained well
in the Open MPI team so you may encounter problems.
But you can ask them on this mailing list.
(C) Build Open MPI for x86_64 natively, copy the opal_wrapper
command, and write wrapper-data.txt file.
This is a bit complex task. I'll write the procedure on
GitHub Wiki when I have a time.
_______________________________________________
users mailing list
https://rfd.newmexicoconsortium.org/mailman/listinfo/users
_______________________________________________
users mailing list
https://rfd.newmexicoconsortium.org/mailman/listinfo/users
Gilles Gouaillardet
2016-10-19 11:08:32 UTC
Permalink
You will not be able to generate VT traces, and since you unlikely want to
do that, you will likely be just fine

Cheers,

Gilles

On Wednesday, October 19, 2016, Mahesh Nanavalla <
Post by Mahesh Nanavalla
Hi Gilles,
Thanks for reply,
If i do *--disable-vt *while configuring the openmpi-1.10.3 ,
the size of the installation directory reduced 70MB to 9MB.
will it effect anything........?
On Wed, Oct 19, 2016 at 4:06 PM, Gilles Gouaillardet <
Post by Gilles Gouaillardet
vt is a contrib that produces traces to be used by VaMPIr
IIRC, this has been removed from Open MPI starting v2.0.0
Worst case scenario is it will fail to build, and most likely case is you
do not need it, so you can save some build time with --disable-vet
Cheers,
Gilles
On Wednesday, October 19, 2016, Mahesh Nanavalla <
Post by Mahesh Nanavalla
Hi all,
can any one tell purpose and importance of *--disable-vt*
*Thanks&Regards,*
*Mahesh.N*
On Wed, Oct 19, 2016 at 12:11 PM, Mahesh Nanavalla <
Post by Mahesh Nanavalla
Hi all
it's working.........
I forget to copy all openmpi libs and bin to target board....
Now it's working fine.......
Thank u all.........
Thank u very much for your support....
------------------------------------------------------------
--------------
mpirun has detected an attempt to run as root.
Running at root is *strongly* discouraged as any mistake (e.g., in
defining TMPDIR) or bug can result in catastrophic damage to the OS
file system, leaving your system in an unusable state.
You can override this protection by adding the --allow-run-as-root
option to your cmd line. However, we reiterate our strong advice
against doing so - please do so at your own risk.
------------------------------------------------------------
--------------
Hello world from processor OpenWrt, rank 0 1
Hello world from processor OpenWrt, rank 1 2
Hello world from processor OpenWrt, rank 0 2
Hello world from processor OpenWrt, rank 0 4
Hello world from processor OpenWrt, rank 2 4
Hello world from processor OpenWrt, rank 3 4
Hello world from processor OpenWrt, rank 1 4
On Tue, Oct 18, 2016 at 8:23 PM, Kawashima, Takahiro <
Post by Kawashima, Takahiro
Hi,
You did *not* specify the following options to configure, right?
Specifying all these will cause a problem.
--disable-mmap-shmem
--disable-posix-shmem
--disable-sysv-shmem
Please send the output of the following command.
mpirun --allow-run-as-root -np 1 --mca shmem_base_verbose 100 helloworld
And, give us the config.log file which is output in the
top directory where configure is executed.
Put it on the web or send the compressed (xz or bzip2 is better) file.
Regards,
Takahiro Kawashima
Post by Mahesh Nanavalla
Hi Gilles,
Thank you for reply,
After doing below config options also
./configure --enable-orterun-prefix-by-default
--prefix="/home/nmahesh//home/nmahesh/Workspace/ARM_MPI/armm
pi/openmpi"
Post by Mahesh Nanavalla
CC=arm-openwrt-linux-muslgnueabi-gcc
CXX=arm-openwrt-linux-muslgnueabi-g++
--host=arm-openwrt-linux-muslgnueabi
--enable-script-wrapper-compilers
--disable-mpi-fortran
--enable-shared
--disable-dlopen
it's configured ,make & make install successfully.....
i compiled *helloworld.c *programm got executable for *arm* as
below(by
Post by Mahesh Nanavalla
checking the readelf *armhelloworld*),
/home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
-L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c -o
helloworld*
Post by Mahesh Nanavalla
But ,while i run using mpirun on target board as below
------------------------------------------------------------
--------------
Post by Mahesh Nanavalla
It looks like opal_init failed for some reason; your parallel
process is
Post by Mahesh Nanavalla
likely to abort. There are many reasons that a parallel process can
fail during opal_init; some of which are due to configuration or
environment problems. This failure appears to be an internal
failure;
Post by Mahesh Nanavalla
here's some additional information (which may only be relevant to an
opal_shmem_base_select failed
--> Returned value -1 instead of OPAL_SUCCESS
Kindly help me.........
On Tue, Oct 18, 2016 at 7:31 PM, Mahesh Nanavalla <
Post by Mahesh Nanavalla
Hi Gilles,
Thank you for reply,
After doing below config options also
./configure --enable-orterun-prefix-by-default
--prefix="/home/nmahesh//home/nmahesh/Workspace/ARM_MPI/armm
pi/openmpi"
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
CC=arm-openwrt-linux-muslgnueabi-gcc
CXX=arm-openwrt-linux-muslgnueabi-g++
--host=arm-openwrt-linux-muslgnueabi
--enable-script-wrapper-compilers
--disable-mpi-fortran
--enable-shared
--disable-dlopen
it's configured ,make & make install successfully.....
i compiled *helloworld.c *programm got executable for *arm* as
below(by
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
checking the readelf *armhelloworld*),
/home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
-L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c -o
helloworld*
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
But ,while i run using mpirun on target board as below
------------------------------------------------------------
--------------
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
It looks like opal_init failed for some reason; your parallel
process is
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
likely to abort. There are many reasons that a parallel process
can
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
fail during opal_init; some of which are due to configuration or
environment problems. This failure appears to be an internal
failure;
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
here's some additional information (which may only be relevant to
an
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
opal_shmem_base_select failed
--> Returned value -1 instead of OPAL_SUCCESS
Kindly help me.........
On Tue, Oct 18, 2016 at 5:51 PM, Gilles Gouaillardet <
3 shmem components are available in v1.10, and you explicitly
blacklisted all of them with
--disable-mmap-shmem \
--disable-posix-shmem \
--disable-sysv-shmem
as a consequence, Open MPI will not start.
unless you have a good reason, you should build all of them and
let
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
the runtime decide which is best
Cheers,
Gilles
On Tue, Oct 18, 2016 at 9:13 PM, Mahesh Nanavalla
Post by Mahesh Nanavalla
Hi all,
Thank you for responding me....
Below is my configure options.......
./configure --enable-orterun-prefix-by-default
--prefix="/home/nmahesh/Workspace/ARM_MPI/openmpi" \
CC=arm-openwrt-linux-muslgnueabi-gcc \
CXX=arm-openwrt-linux-muslgnueabi-g++ \
--host=arm-openwrt-linux-muslgnueabi \
--enable-script-wrapper-compilers
--disable-mpi-fortran \
--enable-shared \
--disable-mmap-shmem \
--disable-posix-shmem \
--disable-sysv-shmem \
--disable-dlopen \
it's configured ,make & make install successfully.....
i compiled helloworld.c programm got executable for arm as
below(by
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
checking the readelf armhelloworld),
/home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
-L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c -o
armhelloworld
Post by Mahesh Nanavalla
a.out armhelloworld helloworld.c openmpi-1.10.3
openmpi-1.10.3.tar.gz
Post by Mahesh Nanavalla
But ,while i run using mpirun on target board as below
------------------------------------------------------------
--------------
Post by Mahesh Nanavalla
It looks like opal_init failed for some reason; your parallel
process is
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
likely to abort. There are many reasons that a parallel
process can
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
fail during opal_init; some of which are due to configuration or
environment problems. This failure appears to be an internal
failure;
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
here's some additional information (which may only be relevant
to an
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
opal_shmem_base_select failed
--> Returned value -1 instead of OPAL_SUCCESS
------------------------------------------------------------
--------------
Post by Mahesh Nanavalla
Kindly help me.......
Thanks and Regards,
Mahesh .N
On Tue, Oct 18, 2016 at 5:09 PM, Kawashima, Takahiro
Post by Kawashima, Takahiro
Hi,
Post by Mahesh Nanavalla
How to cross compile *openmpi *for* arm *on* x86_64 pc.*
*Kindly provide configure options for above...*
You should pass your arm architecture name to the --host
option.
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Kawashima, Takahiro
Example of my configure options for Open MPI, run on sparc64,
--prefix=...
--host=sparc64-unknown-linux-gnu
--build=x86_64-cross-linux-gnu
--disable-mpi-fortran
CC=your_c_cross_compiler_command
CXX=your_cxx_cross_compiler_command
If you need Fortran support, it's a bit complex. You need to
prepare a special file and pass it to the --with-cross option.
A cross mpicc command is not built automatically with the
options above. There are (at least) three options to compile
your MPI programs.
(A) Manually add -L, -I, and -l options to the cross gcc
command
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Kawashima, Takahiro
(or another compiler) when you compile a MPI program.
The options you should pass is written in
$installdir/share/openmpi/mpicc-wrapper-data.txt.
In most cases, -I$installdir/include -L$installdir/lib
-lmpi
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Kawashima, Takahiro
will be sufficient.
(B) Use the --enable-script-wrapper-compilers option on
configure
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Kawashima, Takahiro
time, as you tried. This method may not be maintained well
in the Open MPI team so you may encounter problems.
But you can ask them on this mailing list.
(C) Build Open MPI for x86_64 natively, copy the opal_wrapper
command, and write wrapper-data.txt file.
This is a bit complex task. I'll write the procedure on
GitHub Wiki when I have a time.
_______________________________________________
users mailing list
https://rfd.newmexicoconsortium.org/mailman/listinfo/users
_______________________________________________
users mailing list
https://rfd.newmexicoconsortium.org/mailman/listinfo/users
Mahesh Nanavalla
2016-10-19 11:23:09 UTC
Permalink
k...


Thank u very much for your quick reply.....

On Wed, Oct 19, 2016 at 4:38 PM, Gilles Gouaillardet <
Post by Gilles Gouaillardet
You will not be able to generate VT traces, and since you unlikely want to
do that, you will likely be just fine
Cheers,
Gilles
On Wednesday, October 19, 2016, Mahesh Nanavalla <
Post by Mahesh Nanavalla
Hi Gilles,
Thanks for reply,
If i do *--disable-vt *while configuring the openmpi-1.10.3 ,
the size of the installation directory reduced 70MB to 9MB.
will it effect anything........?
On Wed, Oct 19, 2016 at 4:06 PM, Gilles Gouaillardet <
Post by Gilles Gouaillardet
vt is a contrib that produces traces to be used by VaMPIr
IIRC, this has been removed from Open MPI starting v2.0.0
Worst case scenario is it will fail to build, and most likely case is
you do not need it, so you can save some build time with --disable-vet
Cheers,
Gilles
On Wednesday, October 19, 2016, Mahesh Nanavalla <
Post by Mahesh Nanavalla
Hi all,
can any one tell purpose and importance of *--disable-vt*
*Thanks&Regards,*
*Mahesh.N*
On Wed, Oct 19, 2016 at 12:11 PM, Mahesh Nanavalla <
Post by Mahesh Nanavalla
Hi all
it's working.........
I forget to copy all openmpi libs and bin to target board....
Now it's working fine.......
Thank u all.........
Thank u very much for your support....
------------------------------------------------------------
--------------
mpirun has detected an attempt to run as root.
Running at root is *strongly* discouraged as any mistake (e.g., in
defining TMPDIR) or bug can result in catastrophic damage to the OS
file system, leaving your system in an unusable state.
You can override this protection by adding the --allow-run-as-root
option to your cmd line. However, we reiterate our strong advice
against doing so - please do so at your own risk.
------------------------------------------------------------
--------------
Hello world from processor OpenWrt, rank 0 1
Hello world from processor OpenWrt, rank 1 2
Hello world from processor OpenWrt, rank 0 2
Hello world from processor OpenWrt, rank 0 4
Hello world from processor OpenWrt, rank 2 4
Hello world from processor OpenWrt, rank 3 4
Hello world from processor OpenWrt, rank 1 4
On Tue, Oct 18, 2016 at 8:23 PM, Kawashima, Takahiro <
Post by Kawashima, Takahiro
Hi,
You did *not* specify the following options to configure, right?
Specifying all these will cause a problem.
--disable-mmap-shmem
--disable-posix-shmem
--disable-sysv-shmem
Please send the output of the following command.
mpirun --allow-run-as-root -np 1 --mca shmem_base_verbose 100 helloworld
And, give us the config.log file which is output in the
top directory where configure is executed.
Put it on the web or send the compressed (xz or bzip2 is better) file.
Regards,
Takahiro Kawashima
Post by Mahesh Nanavalla
Hi Gilles,
Thank you for reply,
After doing below config options also
./configure --enable-orterun-prefix-by-default
--prefix="/home/nmahesh//home/nmahesh/Workspace/ARM_MPI/armm
pi/openmpi"
Post by Mahesh Nanavalla
CC=arm-openwrt-linux-muslgnueabi-gcc
CXX=arm-openwrt-linux-muslgnueabi-g++
--host=arm-openwrt-linux-muslgnueabi
--enable-script-wrapper-compilers
--disable-mpi-fortran
--enable-shared
--disable-dlopen
it's configured ,make & make install successfully.....
i compiled *helloworld.c *programm got executable for *arm* as
below(by
Post by Mahesh Nanavalla
checking the readelf *armhelloworld*),
/home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
-L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c -o
helloworld*
Post by Mahesh Nanavalla
But ,while i run using mpirun on target board as below
------------------------------------------------------------
--------------
Post by Mahesh Nanavalla
It looks like opal_init failed for some reason; your parallel
process is
Post by Mahesh Nanavalla
likely to abort. There are many reasons that a parallel process can
fail during opal_init; some of which are due to configuration or
environment problems. This failure appears to be an internal
failure;
Post by Mahesh Nanavalla
here's some additional information (which may only be relevant to an
opal_shmem_base_select failed
--> Returned value -1 instead of OPAL_SUCCESS
Kindly help me.........
On Tue, Oct 18, 2016 at 7:31 PM, Mahesh Nanavalla <
Post by Mahesh Nanavalla
Hi Gilles,
Thank you for reply,
After doing below config options also
./configure --enable-orterun-prefix-by-default
--prefix="/home/nmahesh//home/nmahesh/Workspace/ARM_MPI/armm
pi/openmpi"
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
CC=arm-openwrt-linux-muslgnueabi-gcc
CXX=arm-openwrt-linux-muslgnueabi-g++
--host=arm-openwrt-linux-muslgnueabi
--enable-script-wrapper-compilers
--disable-mpi-fortran
--enable-shared
--disable-dlopen
it's configured ,make & make install successfully.....
i compiled *helloworld.c *programm got executable for *arm* as
below(by
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
checking the readelf *armhelloworld*),
/home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
-L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c -o
helloworld*
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
But ,while i run using mpirun on target board as below
------------------------------------------------------------
--------------
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
It looks like opal_init failed for some reason; your parallel
process is
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
likely to abort. There are many reasons that a parallel process
can
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
fail during opal_init; some of which are due to configuration or
environment problems. This failure appears to be an internal
failure;
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
here's some additional information (which may only be relevant to
an
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
opal_shmem_base_select failed
--> Returned value -1 instead of OPAL_SUCCESS
Kindly help me.........
On Tue, Oct 18, 2016 at 5:51 PM, Gilles Gouaillardet <
3 shmem components are available in v1.10, and you explicitly
blacklisted all of them with
--disable-mmap-shmem \
--disable-posix-shmem \
--disable-sysv-shmem
as a consequence, Open MPI will not start.
unless you have a good reason, you should build all of them and
let
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
the runtime decide which is best
Cheers,
Gilles
On Tue, Oct 18, 2016 at 9:13 PM, Mahesh Nanavalla
Post by Mahesh Nanavalla
Hi all,
Thank you for responding me....
Below is my configure options.......
./configure --enable-orterun-prefix-by-default
--prefix="/home/nmahesh/Workspace/ARM_MPI/openmpi" \
CC=arm-openwrt-linux-muslgnueabi-gcc \
CXX=arm-openwrt-linux-muslgnueabi-g++ \
--host=arm-openwrt-linux-muslgnueabi \
--enable-script-wrapper-compilers
--disable-mpi-fortran \
--enable-shared \
--disable-mmap-shmem \
--disable-posix-shmem \
--disable-sysv-shmem \
--disable-dlopen \
it's configured ,make & make install successfully.....
i compiled helloworld.c programm got executable for arm as
below(by
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
checking the readelf armhelloworld),
/home/nmahesh/Workspace/ARM_MPI/openmpi/bin/mpicc
-L/home/nmahesh/Workspace/ARM_MPI/openmpi/lib helloworld.c -o
armhelloworld
Post by Mahesh Nanavalla
a.out armhelloworld helloworld.c openmpi-1.10.3
openmpi-1.10.3.tar.gz
Post by Mahesh Nanavalla
But ,while i run using mpirun on target board as below
------------------------------------------------------------
--------------
Post by Mahesh Nanavalla
It looks like opal_init failed for some reason; your parallel
process is
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
likely to abort. There are many reasons that a parallel
process can
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
fail during opal_init; some of which are due to configuration
or
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
environment problems. This failure appears to be an internal
failure;
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
here's some additional information (which may only be relevant
to an
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
opal_shmem_base_select failed
--> Returned value -1 instead of OPAL_SUCCESS
------------------------------------------------------------
--------------
Post by Mahesh Nanavalla
Kindly help me.......
Thanks and Regards,
Mahesh .N
On Tue, Oct 18, 2016 at 5:09 PM, Kawashima, Takahiro
Post by Kawashima, Takahiro
Hi,
Post by Mahesh Nanavalla
How to cross compile *openmpi *for* arm *on* x86_64 pc.*
*Kindly provide configure options for above...*
You should pass your arm architecture name to the --host
option.
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Kawashima, Takahiro
Example of my configure options for Open MPI, run on sparc64,
--prefix=...
--host=sparc64-unknown-linux-gnu
--build=x86_64-cross-linux-gnu
--disable-mpi-fortran
CC=your_c_cross_compiler_command
CXX=your_cxx_cross_compiler_command
If you need Fortran support, it's a bit complex. You need to
prepare a special file and pass it to the --with-cross option.
A cross mpicc command is not built automatically with the
options above. There are (at least) three options to compile
your MPI programs.
(A) Manually add -L, -I, and -l options to the cross gcc
command
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Kawashima, Takahiro
(or another compiler) when you compile a MPI program.
The options you should pass is written in
$installdir/share/openmpi/mpicc-wrapper-data.txt.
In most cases, -I$installdir/include -L$installdir/lib
-lmpi
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Kawashima, Takahiro
will be sufficient.
(B) Use the --enable-script-wrapper-compilers option on
configure
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Mahesh Nanavalla
Post by Kawashima, Takahiro
time, as you tried. This method may not be maintained well
in the Open MPI team so you may encounter problems.
But you can ask them on this mailing list.
(C) Build Open MPI for x86_64 natively, copy the opal_wrapper
command, and write wrapper-data.txt file.
This is a bit complex task. I'll write the procedure on
GitHub Wiki when I have a time.
_______________________________________________
users mailing list
https://rfd.newmexicoconsortium.org/mailman/listinfo/users
_______________________________________________
users mailing list
https://rfd.newmexicoconsortium.org/mailman/listinfo/users
_______________________________________________
users mailing list
https://rfd.newmexicoconsortium.org/mailman/listinfo/users
Loading...