k...
Thank u very much for your quick reply..... On Wed, Oct 19, 2016 at 4:38 PM, Gilles Gouaillardet < gilles.gouaillar...@gmail.com> wrote: > 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 < > mahesh.nanavalla...@gmail.com> wrote: > >> 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 < >> gilles.gouaillar...@gmail.com> wrote: >> >>> 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 < >>> mahesh.nanavalla...@gmail.com> wrote: >>> >>>> 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 < >>>> mahesh.nanavalla...@gmail.com> wrote: >>>> >>>>> 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.... >>>>> >>>>> root@OpenWrt:/# cp /openmpi/lib/libopen-rte.so.12 /usr/lib/ >>>>> root@OpenWrt:/# cp /openmpi/lib/libopen-pal.so.13 /usr/lib/ >>>>> root@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. >>>>> ------------------------------------------------------------ >>>>> -------------- >>>>> root@OpenWrt:/# /openmpi/bin/mpirun --allow-run-as-root -np 1 >>>>> helloworld >>>>> Hello world from processor OpenWrt, rank 0 1 >>>>> root@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 >>>>> root@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 < >>>>> t-kawash...@jp.fujitsu.com> wrote: >>>>> >>>>>> 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 >>>>>> >>>>>> > 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" >>>>>> > 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@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 >>>>>> > >>>>>> > root@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 < >>>>>> > mahesh.nanavalla...@gmail.com> wrote: >>>>>> > >>>>>> > > 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" >>>>>> > > 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@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 >>>>>> > > >>>>>> > > root@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 5:51 PM, Gilles Gouaillardet < >>>>>> > > gilles.gouaillar...@gmail.com> wrote: >>>>>> > > >>>>>> > >> 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 >>>>>> > >> <mahesh.nanavalla...@gmail.com> wrote: >>>>>> > >> > 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@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@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 >>>>>> > >> > >>>>>> > >> > root@OpenWrt:/# mpirun --allow-run-as-root -np 1 armhelloworld >>>>>> > >> > >>>>>> > >> > ------------------------------------------------------------ >>>>>> > >> -------------- >>>>>> > >> > 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 >>>>>> > >> > ------------------------------------------------------------ >>>>>> > >> -------------- >>>>>> > >> > root@OpenWrt:/# >>>>>> > >> > >>>>>> > >> > Kindly help me....... >>>>>> > >> > >>>>>> > >> > Thanks and Regards, >>>>>> > >> > Mahesh .N >>>>>> > >> > >>>>>> > >> > >>>>>> > >> > On Tue, Oct 18, 2016 at 5:09 PM, Kawashima, Takahiro >>>>>> > >> > <t-kawash...@jp.fujitsu.com> wrote: >>>>>> > >> >> >>>>>> > >> >> Hi, >>>>>> > >> >> >>>>>> > >> >> > 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. >>>>>> _______________________________________________ >>>>>> users mailing list >>>>>> users@lists.open-mpi.org >>>>>> https://rfd.newmexicoconsortium.org/mailman/listinfo/users >>>>>> >>>>> >>>>> >>>> >>> _______________________________________________ >>> users mailing list >>> users@lists.open-mpi.org >>> https://rfd.newmexicoconsortium.org/mailman/listinfo/users >>> >> >> > _______________________________________________ > users mailing list > users@lists.open-mpi.org > https://rfd.newmexicoconsortium.org/mailman/listinfo/users >
_______________________________________________ users mailing list users@lists.open-mpi.org https://rfd.newmexicoconsortium.org/mailman/listinfo/users
