Re: [OMPI users] starting open-mpi
Hi. I've installed Visual Studio 2008 on my machine. But i have still the same problem. How can i solve it? thx On Fri, May 11, 2012 at 10:50 PM, Ghobad Zarrinchian wrote: > Thanks Dmitry for your reply. :) > > > On Fri, May 11, 2012 at 4:47 PM, Dmitry N. Mikushin > wrote: > >> Hi Ghobad, >> >> The error message means the OpenMPI wants to use cl.exe - the compiler >> from Microsoft Visual Studio. >> >> Here http://www.open-mpi.org/software/ompi/v1.5/ms-windows.php is it >> stated: >> >> This is the first binary release for Windows, with basic MPI libraries >> and executables. The supported platforms are Windows XP, Windows >> Vista, Windows Server 2003/2008, and Windows 7 (including both 32 and >> 64 bit versions). The installers were configured with CMake 2.8.1 and >> compiled under Visual Studio 2010, and they support for C/C++ >> compilers of Visual Studio 2005, 2008 and 2010. >> >> So, to compile MPI programs you probably need one of this compilers to >> be installed. >> >> Best regards. >> - Dima. >> >> 2012/5/10 Ghobad Zarrinchian : >> > Hi all. I'm a new open-mpi user. I've downloaded the >> > OpenMPI_v1.5.5-1_win32.exe file to install open-mpi on my dual-core >> windows >> > 7 machine. I installed the file but now i can't compile my mpi >> programs. I >> > use command below (in command prompt window) to compile my 'test.cpp' >> > program: >> > >> >>> mpic++ -o test test.cpp >> > >> > but i get error as follows: >> > >> >>> The open mpi wrapper compiler was unable to find the specified >> compiler >> >>> cl.exe in your path. >> > Note that this compiler was either specified at configure time or >> in >> > one several possible environment variables. >> > >> > What is the problem? Is my compilation command right? Is there any >> remained >> > necessary steps to complete my open-mpi installation? >> > Is it necessary to specify some environment variables? >> > >> > Thanks in advanced. >> > >> > ___ >> > users mailing list >> > us...@open-mpi.org >> > http://www.open-mpi.org/mailman/listinfo.cgi/users >> >> ___ >> users mailing list >> us...@open-mpi.org >> http://www.open-mpi.org/mailman/listinfo.cgi/users >> > >
Re: [OMPI users] starting open-mpi
Hi, You need to use the command prompt provided by Visual Studio and it will work. Matthieu 2012/5/18 Ghobad Zarrinchian > Hi. I've installed Visual Studio 2008 on my machine. But i have still the > same problem. How can i solve it? thx > > > On Fri, May 11, 2012 at 10:50 PM, Ghobad Zarrinchian < > gzarrin@gmail.com> wrote: > >> Thanks Dmitry for your reply. :) >> >> >> On Fri, May 11, 2012 at 4:47 PM, Dmitry N. Mikushin >> wrote: >> >>> Hi Ghobad, >>> >>> The error message means the OpenMPI wants to use cl.exe - the compiler >>> from Microsoft Visual Studio. >>> >>> Here http://www.open-mpi.org/software/ompi/v1.5/ms-windows.php is it >>> stated: >>> >>> This is the first binary release for Windows, with basic MPI libraries >>> and executables. The supported platforms are Windows XP, Windows >>> Vista, Windows Server 2003/2008, and Windows 7 (including both 32 and >>> 64 bit versions). The installers were configured with CMake 2.8.1 and >>> compiled under Visual Studio 2010, and they support for C/C++ >>> compilers of Visual Studio 2005, 2008 and 2010. >>> >>> So, to compile MPI programs you probably need one of this compilers to >>> be installed. >>> >>> Best regards. >>> - Dima. >>> >>> 2012/5/10 Ghobad Zarrinchian : >>> > Hi all. I'm a new open-mpi user. I've downloaded the >>> > OpenMPI_v1.5.5-1_win32.exe file to install open-mpi on my dual-core >>> windows >>> > 7 machine. I installed the file but now i can't compile my mpi >>> programs. I >>> > use command below (in command prompt window) to compile my 'test.cpp' >>> > program: >>> > >>> >>> mpic++ -o test test.cpp >>> > >>> > but i get error as follows: >>> > >>> >>> The open mpi wrapper compiler was unable to find the specified >>> compiler >>> >>> cl.exe in your path. >>> > Note that this compiler was either specified at configure time or >>> in >>> > one several possible environment variables. >>> > >>> > What is the problem? Is my compilation command right? Is there any >>> remained >>> > necessary steps to complete my open-mpi installation? >>> > Is it necessary to specify some environment variables? >>> > >>> > Thanks in advanced. >>> > >>> > ___ >>> > users mailing list >>> > us...@open-mpi.org >>> > http://www.open-mpi.org/mailman/listinfo.cgi/users >>> >>> ___ >>> users mailing list >>> us...@open-mpi.org >>> http://www.open-mpi.org/mailman/listinfo.cgi/users >>> >> >> > > ___ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users > -- Information System Engineer, Ph.D. Blog: http://matt.eifelle.com LinkedIn: http://www.linkedin.com/in/matthieubrucher
Re: [OMPI users] Returned "Unreachable" (-12) instead of "Success" (0)
Hello Community/Ralph I was told by the sysadmin that the firewall does not prevent communication between two machines (tik33x, tik34x) for instance. However, it will only block if OpenMPI is trying to open TCP/UDP ports lower than 1024, which require privileges. Is it possible to know which port numbers does OpenMPI use? Specifically, is it possible to specify port numbers that OpenMPI must not use (OpenMPI-1.4.x)? Here is the reply I got from my sysadmin: "There is a firewall, but it does not block internal traffic within the whole TIK network (I verified it for myself). Thus, the connection problem must be somewhere else (a service not running or binding to the wrong interface for instance). Maybe the service wants to bind to a tcp or udp port lower than 1024, which can only be allocated by the system's superuser. First, check on which ports and on which network card interfaces the software listens and if it is configured correctly so that it will listen at all." Is there a way out? Thanks a lot Devendra From: Ralph Castain To: devendra rai ; Open MPI Users Sent: Wednesday, 16 May 2012, 15:09 Subject: Re: [OMPI users] Returned "Unreachable" (-12) instead of "Success" (0) Looks like you have a firewall between hosts tik34x and tik33x - you might check to ensure all firewalls are disabled. The error is saying it can't open a TCP socket between the two nodes, so there is no communication path between those two processes. On May 16, 2012, at 4:22 AM, devendra rai wrote: Hello All, > > >I am trying to run an OpenMPI application across two physical machines. > >I get an error "Returned "Unreachable" (-12) instead of "Success" (0)", and >looking through the logs (attached), I cannot seem to find out the cause, and >how to fix it. > >I see lot of (communication) components being loaded and then unloaded, and I >do not see which nodes pick up what kind of comm-interface. > >-- >At least one pair of MPI processes are unable to reach each other for >MPI communications. This means that no Open MPI device has indicated >that it can be used to communicate between these processes. This is >an error; Open MPI requires that all MPI processes be able to reach >each other. This error can sometimes be the result of forgetting to >specify the "self" BTL. > > Process 1 ([[10782,1],6]) is on host: tik34x > Process 2 ([[10782,1],0]) is on host: tik33x > BTLs attempted: self sm tcp > >Your MPI job is now going to abort; sorry. > >The "mpirun" line is: > >mpirun --mca btl self,sm,tcp --mca btl_base_verbose 30 -report-pid >-display-map -report-bindings -hostfile hostfile -np 7 -v --rankfile >rankfile.txt -v --timestamp-output --tag-output ./xstartwrapper.sh >./run_gdb.sh > >where the .sh files are fixes for forwarding X-windows from multiple machines >to the machines where I am logged in. > >Can anyone help? > >Thanks a lot. > >Best, > >Devendra > > > > >From: devendra rai > >Subject: Returned "Unreachable" (-12) instead of "Success" (0) > >List-Post: users@lists.open-mpi.org Date: May 16, 2012 4:18:28 AM MDT > >To: Open MPI Users > >Reply-To: devendra rai > > > > >Hello All, > >I am trying to run an OpenMPI application across two physical machines. > >I get an error "Returned "Unreachable" (-12) instead of "Success" (0)", and >looking through the logs (attached), I cannot seem to find out the cause, and >how to fix it. > >I see lot of (communication) components being loaded and then unloaded, and I >do not see which nodes pick up what kind of comm-interface. > >-- >At least one pair of MPI processes are unable to reach each other for >MPI communications. This means that no Open MPI device has indicated >that it can be used to communicate between these processes. This is >an error; Open MPI requires that all MPI processes be able to reach >each other. This error can sometimes be the result of forgetting to >specify the "self" BTL. > > Process 1 ([[10782,1],6]) is on host: tik34x > Process 2 ([[10782,1],0]) is on host: tik33x > BTLs attempted: self sm tcp > >Your MPI job is now going to abort; sorry. > >The "mpirun" line is: > >mpirun --mca btl self,sm,tcp --mca btl_base_verbose 30 -report-pid >-display-map -report-bindings -hostfile hostfile -np 7 -v --rankfile >rankfile.txt -v --timestamp-output --tag-output ./xstartwrapper.sh >./run_gdb.sh > >where the .sh files are fixes for forwarding X-windows from multiple machines >to the machines where I am logged in. > >Can anyone help? > >Thanks a lot. > >Best, > >Devendra > > >___ >users mailing list >us...@open-mpi.org >http://www.open-mpi.org/mailman/listinfo.cgi/users
Re: [OMPI users] Returned "Unreachable" (-12) instead of "Success" (0)
On May 18, 2012, at 4:02 AM, devendra rai wrote: > Hello Community/Ralph=0A=0AI was told by the sysadmin that the firewall doe= > s not prevent communication between two machines (tik33x, tik34x) for insta= > nce. However, it will only block if OpenMPI is trying to open TCP/UDP ports= > lower than 1024, which require privileges.=0A=0AIs it possible to know whi= > ch port numbers does OpenMPI use? Open MPI uses random TCP ports above 1024 (i.e., we let the system assign which port numbers we use). > Specifically, is it possible to specify p= > ort numbers that OpenMPI must not use (OpenMPI-1.4.x)?=0A=0AHere is the rep= > ly I got from my sysadmin:=0A=0A"There is a firewall, but it does not block= > internal=0Atraffic within the whole TIK network (I verified it for myself)= > .=0AThus, the connection problem must be somewhere else=0A(a service not ru= > nning or binding to the wrong interface=0Afor instance). Maybe the service = > wants to bind to a=0Atcp or udp port lower than 1024, which can only be=0Aa= > llocated by the system's superuser. First, check on=0Awhich ports and on wh= > ich network card interfaces=0Athe software listens and if it is configured = > correctly=0Aso that it will listen at all."=0A=0A=0AIs there a way out?=0A= You might try specifying exactly which interfaces Open MPI should use. For example: mpirun --mca btl_tcp_if_include eth0 --mca oob_tcp_if_include eth0 ... This would restrict Open MPI to only using the "eth0" interface (obviously, you should substitute in whatever is the relevant interface name for your machines -- hopefully, it's the same interface name across all of them). Also, we just released Open MPI 1.6. You might want to upgrade when you can; the 1.6 series replaces the 1.4 series. -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
Re: [OMPI users] Returned "Unreachable" (-12) instead of "Success" (0)
Not sure what the solution is, but ompi does not bind to privilege ports. In fact , ompi_info --param btl tcp | grep port_min should show that the minimum port where TCP BTL will try to bind (by default ) is 1024. -- Sent from my iPhone On May 18, 2012, at 1:02 AM, devendra rai wrote: > Hello Community/Ralph > > I was told by the sysadmin that the firewall does not prevent communication > between two machines (tik33x, tik34x) for instance. However, it will only > block if OpenMPI is trying to open TCP/UDP ports lower than 1024, which > require privileges. > > Is it possible to know which port numbers does OpenMPI use? Specifically, is > it possible to specify port numbers that OpenMPI must not use (OpenMPI-1.4.x)? > > Here is the reply I got from my sysadmin: > > "There is a firewall, but it does not block internal > traffic within the whole TIK network (I verified it for myself). > Thus, the connection problem must be somewhere else > (a service not running or binding to the wrong interface > for instance). Maybe the service wants to bind to a > tcp or udp port lower than 1024, which can only be > allocated by the system's superuser. First, check on > which ports and on which network card interfaces > the software listens and if it is configured correctly > so that it will listen at all." > > > Is there a way out? > > Thanks a lot > > Devendra > > From: Ralph Castain > To: devendra rai ; Open MPI Users > > Sent: Wednesday, 16 May 2012, 15:09 > Subject: Re: [OMPI users] Returned "Unreachable" (-12) instead of "Success" > (0) > > Looks like you have a firewall between hosts tik34x and tik33x - you might > check to ensure all firewalls are disabled. The error is saying it can't open > a TCP socket between the two nodes, so there is no communication path between > those two processes. > > > On May 16, 2012, at 4:22 AM, devendra rai wrote: > >> Hello All, >> >> I am trying to run an OpenMPI application across two physical machines. >> >> I get an error "Returned "Unreachable" (-12) instead of "Success" (0)", and >> looking through the logs (attached), I cannot seem to find out the cause, >> and how to fix it. >> >> I see lot of (communication) components being loaded and then unloaded, and >> I do not see which nodes pick up what kind of comm-interface. >> >> -- >> At least one pair of MPI processes are unable to reach each other for >> MPI communications. This means that no Open MPI device has indicated >> that it can be used to communicate between these processes. This is >> an error; Open MPI requires that all MPI processes be able to reach >> each other. This error can sometimes be the result of forgetting to >> specify the "self" BTL. >> >> Process 1 ([[10782,1],6]) is on host: tik34x >> Process 2 ([[10782,1],0]) is on host: tik33x >> BTLs attempted: self sm tcp >> >> Your MPI job is now going to abort; sorry. >> >> The "mpirun" line is: >> >> mpirun --mca btl self,sm,tcp --mca btl_base_verbose 30 -report-pid >> -display-map -report-bindings -hostfile hostfile -np 7 -v --rankfile >> rankfile.txt -v --timestamp-output --tag-output ./xstartwrapper.sh >> ./run_gdb.sh >> >> where the .sh files are fixes for forwarding X-windows from multiple >> machines to the machines where I am logged in. >> >> Can anyone help? >> >> Thanks a lot. >> >> Best, >> >> Devendra >> >> >> >> From: devendra rai >> Subject: Returned "Unreachable" (-12) instead of "Success" (0) >> Date: May 16, 2012 4:18:28 AM MDT >> To: Open MPI Users >> Reply-To: devendra rai >> >> >> >> Hello All, >> >> I am trying to run an OpenMPI application across two physical machines. >> >> I get an error "Returned "Unreachable" (-12) instead of "Success" (0)", and >> looking through the logs (attached), I cannot seem to find out the cause, >> and how to fix it. >> >> I see lot of (communication) components being loaded and then unloaded, and >> I do not see which nodes pick up what kind of comm-interface. >> >> -- >> At least one pair of MPI processes are unable to reach each other for >> MPI communications. This means that no Open MPI device has indicated >> that it can be used to communicate between these processes. This is >> an error; Open MPI requires that all MPI processes be able to reach >> each other. This error can sometimes be the result of forgetting to >> specify the "self" BTL. >> >> Process 1 ([[10782,1],6]) is on host: tik34x >> Process 2 ([[10782,1],0]) is on host: tik33x >> BTLs attempted: self sm tcp >> >> Your MPI job is now going to abort; sorry. >> >> The "mpirun" line is: >> >> mpirun --mca btl self,sm,tcp --mca btl_base_verbose 30 -report-pid >> -display-map -report-bindings -hostfile hostfile -np 7 -v --rankfile >> rankfile.txt -v --timestamp-output --tag-output ./xstartwrapper.sh >> ./run_g
Re: [OMPI users] Problem-Bug with MPI_Intercomm_create()
I'm afraid there's on news so far. :-\ On May 14, 2012, at 4:21 PM, Aurélien Esnard wrote: > > Hi, > > No news, good news... ? > > Aurélien Esnard :-) > > On 11/04/2011 01:17 PM, Jeff Squyres wrote: >> After some discussion on the devel list, I opened >> https://svn.open-mpi.org/trac/ompi/ticket/2904 to track the issue. >> >> >> On Oct 25, 2011, at 12:08 PM, Ralph Castain wrote: >> >>> FWIW: I have tracked this problem down. The fix is a little more >>> complicated then I'd like, so I'm going to have to ping some other folks to >>> ensure we concur on the approach before doing something. >>> >>> On Oct 25, 2011, at 8:20 AM, Ralph Castain wrote: >>> I still see it failing the test George provided on the trunk. I'm unaware of anyone looking further into it, though, as the prior discussion seemed to just end. On Oct 25, 2011, at 7:01 AM, orel wrote: > Dears, > > I try from several days to use advanced MPI2 features in the following > scenario : > > 1) a master code A (of size NPA) spawns (MPI_Comm_spawn()) two slave > codes B (of size NPB) and C (of size NPC), providing intercomms A-B and > A-C ; > 2) i create intracomm AB and AC by merging intercomms ; > 3) then i create intercomm AB-C by calling MPI_Intercomm_create() by > using AC as bridge... > > MPI_Comm intercommABC; A: MPI_Intercomm_create(intracommAB, 0, > intracommAC, NPA, TAG,&intercommABC); > B: MPI_Intercomm_create(intracommAB, 0, MPI_COMM_NULL, > 0,TAG,&intercommABC); > C: MPI_Intercomm_create(intracommC, 0, intracommAC, 0, TAG,&intercommABC); > >In these calls, A0 and C0 play the role of local leader for AB and C > respectively. >C0 and A0 play the roles of remote leader in bridge intracomm AC. > > 3) MPI_Barrier(intercommABC); > 4) i merge intercomm AB-C into intracomm ABC$ > 5) MPI_Barrier(intracommABC); > > My BUG: These calls success, but when i try to use intracommABC for a > collective communication like MPI_Barrier(), > i got the following error : > > *** An error occurred in MPI_Barrier > *** on communicator > *** MPI_ERR_INTERN: internal error > *** MPI_ERRORS_ARE_FATAL: your MPI job will now abort > > > I try with OpenMPI trunk, 1.5.3, 1.5.4 and Mpich2-1.4.1p1 > > My code works perfectly if intracomm A, B and C are obtained by > MPI_Comm_split() instead of MPI_Comm_spawn() > > > I found same problem in a previous thread of the OMPI Users mailing list : > > => http://www.open-mpi.org/community/lists/users/2011/06/16711.php > > Is that bug/problem is currently under investigation ? :-) > > i can give detailed code, but the one provided by George Bosilca in this > previous thread provides same error... > > Thank you to help me... > > -- > Aurélien Esnard > University Bordeaux 1 / LaBRI / INRIA (France) > ___ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users >>> >>> ___ >>> users mailing list >>> us...@open-mpi.org >>> http://www.open-mpi.org/mailman/listinfo.cgi/users >> > -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
Re: [OMPI users] Make OpenMPI-1.6 fails: Missing files?
Hello All, Nevermind, after a couple of fresh install attempts, I got the build to work. Seems like building on the cluster machines may fail, but I am not sure why. Best, Devendra Rai From: devendra rai To: Open Users Sent: Friday, 18 May 2012, 12:59 Subject: Make OpenMPI-1.6 fails: Missing files? Hello All, I am trying to build OpenMPI-1.6. The ./config part went fine, however the make fails telling me that some file is missing from orte/ folder. Something like this: orte/mca/iof/Makefile.am:41: `orte/mca/iof/base/Makefile.am' included from here orte/mca/notifier/Makefile.am:32: WANT_INSTALL_HEADERS does not appear in AM_CONDITIONAL orte/mca/odls/Makefile.am:32: WANT_INSTALL_HEADERS does not appear in AM_CONDITIONAL orte/mca/odls/base/Makefile.am:25: ORTE_DISABLE_FULL_SUPPORT does not appear in AM_CONDITIONAL orte/mca/odls/Makefile.am:39: `orte/mca/odls/base/Makefile.am' included from here orte/mca/oob/Makefile.am:31: WANT_INSTALL_HEADERS does not appear in AM_CONDITIONAL orte/mca/oob/base/Makefile.am:25: ORTE_DISABLE_FULL_SUPPORT does not appear in AM_CONDITIONAL orte/mca/oob/Makefile.am:38: `orte/mca/oob/base/Makefile.am' included from here orte/mca/plm/Makefile.am:32: WANT_INSTALL_HEADERS does not appear in AM_CONDITIONAL orte/mca/plm/base/Makefile.am:28: ORTE_DISABLE_FULL_SUPPORT does not appear in AM_CONDITIONAL orte/mca/plm/Makefile.am:39: `orte/mca/plm/base/Makefile.am' included from here orte/mca/ras/Makefile.am:32: WANT_INSTALL_HEADERS does not appear in AM_CONDITIONAL orte/mca/ras/base/Makefile.am:27: ORTE_DISABLE_FULL_SUPPORT does not appear in AM_CONDITIONAL orte/mca/ras/Makefile.am:39: `orte/mca/ras/base/Makefile.am' included from here orte/mca/rmaps/Makefile.am:31: WANT_INSTALL_HEADERS does not appear in AM_CONDITIONAL orte/mca/rmaps/base/Makefile.am:26: ORTE_DISABLE_FULL_SUPPORT does not appear in AM_CONDITIONAL orte/mca/rmaps/Makefile.am:38: `orte/mca/rmaps/base/Makefile.am' included from here orte/mca/rmcast/Makefile.am:34: WANT_INSTALL_HEADERS does not appear in AM_CONDITIONAL orte/mca/rmcast/base/Makefile.am:19: ORTE_DISABLE_FULL_SUPPORT does not appear in AM_CONDITIONAL orte/mca/rmcast/Makefile.am:41: `orte/mca/rmcast/base/Makefile.am' included from here orte/mca/rml/Makefile.am:33: WANT_INSTALL_HEADERS does not appear in AM_CONDITIONAL orte/mca/rml/base/Makefile.am:26: ORTE_DISABLE_FULL_SUPPORT does not appear in AM_CONDITIONAL orte/mca/rml/Makefile.am:40: `orte/mca/rml/base/Makefile.am' included from here orte/mca/routed/Makefile.am:25: WANT_INSTALL_HEADERS does not appear in AM_CONDITIONAL orte/mca/routed/base/Makefile.am:17: ORTE_DISABLE_FULL_SUPPORT does not appear in AM_CONDITIONAL orte/mca/routed/Makefile.am:32: `orte/mca/routed/base/Makefile.am' included from here orte/mca/snapc/Makefile.am:44: WANT_INSTALL_HEADERS does not appear in AM_CONDITIONAL orte/mca/snapc/base/Makefile.am:25: ORTE_DISABLE_FULL_SUPPORT does not appear in AM_CONDITIONAL orte/mca/snapc/Makefile.am:51: `orte/mca/snapc/base/Makefile.am' included from here make: *** [Makefile.in] Error 1 My build steps are: #!/bin/bash #setup paths PATH=/home/raid/private/Customizations_NODELETE/gcc-4.6/bin:$PATH export LD_LIBRARY_PATH=/home/raid/private/Customizations_NODELETE/gcc-4.6/lib mkdir ../ompi-output ./configure CC=/home/raid/private/Customizations_NODELETE/gcc-4.6/bin/gcc CXX=/home/raid/private/Customizations_NODELETE/gcc-4.6/bin/g++ -prefix=/home/raid/private/Customizations_NODELETE/OpenMPI-1.6 --enable-mem-profile --enable-mem-debug --enable-heterogeneous --enable-ipv6 --enable-mpirun-prefix-by-default --enable-multicast --enable-mpi-interface-warning --enable-mpi-cxx --enable-mpi-cxx-seek --enable-cxx-exceptions --enable-smp-locks --enable-opal-multi-threads --enable-mpi-thread-multiple --enable-debug --enable-trace --enable-memchecker --with-sge --with-valgrind=/usr --with-threads=posix --disable-mpi-f77 --disable-mpi-f90 |& tee ../ompi-output/configure.out cp config.log opal/include/opal_config.h ../ompi-output make all |& tee ../ompi-output/make.out make install |& tee ../ompi-output/make-install.out I am running without privileges on the server, and I am trying to use a custom version of gcc (4.6). All logs are attached. I had a similar looking strange problem before, and that was somehow a bug in the package that I downloaded from http://www.open-mpi.org. Can someone provide a clue? Thanks a lot best, Devendra
Re: [OMPI users] Make OpenMPI-1.6 fails: Missing files?
I've seen this happen when you build on a networked filesystem and the time is not well synced between the machine that you're building on and the network filesystem server. Open MPI's build system relies on precise timestamps and make dependency rules; they can go completely awry if the timestamps are off. On May 18, 2012, at 1:48 PM, devendra rai wrote: > > Hello All, > > Nevermind, after a couple of fresh install attempts, I got the build to work. > > Seems like building on the cluster machines may fail, but I am not sure why. > > Best, > > Devendra Rai > From: devendra rai > To: Open Users > Sent: Friday, 18 May 2012, 12:59 > Subject: Make OpenMPI-1.6 fails: Missing files? > > Hello All, > > I am trying to build OpenMPI-1.6. The ./config part went fine, however the > make fails telling me that some file is missing from orte/ folder. Something > like this: > > orte/mca/iof/Makefile.am:41: `orte/mca/iof/base/Makefile.am' included from > here > orte/mca/notifier/Makefile.am:32: WANT_INSTALL_HEADERS does not appear in > AM_CONDITIONAL > orte/mca/odls/Makefile.am:32: WANT_INSTALL_HEADERS does not appear in > AM_CONDITIONAL > orte/mca/odls/base/Makefile.am:25: ORTE_DISABLE_FULL_SUPPORT does not appear > in AM_CONDITIONAL > orte/mca/odls/Makefile.am:39: `orte/mca/odls/base/Makefile.am' included > from here > orte/mca/oob/Makefile.am:31: WANT_INSTALL_HEADERS does not appear in > AM_CONDITIONAL > orte/mca/oob/base/Makefile.am:25: ORTE_DISABLE_FULL_SUPPORT does not appear > in AM_CONDITIONAL > orte/mca/oob/Makefile.am:38: `orte/mca/oob/base/Makefile.am' included from > here > orte/mca/plm/Makefile.am:32: WANT_INSTALL_HEADERS does not appear in > AM_CONDITIONAL > orte/mca/plm/base/Makefile.am:28: ORTE_DISABLE_FULL_SUPPORT does not appear > in AM_CONDITIONAL > orte/mca/plm/Makefile.am:39: `orte/mca/plm/base/Makefile.am' included from > here > orte/mca/ras/Makefile.am:32: WANT_INSTALL_HEADERS does not appear in > AM_CONDITIONAL > orte/mca/ras/base/Makefile.am:27: ORTE_DISABLE_FULL_SUPPORT does not appear > in AM_CONDITIONAL > orte/mca/ras/Makefile.am:39: `orte/mca/ras/base/Makefile.am' included from > here > orte/mca/rmaps/Makefile.am:31: WANT_INSTALL_HEADERS does not appear in > AM_CONDITIONAL > orte/mca/rmaps/base/Makefile.am:26: ORTE_DISABLE_FULL_SUPPORT does not appear > in AM_CONDITIONAL > orte/mca/rmaps/Makefile.am:38: `orte/mca/rmaps/base/Makefile.am' included > from here > orte/mca/rmcast/Makefile.am:34: WANT_INSTALL_HEADERS does not appear in > AM_CONDITIONAL > orte/mca/rmcast/base/Makefile.am:19: ORTE_DISABLE_FULL_SUPPORT does not > appear in AM_CONDITIONAL > orte/mca/rmcast/Makefile.am:41: `orte/mca/rmcast/base/Makefile.am' included > from here > orte/mca/rml/Makefile.am:33: WANT_INSTALL_HEADERS does not appear in > AM_CONDITIONAL > orte/mca/rml/base/Makefile.am:26: ORTE_DISABLE_FULL_SUPPORT does not appear > in AM_CONDITIONAL > orte/mca/rml/Makefile.am:40: `orte/mca/rml/base/Makefile.am' included from > here > orte/mca/routed/Makefile.am:25: WANT_INSTALL_HEADERS does not appear in > AM_CONDITIONAL > orte/mca/routed/base/Makefile.am:17: ORTE_DISABLE_FULL_SUPPORT does not > appear in AM_CONDITIONAL > orte/mca/routed/Makefile.am:32: `orte/mca/routed/base/Makefile.am' included > from here > orte/mca/snapc/Makefile.am:44: WANT_INSTALL_HEADERS does not appear in > AM_CONDITIONAL > orte/mca/snapc/base/Makefile.am:25: ORTE_DISABLE_FULL_SUPPORT does not appear > in AM_CONDITIONAL > orte/mca/snapc/Makefile.am:51: `orte/mca/snapc/base/Makefile.am' included > from here > make: *** [Makefile.in] Error 1 > > > > > My build steps are: > > #!/bin/bash > > #setup paths > PATH=/home/raid/private/Customizations_NODELETE/gcc-4.6/bin:$PATH > export LD_LIBRARY_PATH=/home/raid/private/Customizations_NODELETE/gcc-4.6/lib > > > mkdir ../ompi-output > ./configure CC=/home/raid/private/Customizations_NODELETE/gcc-4.6/bin/gcc > CXX=/home/raid/private/Customizations_NODELETE/gcc-4.6/bin/g++ > -prefix=/home/raid/private/Customizations_NODELETE/OpenMPI-1.6 > --enable-mem-profile --enable-mem-debug --enable-heterogeneous --enable-ipv6 > --enable-mpirun-prefix-by-default --enable-multicast > --enable-mpi-interface-warning --enable-mpi-cxx --enable-mpi-cxx-seek > --enable-cxx-exceptions --enable-smp-locks --enable-opal-multi-threads > --enable-mpi-thread-multiple --enable-debug --enable-trace > --enable-memchecker --with-sge --with-valgrind=/usr --with-threads=posix > --disable-mpi-f77 --disable-mpi-f90 |& tee ../ompi-output/configure.out > > cp config.log opal/include/opal_config.h ../ompi-output > > make all |& tee ../ompi-output/make.out > > make install |& tee ../ompi-output/make-install.out > > I am running without privileges on the server, and I am trying to use a > custom version of gcc (4.6). > > > All logs are attached. I had a similar looking strange problem before, and > that was somehow a bug in the package that I downloaded from
