[OMPI users] Windows: msv*.dll files presence in Release build
Greetings! On doing Release build for Visual Studio 2008 I am observing following debug files along with other files ... libmpi*d.dll* libmpi_cxx*d.dll* libmpi_f77*d.dll* etc... *msvcm90.dll* * msvcp90.dll* * msvcr90.dll* In this regard I have following two questions... 1) For Release build using VS2008, why it generates *msv*.dll* files? 2) For Release build using VS2008, why it generates **d.dll* files (i.e. debug libraries)? In both of the above cases, How can we stop generating these files? Please clarify. Thank you. -Hiral
Re: [OMPI users] FW: Issue with mpicc --showme in windows
Hi Amarnath, Probably http://www.open-mpi.org/community/lists/users/2011/05/16524.php thread may help. Thank you. -Hiral
[OMPI users] mpi.h:: OMPI_HAVE_FORTRAN_LOGICAL / INTEGER / REAL are set to 0 (zero)
Greetings once again !!! Environment: OS: Windows 7 64-bit Compilers: ifort and cl.exe (both 64-bit) CMAKE: version-2.8.4 OpenMPI: version 1.5.3 As described in the README.WINDOWS.txt, when performing 'First approach:" I am observing following... 1) via cmake-gui.exe clicked 'Configure' and it shown all config options in pink color see output of this step in attached cmake_gui_output1.txt 2) then I enabled OMPI_WANT_F77_BINDING and OMPI_WANT_F90_BINDING to true and then clicked 'Configure'. see output of this step in attached cmake_gui_output2.txt As you can observe in cmake_gui_output2.txt file, it succeeded on all Fortran data types (except INTEGER*16 and REAL*2). Now what I am observing is that eventho' fortran compiler supports most of the datatypes, but still mpi.h file reports '0' for corresponding datatype. /* Whether we have FORTRAN LOGICAL*1 or not */ #define OMPI_HAVE_FORTRAN_LOGICAL1 0 /* Whether we have FORTRAN LOGICAL*2 or not */ #define OMPI_HAVE_FORTRAN_LOGICAL2 0 /* Whether we have FORTRAN LOGICAL*4 or not */ #define OMPI_HAVE_FORTRAN_LOGICAL4 0 /* Whether we have FORTRAN LOGICAL*8 or not */ #define OMPI_HAVE_FORTRAN_LOGICAL8 0 /* Whether we have FORTRAN INTEGER*1 or not */ #define OMPI_HAVE_FORTRAN_INTEGER1 0 /* Whether we have FORTRAN INTEGER*16 or not */ #define OMPI_HAVE_FORTRAN_INTEGER16 0 /* Whether we have FORTRAN INTEGER*2 or not */ #define OMPI_HAVE_FORTRAN_INTEGER2 0 /* Whether we have FORTRAN INTEGER*4 or not */ #define OMPI_HAVE_FORTRAN_INTEGER4 0 /* Whether we have FORTRAN INTEGER*8 or not */ #define OMPI_HAVE_FORTRAN_INTEGER8 0 /* Whether we have FORTRAN REAL*16 or not */ #define OMPI_HAVE_FORTRAN_REAL16 0 /* Whether we have FORTRAN REAL*2 or not */ #define OMPI_HAVE_FORTRAN_REAL2 0 /* Whether we have FORTRAN REAL*4 or not */ #define OMPI_HAVE_FORTRAN_REAL4 0 /* Whether we have FORTRAN REAL*8 or not */ #define OMPI_HAVE_FORTRAN_REAL8 0 == Any idea on why mpi.h is setting zero for all above fortran datatypes despite fortran compiler supports most of the datatypes (see cmake_gui_output2.txt)??? Thank you in advance. -Hiral Checking for working Fortran compiler... Checking for working Fortran compiler...ifort.exe Check ifort.exe external symbol convention... Check ifort.exe external symbol convention...upper case Check if Fortran 77 compiler supports CHARACTER... Check if Fortran 77 compiler supports CHARACTER...yes Check size of Fortran 77 CHARACTER... Check size of Fortran 77 CHARACTER...1 Check corresponding C type of CHARACTER... Check corresponding C type of CHARACTER... char Check alignment of Fortran CHARACTER... Check alignment of Fortran CHARACTER...1 Check if Fortran 77 compiler supports LOGICAL... Check if Fortran 77 compiler supports LOGICAL...yes Check size of Fortran 77 LOGICAL... Check size of Fortran 77 LOGICAL...4 Check corresponding C type of LOGICAL... Check corresponding C type of LOGICAL... int Check alignment of Fortran LOGICAL... Check alignment of Fortran LOGICAL...4 Check if Fortran 77 compiler supports LOGICAL*1... Check if Fortran 77 compiler supports LOGICAL*1...yes Check size of Fortran 77 LOGICAL*1... Check size of Fortran 77 LOGICAL*1...1 Check corresponding C type of LOGICAL*1... Check corresponding C type of LOGICAL*1... char Check alignment of Fortran LOGICAL*1... Check alignment of Fortran LOGICAL*1...1 Check if Fortran 77 compiler supports LOGICAL*2... Check if Fortran 77 compiler supports LOGICAL*2...yes Check size of Fortran 77 LOGICAL*2... Check size of Fortran 77 LOGICAL*2...2 Check corresponding C type of LOGICAL*2... Check corresponding C type of LOGICAL*2... short Check alignment of Fortran LOGICAL*2... Check alignment of Fortran LOGICAL*2...2 Check if Fortran 77 compiler supports LOGICAL*4... Check if Fortran 77 compiler supports LOGICAL*4...yes Check size of Fortran 77 LOGICAL*4... Check size of Fortran 77 LOGICAL*4...4 Check corresponding C type of LOGICAL*4... Check corresponding C type of LOGICAL*4... int Check alignment of Fortran LOGICAL*4... Check alignment of Fortran LOGICAL*4...4 Check if Fortran 77 compiler supports LOGICAL*8... Check if Fortran 77 compiler supports LOGICAL*8...yes Check size of Fortran 77 LOGICAL*8... Check size of Fortran 77 LOGICAL*8...8 Check corresponding C type of LOGICAL*8... Check corresponding C type of LOGICAL*8... long long Check alignment of Fortran LOGICAL*8... Check alignment of Fortran LOGICAL*8...8 Check if Fortran 77 compiler supports INTEGER... Check if Fortran 77 compiler supports INTEGER...yes Check size of Fortran 77 INTEGER... Check size of Fortran 77 INTEGER...4 Check corresponding C type of INTEGER... Check corresponding C type of INTEGER... int Check alignment of Fortran INTEGER... Check alignment of Fortran INTEGER...4 Check if Fortran 77 compiler supports INTEGER*1... Check if Fortran 77 compiler supports INTEGER*1...yes Check size of Fortran 77 INTEGER*1... Check size of Fortran 77 INTEGER*1...1 Check corresponding C type of INTEGER*1... Check
Re: [OMPI users] Windows: MPI_Allreduce() crashes when using MPI_DOUBLE_PRECISION
Hi Rainer / Jeff / Shiqing, Did you get a chance to try MPI_AllReduce() FORTRAN test program (using INTEGER and REAL) attached with this thread? Thank you. -Hiral
Re: [OMPI users] Sorry! You were supposed to get help about: But couldn't open help-orterun.txt
Can you please suggest fix or some workaround? Thank you. -Hiral
Re: [OMPI users] Sorry! You were supposed to get help about: But couldn't open help-orterun.txt
Hi Ralph, I tried following... 1) C:\test> mpirun -mca orte_headnode_name where is returned by 'hostname' command. 2) C:\test> mpirun -mca ras ^ccp but still observing same errors... BTW: for further inforamtion on ompi_info you can see thread http://www.open-mpi.org/community/lists/users/2011/05/16554.php Thank you. -Hiral On 5/18/11, Ralph Castain <r...@open-mpi.org> wrote: > I'm no Windozer, and our developer in that area is away for awhile. However, > looking over the code, I can see where this might be failing. > > The Win allocator appears to be trying to connect to some cluster server - > failing that, it aborts. > > If you just want to launch local, I would suggest adding "-mca ras ^ccp" to > your mpirun cmd line. This will allow the system to pickup the local host > and use it. > > BTW: your orte_headnode_name value is supposed to be whatever is returned by > the "hostname" command on your head node (probably the node where you are > executing mpirun), not the literal "HEADNODE_NAME" string. You might try it > with that correction as well. > > > On May 18, 2011, at 4:26 AM, hi wrote: > >> Any comment / suggestion on how to resolve this? >> >> Thank you. >> -Hiral >> >> On 5/12/11, hi <hiralsmaill...@gmail.com> wrote: >>> Hi, >>> >>> Clarifications: >>> - I have downloaded pre-build OpenMPI_v1..5.3-x64 from open-mpi.org >>> - installed it on Window 7 >>> - and then copied OpenMPI_v1..5.3-x64 directory from Windows 7 to >>> Windows Server 2008 into different directory and also in same >>> directory >>> >>> Now on Windows Server 2008, I am observing these errors... >>> >>> c:\ompi_tests\win64>mpirun mar_f_i_op.exe >>> [nbld-w08:04820] [[30632,0],0] ORTE_ERROR_LOG: Error in file >>> ..\..\..\openmpi-1.5.3\orte\mca\ras\base\ras_base_allocate.c at line >>> 147 >>> [nbld-w08:04820] [[30632,0],0] ORTE_ERROR_LOG: Error in file >>> ..\..\..\openmpi-1.5.3\orte\mca\plm\base\plm_base_launch_support.c at >>> line 99 >>> [nbld-w08:04820] [[30632,0],0] ORTE_ERROR_LOG: Error in file >>> ..\..\..\openmpi-1.5.3\orte\mca\plm\ccp\plm_ccp_module.c at line 186 >>> = >>> >>> As suggested, I tried with following but nothing worked... >>> - copied to the same directory as it was in previous machine >>> - executed "mpirun -mca orte_headnode_name HEADNODE_NAME" and "mpirun >>> -mca orte_headnode_name MYHOSTNAME" >>> - set OPENMPI_HOME and other OPAL_* env variables as follow... >>> >>> set OPENMPI_HOME=C:\MPIs\OpenMPI_v1.5.3-x64 >>> set OPAL_PREFIX=C:\MPIs\OpenMPI_v1.5.3-x64 >>> set OPAL_EXEC_PREFIX=C:\MPIs\OpenMPI_v1.5.3-x64 >>> set OPAL_BINDIR=C:\MPIs\OpenMPI_v1.5.3-x64\bin >>> set OPAL_SBINDIR=C:\MPIs\OpenMPI_v1.5.3-x64\sbin >>> set OPAL_LIBEXECDIR=C:\MPIs\OpenMPI_v1.5.3-x64\libexec >>> set OPAL_DATAROOTDIR=C:\MPIs\OpenMPI_v1.5.3-x64\share >>> set OPAL_DATADIR=C:\MPIs\OpenMPI_v1.5.3-x64\share >>> set OPAL_SYSCONFDIR=C:\MPIs\OpenMPI_v1.5.3-x64\etc >>> set OPAL_LOCALSTATEDIR=C:\MPIs\OpenMPI_v1.5.3-x64\etc >>> set OPAL_LIBDIR=C:\MPIs\OpenMPI_v1.5.3-x64\lib >>> set OPAL_INCLUDEDIR=C:\MPIs\OpenMPI_v1.5.3-x64\include >>> set OPAL_INFODIR=C:\MPIs\OpenMPI_v1.5.3-x64\share\info >>> set OPAL_MANDIR=C:\MPIs\OpenMPI_v1.5.3-x64\share\man >>> set OPAL_PKGDATADIR=C:\MPIs\OpenMPI_v1.5.3-x64\share\openmpi >>> set OPAL_PKGLIBDIR=C:\MPIs\OpenMPI_v1.5.3-x64\lib\openmpi >>> set OPAL_PKGINCLUDEDIR=C:\MPIs\OpenMPI_v1.5.3-x64\include\openmpi >>> >>> Please correct if I missed any other env variable. >>> >>> Thank you. >>> -Hiral >>> >>> >>> On Wed, May 11, 2011 at 8:56 PM, Shiqing Fan <hpc...@hlrs.de> wrote: >>>> Hi, >>>> >>>> The error message means that Open MPI couldn't allocate any compute >>>> node. >>>> It might because the headnode wasn't discovered. You could try with >>>> option >>>> "-mca orte_headnode_name HEADNODE_NAME" in the mpirun command line >>>> (mpirun >>>> --help will show how to use it) . >>>> >>>> And Jeff is also right, special care should be taken for the executable >>>> paths, and it's better to use UNC path. >>>> >>>> To clarify the path issue, if you just copy the OMPI dir to another >>>> computer, there might also be another problem that OMPI couldn't load >>>> the >>
Re: [OMPI users] Sorry! You were supposed to get help about: But couldn't open help-orterun.txt
Any comment / suggestion on how to resolve this? Thank you. -Hiral On 5/12/11, hi <hiralsmaill...@gmail.com> wrote: > Hi, > > Clarifications: > - I have downloaded pre-build OpenMPI_v1..5.3-x64 from open-mpi.org > - installed it on Window 7 > - and then copied OpenMPI_v1..5.3-x64 directory from Windows 7 to > Windows Server 2008 into different directory and also in same > directory > > Now on Windows Server 2008, I am observing these errors... > > c:\ompi_tests\win64>mpirun mar_f_i_op.exe > [nbld-w08:04820] [[30632,0],0] ORTE_ERROR_LOG: Error in file > ..\..\..\openmpi-1.5.3\orte\mca\ras\base\ras_base_allocate.c at line > 147 > [nbld-w08:04820] [[30632,0],0] ORTE_ERROR_LOG: Error in file > ..\..\..\openmpi-1.5.3\orte\mca\plm\base\plm_base_launch_support.c at > line 99 > [nbld-w08:04820] [[30632,0],0] ORTE_ERROR_LOG: Error in file > ..\..\..\openmpi-1.5.3\orte\mca\plm\ccp\plm_ccp_module.c at line 186 > = > > As suggested, I tried with following but nothing worked... > - copied to the same directory as it was in previous machine > - executed "mpirun -mca orte_headnode_name HEADNODE_NAME" and "mpirun > -mca orte_headnode_name MYHOSTNAME" > - set OPENMPI_HOME and other OPAL_* env variables as follow... > > set OPENMPI_HOME=C:\MPIs\OpenMPI_v1.5.3-x64 > set OPAL_PREFIX=C:\MPIs\OpenMPI_v1.5.3-x64 > set OPAL_EXEC_PREFIX=C:\MPIs\OpenMPI_v1.5.3-x64 > set OPAL_BINDIR=C:\MPIs\OpenMPI_v1.5.3-x64\bin > set OPAL_SBINDIR=C:\MPIs\OpenMPI_v1.5.3-x64\sbin > set OPAL_LIBEXECDIR=C:\MPIs\OpenMPI_v1.5.3-x64\libexec > set OPAL_DATAROOTDIR=C:\MPIs\OpenMPI_v1.5.3-x64\share > set OPAL_DATADIR=C:\MPIs\OpenMPI_v1.5.3-x64\share > set OPAL_SYSCONFDIR=C:\MPIs\OpenMPI_v1.5.3-x64\etc > set OPAL_LOCALSTATEDIR=C:\MPIs\OpenMPI_v1.5.3-x64\etc > set OPAL_LIBDIR=C:\MPIs\OpenMPI_v1.5.3-x64\lib > set OPAL_INCLUDEDIR=C:\MPIs\OpenMPI_v1.5.3-x64\include > set OPAL_INFODIR=C:\MPIs\OpenMPI_v1.5.3-x64\share\info > set OPAL_MANDIR=C:\MPIs\OpenMPI_v1.5.3-x64\share\man > set OPAL_PKGDATADIR=C:\MPIs\OpenMPI_v1.5.3-x64\share\openmpi > set OPAL_PKGLIBDIR=C:\MPIs\OpenMPI_v1.5.3-x64\lib\openmpi > set OPAL_PKGINCLUDEDIR=C:\MPIs\OpenMPI_v1.5.3-x64\include\openmpi > > Please correct if I missed any other env variable. > > Thank you. > -Hiral > > > On Wed, May 11, 2011 at 8:56 PM, Shiqing Fan <hpc...@hlrs.de> wrote: >> Hi, >> >> The error message means that Open MPI couldn't allocate any compute node. >> It might because the headnode wasn't discovered. You could try with option >> "-mca orte_headnode_name HEADNODE_NAME" in the mpirun command line (mpirun >> --help will show how to use it) . >> >> And Jeff is also right, special care should be taken for the executable >> paths, and it's better to use UNC path. >> >> To clarify the path issue, if you just copy the OMPI dir to another >> computer, there might also be another problem that OMPI couldn't load the >> registry entries, as the registry entries were set during the installation >> phase on the specific computer. In 1.5.3, a overall env "OPENMPI_HOME" >> will do the work. >> >> Regards, >> Shiqing >> - 原始邮件 - >> 发件人: Jeff Squyres <jsquy...@cisco.com> >> 收件人: Open MPI Users <us...@open-mpi.org> >> 已发送邮件: Wed, 11 May 2011 15:21:26 +0200 (CEST) >> 主题: Re: [OMPI users] Sorry! You were supposed to get help about: But >> couldn't open help-orterun.txt >> >> On May 11, 2011, at 5:50 AM, Ralph Castain wrote: >> >>>> Clarification: I installed pre-built OpenMPI_v1.5.3-x64 on Windows 7 >>>> and copied this directory into Windows Server 2008. >> >> Did you copy OMPI to the same directory tree that you built it? >> >> OMPI hard-codes some directory names when it builds, and it expects to >> find that directory structure when it runs. If you build OMPI with a >> --prefix of /foo, but then move it to /bar, various things may not work >> (like finding help messages, etc.) unless you set the OMPI/OPAL >> environment variables that tell OMPI where the files are actually >> located. >> >> -- >> Jeff Squyres >> jsquy...@cisco.com >> For corporate legal information go to: >> http://www.cisco.com/web/about/doing_business/legal/cri/ >> >> >> ___ >> users mailing list >> us...@open-mpi.org >> http://www.open-mpi.org/mailman/listinfo.cgi/users >> >> >
Re: [OMPI users] Windows: MPI_Allreduce() crashes when using MPI_DOUBLE_PRECISION
Did you tried these test programs? Or any suggestion to overcome this bug??? Thank you. -Hiral On Fri, May 13, 2011 at 11:20 AM, hi <hiralsmaill...@gmail.com> wrote: > Hi Rainer, > >> Does REAL work for You? > No. > I am observing same errors (see below) even with INTEGER; please find > the attached test programs with INTEGER and REAL. > > C:\test> mpirun mar_f_i.exe > size= 1 , rank= 0 > start --, rcvbuf= 0 0 0 0 0 > end --, rcvbuf= 2 2 2 2 2 > > C:\test> mpirun -np 2 mar_f_i.exe > size= 2 , rank= 0 > start --, rcvbuf= 0 0 0 0 0 > size= 2 , rank= 1 > start --, rcvbuf= 0 0 0 0 0 > forrtl: severe (157): Program Exception - access violation > Image PC Routine Line Source > [vibgyor:12628] [[31763,0],0]-[[31763,1],0] mca_oob_tcp_msg_recv: > readv failed: Unknown error (108) > -- > WARNING: A process refused to die! > > Host: vibgyor > PID: 488 > > This process may still be running and/or consuming resources. > > -- > -- > mpirun has exited due to process rank 0 with PID 452 on node vibgyor > exiting improperly. There are two reasons this could occur: > > 1. this process did not call "init" before exiting, but others in the > job did. This can cause a job to hang indefinitely while it waits for > all processes to call "init". By rule, if one process calls "init", > then ALL processes must call "init" prior to termination. > > 2. this process called "init", but exited without calling "finalize". > By rule, all processes that call "init" MUST call "finalize" prior to > exiting or it will be considered an "abnormal termination" > > This may have caused other processes in the application to be > terminated by signals sent by mpirun (as reported here). > -- > > > Thank you. > -Hiral > > > On Thu, May 12, 2011 at 9:03 PM, Rainer Keller <kel...@hlrs.de> wrote: >> Hello Hiral, >> in the ompi_info You attached, the fortran size detection did not work >> correctly (on viscluster -- aka that shows the you used the std.-installation >> package): >> ... >> Fort dbl prec size: 4 >> ... >> >> This most probably does not match Your compiler's setting for DOUBLE >> PRECISION, which probably considers this to be 8. >> >> Does REAL work for You? >> >> Shiqing is currently away, will ask when he returns. >> >> With best regards, >> Rainer >> >> >> On Wednesday 11 May 2011 09:29:03 hi wrote: >>> Hi Jeff, >>> >>> > Can you send the info listed on the help page? >>> > >>> >From the HELP page... >>> >>> ***For run-time problems: >>> 1) Check the FAQ first. Really. This can save you a lot of time; many >>> common problems and solutions are listed there. >>> I couldn't find reference in FAQ. >>> >>> 2) The version of Open MPI that you're using. >>> I am using pre-built openmpi-1.5.3 64-bit and 32-bit binaries on Window 7 >>> I also tried with locally built openmpi-1.5.2 using Visual Studio 2008 >>> 32-bit compilers >>> I tried various compilers: VS-9 32-bit and VS-10 64-bit and >>> corresponding intel ifort compiler. >>> >>> 3) The config.log file from the top-level Open MPI directory, if >>> available (please compress!). >>> Don't have. >>> >>> 4) The output of the "ompi_info --all" command from the node where >>> you're invoking mpirun. >>> see output of pre-built openmpi-1.5.3_x64/bin/ompi_info --all" in >>> attachments. >>> >>> 5) If running on more than one node -- >>> I am running test program on single none. >>> >>> 6) A detailed description of what is failing. >>> Already described in this post. >>> >>> 7) Please include information about your network: >>> As I am running test program on local and single machine, this might >>> not be required. >>> >>> > You forgot ierr in t
Re: [OMPI users] Windows: MPI_Allreduce() crashes when using MPI_DOUBLE_PRECISION
Can please try this test program on Windows environment. Thank you. -Hiral On Thu, May 12, 2011 at 10:59 AM, hi <hiralsmaill...@gmail.com> wrote: > Any comment or suggestion on my below update > > > > On Wed, May 11, 2011 at 12:59 PM, hi <hiralsmaill...@gmail.com> wrote: >> Hi Jeff, >> >>> Can you send the info listed on the help page? >> >> From the HELP page... >> >> ***For run-time problems: >> 1) Check the FAQ first. Really. This can save you a lot of time; many >> common problems and solutions are listed there. >> I couldn't find reference in FAQ. >> >> 2) The version of Open MPI that you're using. >> I am using pre-built openmpi-1.5.3 64-bit and 32-bit binaries on Window 7 >> I also tried with locally built openmpi-1.5.2 using Visual Studio 2008 >> 32-bit compilers >> I tried various compilers: VS-9 32-bit and VS-10 64-bit and >> corresponding intel ifort compiler. >> >> 3) The config.log file from the top-level Open MPI directory, if >> available (please compress!). >> Don't have. >> >> 4) The output of the "ompi_info --all" command from the node where >> you're invoking mpirun. >> see output of pre-built openmpi-1.5.3_x64/bin/ompi_info --all" in >> attachments. >> >> 5) If running on more than one node -- >> I am running test program on single none. >> >> 6) A detailed description of what is failing. >> Already described in this post. >> >> 7) Please include information about your network: >> As I am running test program on local and single machine, this might >> not be required. >> >>> You forgot ierr in the call to MPI_Finalize. You also paired >>> DOUBLE_PRECISION data with MPI_INTEGER in the call to allreduce. And you >>> mixed sndbuf and rcvbuf in the call to allreduce, meaning that when your >>> print rcvbuf afterwards, it'll always still be 0. >> >> As I am not Fortran programmer, this is my mistake !!! >> >> >>> program Test_MPI >>> use mpi >>> implicit none >>> >>> DOUBLE PRECISION rcvbuf(5), sndbuf(5) >>> INTEGER nproc, rank, ierr, n, i, ret >>> >>> n = 5 >>> do i = 1, n >>> sndbuf(i) = 2.0 >>> rcvbuf(i) = 0.0 >>> end do >>> >>> call MPI_INIT(ierr) >>> call MPI_COMM_RANK(MPI_COMM_WORLD, rank, ierr) >>> call MPI_COMM_SIZE(MPI_COMM_WORLD, nproc, ierr) >>> write(*,*) "size=", nproc, ", rank=", rank >>> write(*,*) "start --, rcvbuf=", rcvbuf >>> CALL MPI_ALLREDUCE(sndbuf, rcvbuf, n, >>> & MPI_DOUBLE_PRECISION, MPI_SUM, MPI_COMM_WORLD, ierr) >>> write(*,*) "end --, rcvbuf=", rcvbuf >>> >>> CALL MPI_Finalize(ierr) >>> end >>> >>> (you could use "include 'mpif.h'", too -- I tried both) >>> >>> This program works fine for me. >> >> I am observing same crash, as described in this thread (when executing >> as "mpirun -np 2 mar_f_dp.exe"), even with above correct and simple >> test program. I commented 'use mpi' as it gave me "Error in compiled >> module file" error, so I used 'include "mpif.h"' statement (see >> attachement). >> >> It seems that Windows specific issue, (I could run this test program >> on Linux with openmpi-1.5.1). >> >> Can anybody try this test program on Windows? >> >> Thank you in advance. >> -Hiral >> >
Re: [OMPI users] Sorry! You were supposed to get help about: But couldn't open help-orterun.txt
Hi, Clarifications: - I have downloaded pre-build OpenMPI_v1..5.3-x64 from open-mpi.org - installed it on Window 7 - and then copied OpenMPI_v1..5.3-x64 directory from Windows 7 to Windows Server 2008 into different directory and also in same directory Now on Windows Server 2008, I am observing these errors... c:\ompi_tests\win64>mpirun mar_f_i_op.exe [nbld-w08:04820] [[30632,0],0] ORTE_ERROR_LOG: Error in file ..\..\..\openmpi-1.5.3\orte\mca\ras\base\ras_base_allocate.c at line 147 [nbld-w08:04820] [[30632,0],0] ORTE_ERROR_LOG: Error in file ..\..\..\openmpi-1.5.3\orte\mca\plm\base\plm_base_launch_support.c at line 99 [nbld-w08:04820] [[30632,0],0] ORTE_ERROR_LOG: Error in file ..\..\..\openmpi-1.5.3\orte\mca\plm\ccp\plm_ccp_module.c at line 186 = As suggested, I tried with following but nothing worked... - copied to the same directory as it was in previous machine - executed "mpirun -mca orte_headnode_name HEADNODE_NAME" and "mpirun -mca orte_headnode_name MYHOSTNAME" - set OPENMPI_HOME and other OPAL_* env variables as follow... set OPENMPI_HOME=C:\MPIs\OpenMPI_v1.5.3-x64 set OPAL_PREFIX=C:\MPIs\OpenMPI_v1.5.3-x64 set OPAL_EXEC_PREFIX=C:\MPIs\OpenMPI_v1.5.3-x64 set OPAL_BINDIR=C:\MPIs\OpenMPI_v1.5.3-x64\bin set OPAL_SBINDIR=C:\MPIs\OpenMPI_v1.5.3-x64\sbin set OPAL_LIBEXECDIR=C:\MPIs\OpenMPI_v1.5.3-x64\libexec set OPAL_DATAROOTDIR=C:\MPIs\OpenMPI_v1.5.3-x64\share set OPAL_DATADIR=C:\MPIs\OpenMPI_v1.5.3-x64\share set OPAL_SYSCONFDIR=C:\MPIs\OpenMPI_v1.5.3-x64\etc set OPAL_LOCALSTATEDIR=C:\MPIs\OpenMPI_v1.5.3-x64\etc set OPAL_LIBDIR=C:\MPIs\OpenMPI_v1.5.3-x64\lib set OPAL_INCLUDEDIR=C:\MPIs\OpenMPI_v1.5.3-x64\include set OPAL_INFODIR=C:\MPIs\OpenMPI_v1.5.3-x64\share\info set OPAL_MANDIR=C:\MPIs\OpenMPI_v1.5.3-x64\share\man set OPAL_PKGDATADIR=C:\MPIs\OpenMPI_v1.5.3-x64\share\openmpi set OPAL_PKGLIBDIR=C:\MPIs\OpenMPI_v1.5.3-x64\lib\openmpi set OPAL_PKGINCLUDEDIR=C:\MPIs\OpenMPI_v1.5.3-x64\include\openmpi Please correct if I missed any other env variable. Thank you. -Hiral On Wed, May 11, 2011 at 8:56 PM, Shiqing Fan <hpc...@hlrs.de> wrote: > Hi, > > The error message means that Open MPI couldn't allocate any compute node. It > might because the headnode wasn't discovered. You could try with option "-mca > orte_headnode_name HEADNODE_NAME" in the mpirun command line (mpirun --help > will show how to use it) . > > And Jeff is also right, special care should be taken for the executable > paths, and it's better to use UNC path. > > To clarify the path issue, if you just copy the OMPI dir to another computer, > there might also be another problem that OMPI couldn't load the registry > entries, as the registry entries were set during the installation phase on > the specific computer. In 1.5.3, a overall env "OPENMPI_HOME" will do the > work. > > Regards, > Shiqing > - 原始邮件 - > 发件人: Jeff Squyres <jsquy...@cisco.com> > 收件人: Open MPI Users <us...@open-mpi.org> > 已发送邮件: Wed, 11 May 2011 15:21:26 +0200 (CEST) > 主题: Re: [OMPI users] Sorry! You were supposed to get help about: But > couldn't open help-orterun.txt > > On May 11, 2011, at 5:50 AM, Ralph Castain wrote: > >>> Clarification: I installed pre-built OpenMPI_v1.5.3-x64 on Windows 7 >>> and copied this directory into Windows Server 2008. > > Did you copy OMPI to the same directory tree that you built it? > > OMPI hard-codes some directory names when it builds, and it expects to find > that directory structure when it runs. If you build OMPI with a --prefix of > /foo, but then move it to /bar, various things may not work (like finding > help messages, etc.) unless you set the OMPI/OPAL environment variables that > tell OMPI where the files are actually located. > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > > ___ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users > >
Re: [OMPI users] Windows: MPI_Allreduce() crashes when using MPI_DOUBLE_PRECISION
Any comment or suggestion on my below update On Wed, May 11, 2011 at 12:59 PM, hi <hiralsmaill...@gmail.com> wrote: > Hi Jeff, > >> Can you send the info listed on the help page? > > From the HELP page... > > ***For run-time problems: > 1) Check the FAQ first. Really. This can save you a lot of time; many > common problems and solutions are listed there. > I couldn't find reference in FAQ. > > 2) The version of Open MPI that you're using. > I am using pre-built openmpi-1.5.3 64-bit and 32-bit binaries on Window 7 > I also tried with locally built openmpi-1.5.2 using Visual Studio 2008 > 32-bit compilers > I tried various compilers: VS-9 32-bit and VS-10 64-bit and > corresponding intel ifort compiler. > > 3) The config.log file from the top-level Open MPI directory, if > available (please compress!). > Don't have. > > 4) The output of the "ompi_info --all" command from the node where > you're invoking mpirun. > see output of pre-built openmpi-1.5.3_x64/bin/ompi_info --all" in attachments. > > 5) If running on more than one node -- > I am running test program on single none. > > 6) A detailed description of what is failing. > Already described in this post. > > 7) Please include information about your network: > As I am running test program on local and single machine, this might > not be required. > >> You forgot ierr in the call to MPI_Finalize. You also paired >> DOUBLE_PRECISION data with MPI_INTEGER in the call to allreduce. And you >> mixed sndbuf and rcvbuf in the call to allreduce, meaning that when your >> print rcvbuf afterwards, it'll always still be 0. > > As I am not Fortran programmer, this is my mistake !!! > > >> program Test_MPI >> use mpi >> implicit none >> >> DOUBLE PRECISION rcvbuf(5), sndbuf(5) >> INTEGER nproc, rank, ierr, n, i, ret >> >> n = 5 >> do i = 1, n >> sndbuf(i) = 2.0 >> rcvbuf(i) = 0.0 >> end do >> >> call MPI_INIT(ierr) >> call MPI_COMM_RANK(MPI_COMM_WORLD, rank, ierr) >> call MPI_COMM_SIZE(MPI_COMM_WORLD, nproc, ierr) >> write(*,*) "size=", nproc, ", rank=", rank >> write(*,*) "start --, rcvbuf=", rcvbuf >> CALL MPI_ALLREDUCE(sndbuf, rcvbuf, n, >> & MPI_DOUBLE_PRECISION, MPI_SUM, MPI_COMM_WORLD, ierr) >> write(*,*) "end --, rcvbuf=", rcvbuf >> >> CALL MPI_Finalize(ierr) >> end >> >> (you could use "include 'mpif.h'", too -- I tried both) >> >> This program works fine for me. > > I am observing same crash, as described in this thread (when executing > as "mpirun -np 2 mar_f_dp.exe"), even with above correct and simple > test program. I commented 'use mpi' as it gave me "Error in compiled > module file" error, so I used 'include "mpif.h"' statement (see > attachement). > > It seems that Windows specific issue, (I could run this test program > on Linux with openmpi-1.5.1). > > Can anybody try this test program on Windows? > > Thank you in advance. > -Hiral >
Re: [OMPI users] Sorry! You were supposed to get help about: But couldn't open help-orterun.txt
After setting OPAL_PKGDATADIR, "mpirun" gives proper help message. But when executing simple test program which calls MPI_ALLREDUCE() it gives following errors onto the console... c:\ompi_tests\win64>mpirun mar_f_i_op.exe [nbld-w08:04820] [[30632,0],0] ORTE_ERROR_LOG: Error in file ..\..\..\openmpi-1.5.3\orte\mca\ras\base\ras_base_allocate.c at line 147 [nbld-w08:04820] [[30632,0],0] ORTE_ERROR_LOG: Error in file ..\..\..\openmpi-1.5.3\orte\mca\plm\base\plm_base_launch_support.c at line 99 [nbld-w08:04820] [[30632,0],0] ORTE_ERROR_LOG: Error in file ..\..\..\openmpi-1.5.3\orte\mca\plm\ccp\plm_ccp_module.c at line 186 Any idea on these errors??? Clarification: I installed pre-built OpenMPI_v1.5.3-x64 on Windows 7 and copied this directory into Windows Server 2008. Thank you in advance. -Hiral
Re: [OMPI users] Sorry! You were supposed to get help about: But couldn't open help-orterun.txt
It's my mistake it should be OPAL_PKGDATADIR env var instead of OPAL_DATADIR. With this it is working fine. Thank you. -Hiral
[OMPI users] Sorry! You were supposed to get help about: But couldn't open help-orterun.txt
Hi, I am observing following message on Windows platform... c:\Users\oza\Desktop\test>mpirun -- orterun:executable-not-specified But I couldn't open the help file: C:\Users\hpcfan\Documents\OpenMPI\openmpi-1.5.3\installed-64\share\openmpi\help-orterun.txt: No such file or directory. Sorry! -- I copied pre-built installed "OpenMPI_v1.5.3-x64" directory into one Windows machine to another Windows machine. As discussed in some mailing-threads I also tried to set OPAL_PKGDATA and other OPAL_* environment variables, but still above message persist. Please suggest. Thank you in advance. -Hiral
Re: [OMPI users] Windows: MPI_Allreduce() crashes when using MPI_DOUBLE_PRECISION
Hi Jeff, > Can you send the info listed on the help page? >From the HELP page... ***For run-time problems: 1) Check the FAQ first. Really. This can save you a lot of time; many common problems and solutions are listed there. I couldn't find reference in FAQ. 2) The version of Open MPI that you're using. I am using pre-built openmpi-1.5.3 64-bit and 32-bit binaries on Window 7 I also tried with locally built openmpi-1.5.2 using Visual Studio 2008 32-bit compilers I tried various compilers: VS-9 32-bit and VS-10 64-bit and corresponding intel ifort compiler. 3) The config.log file from the top-level Open MPI directory, if available (please compress!). Don't have. 4) The output of the "ompi_info --all" command from the node where you're invoking mpirun. see output of pre-built openmpi-1.5.3_x64/bin/ompi_info --all" in attachments. 5) If running on more than one node -- I am running test program on single none. 6) A detailed description of what is failing. Already described in this post. 7) Please include information about your network: As I am running test program on local and single machine, this might not be required. > You forgot ierr in the call to MPI_Finalize. You also paired > DOUBLE_PRECISION data with MPI_INTEGER in the call to allreduce. And you > mixed sndbuf and rcvbuf in the call to allreduce, meaning that when your > print rcvbuf afterwards, it'll always still be 0. As I am not Fortran programmer, this is my mistake !!! > program Test_MPI > use mpi > implicit none > > DOUBLE PRECISION rcvbuf(5), sndbuf(5) > INTEGER nproc, rank, ierr, n, i, ret > > n = 5 > do i = 1, n > sndbuf(i) = 2.0 > rcvbuf(i) = 0.0 > end do > > call MPI_INIT(ierr) > call MPI_COMM_RANK(MPI_COMM_WORLD, rank, ierr) > call MPI_COMM_SIZE(MPI_COMM_WORLD, nproc, ierr) > write(*,*) "size=", nproc, ", rank=", rank > write(*,*) "start --, rcvbuf=", rcvbuf > CALL MPI_ALLREDUCE(sndbuf, rcvbuf, n, > & MPI_DOUBLE_PRECISION, MPI_SUM, MPI_COMM_WORLD, ierr) > write(*,*) "end --, rcvbuf=", rcvbuf > > CALL MPI_Finalize(ierr) > end > > (you could use "include 'mpif.h'", too -- I tried both) > > This program works fine for me. I am observing same crash, as described in this thread (when executing as "mpirun -np 2 mar_f_dp.exe"), even with above correct and simple test program. I commented 'use mpi' as it gave me "Error in compiled module file" error, so I used 'include "mpif.h"' statement (see attachement). It seems that Windows specific issue, (I could run this test program on Linux with openmpi-1.5.1). Can anybody try this test program on Windows? Thank you in advance. -Hiral Package: Open MPI hpcfan@VISCLUSTER25 Distribution Open MPI: 1.5.3 Open MPI SVN revision: r24532 Open MPI release date: Mar 16, 2011 Open RTE: 1.5.3 Open RTE SVN revision: r24532 Open RTE release date: Mar 16, 2011 OPAL: 1.5.3 OPAL SVN revision: r24532 OPAL release date: Mar 16, 2011 Ident string: 1.5.3 MCA backtrace: none (MCA v2.0, API v2.0, Component v1.5.3) MCA carto: auto_detect (MCA v2.0, API v2.0, Component v1.5.3) MCA maffinity: first_use (MCA v2.0, API v2.0, Component v1.5.3) MCA timer: windows (MCA v2.0, API v2.0, Component v1.5.3) MCA installdirs: env (MCA v2.0, API v2.0, Component v1.5.3) MCA installdirs: windows (MCA v2.0, API v2.0, Component v1.5.3) MCA installdirs: config (MCA v2.0, API v2.0, Component v1.5.3) MCA dpm: orte (MCA v2.0, API v2.0, Component v1.5.3) MCA pubsub: orte (MCA v2.0, API v2.0, Component v1.5.3) MCA allocator: bucket (MCA v2.0, API v2.0, Component v1.5.3) MCA allocator: basic (MCA v2.0, API v2.0, Component v1.5.3) MCA coll: sync (MCA v2.0, API v2.0, Component v1.5.3) MCA coll: sm (MCA v2.0, API v2.0, Component v1.5.3) MCA coll: self (MCA v2.0, API v2.0, Component v1.5.3) MCA coll: hierarch (MCA v2.0, API v2.0, Component v1.5.3) MCA coll: basic (MCA v2.0, API v2.0, Component v1.5.3) MCA mpool: sm (MCA v2.0, API v2.0, Component v1.5.3) MCA mpool: rdma (MCA v2.0, API v2.0, Component v1.5.3) MCA pml: ob1 (MCA v2.0, API v2.0, Component v1.5.3) MCA bml: r2 (MCA v2.0, API v2.0, Component v1.5.3) MCA btl: tcp (MCA v2.0, API v2.0, Component v1.5.3) MCA btl: sm (MCA v2.0, API v2.0, Componen
Re: [OMPI users] Windows: MPI_Allreduce() crashes when using MPI_DOUBLE_PRECISION
Hi Jeff, > You didn't answer my prior questions. :-) I am observing this crash using MPI_ALLREDUCE() in test program; and which does not have any memory corruption issue. ;) > I ran your test program with -np 2 and -np 4 and it seemed to work ok. Can you please let me know what environment (including os, compilers) are you using? I am able to reproduce the crash using attached simplified test program with 5 element array. Please note that these experiments I am doing on Windows7 using msys/mingw console; see attached makefile for more information. When running this program as "C:\>mpirun mar_f_dp2.exe" it works fine; but when running it as "C:\>mpirun -np 2 mar_f_dp2.exe" it generates following error on console... C:\>mpirun -np 2 mar_f_dp2.exe 0 0 0 size= 2 , rank= 0 start -- 0 0 0 size= 2 , rank= 1 start -- forrtl: severe (157): Program Exception - access violation Image PCRoutineLineSource [vibgyor:09168] [[28311,0],0]-[[28311,1],0] mca_oob_tcp_msg_recv: readv failed: Unknown error (108) -- WARNING: A process refused to die! Host: vibgyor PID: 512 This process may still be running and/or consuming resources. -- -- mpirun has exited due to process rank 0 with PID 476 on node vibgyor exiting improperly. There are two reasons this could occur: 1. this process did not call "init" before exiting, but others in the job did. This can cause a job to hang indefinitely while it waits for all processes to call "init". By rule, if one process calls "init", then ALL processes must call "init" prior to termination. 2. this process called "init", but exited without calling "finalize". By rule, all processes that call "init" MUST call "finalize" prior to exiting or it will be considered an "abnormal termination" This may have caused other processes in the application to be terminated by signals sent by mpirun (as reported here). -- Another observation I have with attached test program is that it crashes in MPI_Finilize() on running "C:\>mpirun mar_f_dp2.exe" if we un-comment following lines (lines 27 and 35)... write(*,*) "start --, rcvbuf=", rcvbuf ... write(*,*) "end --, rcvbuf=", rcvbuf Thank you in advance. -Hiral makefile Description: Binary data mar_f_dp2.f Description: Binary data
Re: [OMPI users] Request for F90 bindings for Windows Builds
I also vote for F90 support in OpenMPI.
Re: [OMPI users] Windows: MPI_Allreduce() crashes when using MPI_DOUBLE_PRECISION
Hi Jeff, Test program works fine; but you can notice the difference between the callstack images of test program and of my actual application. In test program it calls mca_coll_self_allreduce_intra while in my application it calls mca_coll_basic_allreduce_intra. So I want to know which parameter or setting makes call to mca_coll_basic_allreduce_intra compared to mca_coll_self_allreduce.intra; if you can comment on this would be helpful. Just for more information: op->o_func.intrinsic.fns[27] points to 0 when using MPI_Allreduce(...,...,...,MPI_DOUBLE_PRECISION, MPI_SUM,...,...) Thank you. -Hiral
[OMPI users] Fwd: Windows: MPI_Allreduce() crashes when using MPI_DOUBLE_PRECISION
Please find test program... mar_f_dp.f Description: Binary data
[OMPI users] Fwd: Windows: MPI_Allreduce() crashes when using MPI_DOUBLE_PRECISION
Please find callstack of test program...
Re: [OMPI users] Windows: MPI_Allreduce() crashes when using MPI_DOUBLE_PRECISION
Please find the callstack of my application...
[OMPI users] Windows: MPI_Allreduce() crashes when using MPI_DOUBLE_PRECISION
Greetings!!!
I am observing crash in MPI_Allreduce() call from my actual application.
After debugging I found that MPI_Allreduce() with MPI_DOUBLE_PRECISION
returns NULL for following code in op.h
if (0 != (op->o_flags & OMPI_OP_FLAGS_INTRINSIC)) {
op->o_func.intrinsic.fns[ompi_op_ddt_map[dtype->id]](source, target,
, ,
op->o_func.intrinsic.modules[ompi_op_ddt_map[dtype->id]]);
where, o_func.intrinsic.fns[27] points to 0.
On further debugging, I found that it is making call to
mca_coll_basic_reduce_lin_intra(); see below trace...
> libmpid.dll!ompi_op_reduce(ompi_op_t * op, void * source, void *
> target, int count, ompi_datatype_t * dtype) Line 500 C++
libmpid.dll!mca_coll_basic_reduce_lin_intra(void * sbuf, void *
rbuf, int count, ompi_datatype_t * dtype, ompi_op_t * op, int root,
ompi_communicator_t * comm, mca_coll_base_module_2_0_0_t * module)
Line 249C++
libmpid.dll!mca_coll_sync_reduce(void * sbuf, void * rbuf, int
count, ompi_datatype_t * dtype, ompi_op_t * op, int root,
ompi_communicator_t * comm, mca_coll_base_module_2_0_0_t * module)
Line 45 + 0xd4 bytesC++
libmpid.dll!mca_coll_basic_allreduce_intra(void * sbuf, void * rbuf,
int count, ompi_datatype_t * dtype, ompi_op_t * op,
ompi_communicator_t * comm, mca_coll_base_module_2_0_0_t * module)
Line 57 + 0x58 bytesC++
libmpid.dll!MPI_Allreduce(void * sendbuf, void * recvbuf, int count,
ompi_datatype_t * datatype, ompi_op_t * op, ompi_communicator_t *
comm) Line 107 + 0x5c bytesC++
libmpi_f77d.dll!mpi_allreduce_f(char * sendbuf, char * recvbuf, int
* count, int * datatype, int * op, int * comm, int * ierr) Line 79 +
0x34 bytes C++
libmpi_f77d.dll!MPI_ALLREDUCE(char * sendbuf, char * recvbuf, int *
count, int * datatype, int * op, int * comm, int * ierr) Line 53 +
0x67 bytes C++
Now to simulate this problem, the attached test program works fine but
I observed completely different callstack see attached images...
Just for information: I am executing my application using following command:
c:/openmpi/bin/orterun -mca mca_component_show_load_errors 0 --prefix
... -x ... -x ... --machinefile ... -np 2 myApplication
And test program using following command:
c:/openmpi/bin/mpirun mar_f_dp.exe
Please let me know based on what criteria "coll_reduce" is pointing to
"mca_coll_basic_allreduce_intra() or mca_coll_self_allreduce_intra();
this would help me to debug my application further.
Thank you in advance.
-Hiral
Re: [OMPI users] Error occurred in MPI_Allreduce on communicator MPI_COMM_WORLD
Hi Peter, Thanks that helped a lot. BTW: please let me know if you any comment on "Windows: MPI_Allreduce() crashes when using MPI_DOUBLE_PRECISION" thread. Thank you. -Hiral 2011/5/4 Peter Kjellström <c...@nsc.liu.se>: > On Wednesday, May 04, 2011 04:04:37 PM hi wrote: >> Greetings !!! >> >> I am observing following error messages when executing attached test >> program... >> >> >> C:\test>mpirun mar_f.exe > ... >> [vbgyor:9920] *** An error occurred in MPI_Allreduce >> [vbgyor:9920] *** on communicator MPI_COMM_WORLD >> [vbgyor:9920] *** MPI_ERR_OP: invalid reduce operation >> [vbgyor:9920] *** MPI_ERRORS_ARE_FATAL (your MPI job will now abort) > > I'm not a fortran programmer but it seems to me that placing the MPI_Allreduce > call in a subroutine like that broke the meaning of MPI_SUM and MPI_REAL in > that scope. Adding: > > include 'mpif.h' > > after SUBROUTINE PAR_BLAS2(m, n, a, b, c, comm) helps. > > /Peter > > ___ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users
[OMPI users] Error occurred in MPI_Allreduce on communicator MPI_COMM_WORLD
Greetings !!! I am observing following error messages when executing attached test program... C:\test>mpirun mar_f.exe 0 0 0 size= 1 , rank= 0 start -- a= 2.002.002.00 2.002.00 b= 3.003.003.00 3.003.003.00 3.003.003.00 3.003.003.00 3.003.003.00 3.003.003.00 3.003.003.00 3.003.003.00 3.00 c= 0.000E+000 0.000E+000 0.000E+000 0.000E+000 0.000E+000 sum= 0.000E+000 0.000E+000 0.000E+000 0.000E+000 0.000E+000 sum= 30.030.030.0 30.030.0 [vbgyor:9920] *** An error occurred in MPI_Allreduce [vbgyor:9920] *** on communicator MPI_COMM_WORLD [vbgyor:9920] *** MPI_ERR_OP: invalid reduce operation [vbgyor:9920] *** MPI_ERRORS_ARE_FATAL (your MPI job will now abort) [vbgyor:09736] [[27471,0],0]-[[27471,1],0] mca_oob_tcp_msg_recv: readv failed: Unknown error (10054) -- mpirun has exited due to process rank 0 with PID 488 on node vbgyor exiting improperly. There are two reasons this could occur: 1. this process did not call "init" before exiting, but others in the job did. This can cause a job to hang indefinitely while it waits for all processes to call "init". By rule, if one process calls "init", then ALL processes must call "init" prior to termination. 2. this process called "init", but exited without calling "finalize". By rule, all processes that call "init" MUST call "finalize" prior to exiting or it will be considered an "abnormal termination" This may have caused other processes in the application to be terminated by signals sent by mpirun (as reported here). -- Environment: OS: Windows 7 64-bit Compilers: Visual Studio 2008 32bit and Intel ifort 32bit OpenMPI: OpenMPI-1.5.2 pre-built libraries and also with locally built libraries Thank you. -Hiral mar_f.f Description: Binary data
Re: [OMPI users] mca_oob_tcp_msg_recv: readv failed:Unknown error (10054)
Hi Ralph, The Fortran code snippet is as follow... <<< ... write(*,*) "calling blacs_pinfo()..." CALL BLACS_PINFO(IAM, NPROCS) write(*,*), "after blacs_pinfo()..." write(*,*), "IAM=", IAM write(*,*), "NPROCS=", NPROCS ... >>> As you can notice, below-mentioned crash is happening in call to BLACS_PINFO(). I am using following environment: OS: Windows 7 64-bit Compilers: Visual Studio 2008 32bit and Intel ifort 32bit OpenMPI: OpenMPI-1.5.3 pre-built libraries and also with OpenMPI-1.5.2. locally built libraries BLACS: pre-built libraries taken from http://icl.cs.utk.edu/lapack-for-windows/scalapack/index.html#librairies Thank you. -Hiral On Tue, Apr 19, 2011 at 6:56 PM, Ralph Castain <r...@open-mpi.org> wrote: > Just a suggestion: have you looked at it in a debugger? The error isn't > coming from OMPI - looks like a segfault caused by an error in the program or > how it is being run. > > > On Apr 19, 2011, at 7:19 AM, hi wrote: > >> On WINDOWS platform, I am observing following error when executing >> "mpirun blacs_hello_example.exe" (example program to test BLACS taken >> from http://www.netlib.org/blacs/BLACS/Examples.html#HELLO)... >> >> C:\blacs_examples> mpirun blacs_hello_example.exe >> calling blacs_pinfo()... >> forrtl: severe (157): Program Exception - access violation >> Image PC Routine Line Source >> libmpid.dll 6A8E2DC5 Unknown Unknown Unknown >> libmpid.dll 6A8E2C31 Unknown Unknown Unknown >> blacs_ex01.exe 00402357 Unknown Unknown Unknown >> libifcorert.dll 1002A1C1 Unknown Unknown Unknown >> [myhost1:15340] [[30379,0],0]-[[30379,1],0] mca_oob_tcp_msg_recv: >> readv failed:Unknown error (10054) >> -- >> mpirun.exe has exited due to process rank 0 with PID 528 on node >> vibgyor exiting improperly. There are two reasons this could occur: >> >> 1. this process did not call "init" before exiting, but others in the >> job did. This can cause a job to hang indefinitely while it waits for >> all processes to call "init". By rule, if one process calls "init", >> then ALL processes must call "init" prior to termination. >> >> 2. this process called "init", but exited without calling "finalize". >> By rule, all processes that call "init" MUST call "finalize" prior to >> exiting or it will be considered an "abnormal termination" >> >> This may have caused other processes in the application to be >> terminated by signals sent by mpirun.exe (as reported here). >> -- >> >> Environment: >> OS: Windows 7 64-bit >> Compilers: Visual Studio 2008 32bit and Intel ifort 32bit >> OpenMPI: OpenMPI-1.5.3 pre-built libraries and also with >> OpenMPI-1.5.2. locally built libraries >> BLACS: pre-built libraries taken from >> http://icl.cs.utk.edu/lapack-for-windows/scalapack/index.html#librairies >> >> Any idea on how to resolve this??? >> >> Thank you in advance. >> -Hiral >> ___ >> 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 >
[OMPI users] mca_oob_tcp_msg_recv: readv failed:Unknown error (10054)
On WINDOWS platform, I am observing following error when executing "mpirun blacs_hello_example.exe" (example program to test BLACS taken from http://www.netlib.org/blacs/BLACS/Examples.html#HELLO)... C:\blacs_examples> mpirun blacs_hello_example.exe calling blacs_pinfo()... forrtl: severe (157): Program Exception - access violation Image PCRoutineLineSource libmpid.dll6A8E2DC5 Unknown Unknown Unknown libmpid.dll6A8E2C31 Unknown Unknown Unknown blacs_ex01.exe 00402357 Unknown Unknown Unknown libifcorert.dll1002A1C1 Unknown Unknown Unknown [myhost1:15340] [[30379,0],0]-[[30379,1],0] mca_oob_tcp_msg_recv: readv failed:Unknown error (10054) -- mpirun.exe has exited due to process rank 0 with PID 528 on node vibgyor exiting improperly. There are two reasons this could occur: 1. this process did not call "init" before exiting, but others in the job did. This can cause a job to hang indefinitely while it waits for all processes to call "init". By rule, if one process calls "init", then ALL processes must call "init" prior to termination. 2. this process called "init", but exited without calling "finalize". By rule, all processes that call "init" MUST call "finalize" prior to exiting or it will be considered an "abnormal termination" This may have caused other processes in the application to be terminated by signals sent by mpirun.exe (as reported here). -- Environment: OS: Windows 7 64-bit Compilers: Visual Studio 2008 32bit and Intel ifort 32bit OpenMPI: OpenMPI-1.5.3 pre-built libraries and also with OpenMPI-1.5.2. locally built libraries BLACS: pre-built libraries taken from http://icl.cs.utk.edu/lapack-for-windows/scalapack/index.html#librairies Any idea on how to resolve this??? Thank you in advance. -Hiral
Re: [OMPI users] "Value out of bounds in file" error
Hi Rainer, When executing "mpirun blacs_hello_example.exe" (reference: http://www.netlib.org/blacs/BLACS/Examples.html#HELLO), I am now getting folloing error... <<<<<< C:\blacs_examples>mpirun blacs_hello_example.exe forrtl: severe (157): Program Exception - access violation Image PCRoutineLineSource libmpid.dll63472DC5 Unknown Unknown Unknown libmpid.dll63472C31 Unknown Unknown Unknown blacs_ex01.exe 0040418A Unknown Unknown Unknown blacs_ex01.exe 00401034 Unknown Unknown Unknown blacs_ex01.exe 00401F53 Unknown Unknown Unknown blacs_ex01.exe 0040182A Unknown Unknown Unknown kernel32.dll 75E23677 Unknown Unknown Unknown ntdll.dll 77049F02 Unknown Unknown Unknown ntdll.dll 77049ED5 Unknown Unknown Unknown [vibgyor:08548] [[27683,0],0]-[[27683,1],0] mca_oob_tcp_msg_recv: readv failed: Unknown error (10054) -- mpirun has exited due to process rank 0 with PID 480 on node vibgyor exiting improperly. There are two reasons this could occur: 1. this process did not call "init" before exiting, but others in the job did. This can cause a job to hang indefinitely while it waits for all processes to call "init". By rule, if one process calls "init", then ALL processes must call "init" prior to termination. 2. this process called "init", but exited without calling "finalize". By rule, all processes that call "init" MUST call "finalize" prior to exiting or it will be considered an "abnormal termination" This may have caused other processes in the application to be terminated by signals sent by mpirun (as reported here). ------ >>>>>> Any idea on this??? Thank you. -Hiral On Wed, Apr 13, 2011 at 11:45 AM, hi <hiralsmaill...@gmail.com> wrote: > Hi Rainer, > > Thanks for acknowledgment. > > > You may want to port/compile BLACS from netlib yourselve, see here: > > http://icl.cs.utk.edu/lapack-for-windows/VisualStudio_install.html > > With that I am seeing compilation errors as reported in... > http://icl.cs.utk.edu/lapack-forum/viewtopic.php?f=12=2354 > > Please comment on this, if you any idea. > > Thank you. > -Hiral > On Wed, Apr 13, 2011 at 1:37 AM, Rainer Keller <kel...@hlrs.de> wrote: > >> Hiral, >> >> On Monday 11 April 2011 15:04:19 hi wrote: >> > Is it the case that I am combining mkl_intelmpi with locally built >> openmpi >> > and hence this problem??? >> Yes, as You mention yourselve here ,-] >> >> > ... >> > Files (x86)\Intel\Compiler\11.1\065\mkl/ia32/lib" mkl_blacs_intelmpi.lib >> > mkl_core.lib mkl_core_dll.lib /LIBPATH:"C:/Program Files >> >> MKL includes the BLACS interface -- however, MKL is built against >> Intel-MPI: >> under Linux-based MKL, there exist the static libraries >> libmkl_blacs_intelmpi_*lp64.a, libmkl_blacs_sgimpt_*lp64.a and >> libmkl_blacs_openmpi_*lp64.a. >> >> The corresponding libraries do not exist under your windows installation. >> >> You may want to port/compile BLACS from netlib yourselve, see here: >> http://icl.cs.utk.edu/lapack-for-windows/VisualStudio_install.html >> >> Hope this helps? >> >> Best regards, >> Rainer >> -- >> >> Dr.-Ing. Rainer Keller http://www.hlrs.de/people/keller >> HLRS Tel: ++49 (0)711-685 6 5858 >> Nobelstrasse 19 Fax: ++49 (0)711-685 6 5832 >> 70550 Stuttgartemail: kel...@hlrs.de >> Germany AIM/Skype:rusraink >> > >
Re: [OMPI users] "Value out of bounds in file" error
Hi Rainer, Thanks for acknowledgment. > You may want to port/compile BLACS from netlib yourselve, see here: > http://icl.cs.utk.edu/lapack-for-windows/VisualStudio_install.html With that I am seeing compilation errors as reported in... http://icl.cs.utk.edu/lapack-forum/viewtopic.php?f=12=2354 Please comment on this, if you any idea. Thank you. -Hiral On Wed, Apr 13, 2011 at 1:37 AM, Rainer Keller <kel...@hlrs.de> wrote: > Hiral, > > On Monday 11 April 2011 15:04:19 hi wrote: > > Is it the case that I am combining mkl_intelmpi with locally built > openmpi > > and hence this problem??? > Yes, as You mention yourselve here ,-] > > > ... > > Files (x86)\Intel\Compiler\11.1\065\mkl/ia32/lib" mkl_blacs_intelmpi.lib > > mkl_core.lib mkl_core_dll.lib /LIBPATH:"C:/Program Files > > MKL includes the BLACS interface -- however, MKL is built against > Intel-MPI: > under Linux-based MKL, there exist the static libraries > libmkl_blacs_intelmpi_*lp64.a, libmkl_blacs_sgimpt_*lp64.a and > libmkl_blacs_openmpi_*lp64.a. > > The corresponding libraries do not exist under your windows installation. > > You may want to port/compile BLACS from netlib yourselve, see here: > http://icl.cs.utk.edu/lapack-for-windows/VisualStudio_install.html > > Hope this helps? > > Best regards, > Rainer > -- > > Dr.-Ing. Rainer Keller http://www.hlrs.de/people/keller > HLRS Tel: ++49 (0)711-685 6 5858 > Nobelstrasse 19 Fax: ++49 (0)711-685 6 5832 > 70550 Stuttgartemail: kel...@hlrs.de > Germany AIM/Skype:rusraink >
Re: [OMPI users] "Value out of bounds in file" error
Hi Jeff, I tried "hello_f77", "hello_c", "hello_cxx" examples and all are halting at call to "MPI_INIT()" with below message on console... """ [mymachine:10108] [[27195,0],0] ORTE_ERROR_LOG: Value out of bounds in file ..\..\orte\mca\oob\tcp\oob_tcp.c at line 1193 """ Do you have any idea??? Thank you. -Hiral On Tue, Apr 12, 2011 at 3:36 PM, Jeff Squyres <jsquy...@cisco.com> wrote: > Can you provide more information? > > Where / when exactly does this error occur? E.g., does it happen during > MPI_INIT, or is it later in the application? > > Are you able to run any MPI codes at all, such as the example "hello world" > or "ring" programs? Are you able to run non-MPI applications at all, such > as "hostname" (or whatever the equivalent is in Windows)? > > Please send all the information listed here: > >http://www.open-mpi.org/community/help/ > > > On Apr 11, 2011, at 9:04 AM, hi wrote: > > > Hi, > > > > For the attached test program (reference: > http://www.netlib.org/blacs/BLACS/Examples.html#HELLO), I am observing > following message and binary halts... > > > > [:03864] [[16991,0],0] ORTE_ERROR_LOG: Value out of bounds > in file ..\..\orte\mca\oob\tcp\oob_tcp.c at line 1193 > > > > > > *Command used to compile is as follow: > > 1) ifort blacs_ex01.f -c -I"C:\Program Files > (x86)\Intel\Compiler\11.1\065\mkl/include" > > > > 2) link /SUBSYSTEM:CONSOLE -NODEFAULTLIB /INCREMENTAL:NO /MAP > /MAPINFO:EXPORTS /DEBUG -opt:ref,icf /out:blacs_ex01.exe blacs_ex01.obj > /LIBPATH:"C:/Program Files (x86)/Intel/Compiler/11.1/065\\Lib\ia32" > libirc.lib libifcorert.lib /LIBPATH:"C:\Program Files > (x86)\Intel\Compiler\11.1\065\lib\ia32" ifqwin.lib /LIBPATH:"C:\Program > Files (x86)\Intel\Compiler\11.1\065\mkl/ia32/lib" mkl_blacs_intelmpi.lib > mkl_core.lib mkl_core_dll.lib /LIBPATH:"C:/Program Files > (x86)/Intel/Compiler/11.1/065/mkl\\ia32\\lib" mkl_lapack95.lib > mkl_core_dll.lib mkl_intel_c_dll.lib mkl_intel_thread_dll.lib > /LIBPATH:"C:/Program Files (x86)/Intel/Compiler/11.1/065/mkl/ia32/lib/" > mkl_scalapack_core.lib mkl_blacs_dll.lib > /LIBPATH:"C:\openmpi-1.5.2\installed_vs2008\lib" libmpi_f77d.lib libmpid.lib > libopen-pald.lib libopen-rted.lib /LIBPATH:"C:\Program Files\Microsoft > SDKs\Windows\v6.1\\\Lib" /LIBPATH:"C:/Program Files (x86)/Microsoft Visual > Studio 9.0/VC\\Lib" msvcrt.lib msvcprt.lib kernel32.lib > > > > * Environment: > > OS: Windows 7 (64-bit) > > Compiler: cl.exe (32-bit) and ifort (32-bit) > > MPI: openmpi-1.5.2 (local build) > > > > Is it the case that I am combining mkl_intelmpi with locally built > openmpi and hence this problem??? > > > > Thank you in advance. > > -Hiral > > ___ > > users mailing list > > us...@open-mpi.org > > http://www.open-mpi.org/mailman/listinfo.cgi/users > > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > > ___ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users >
Re: [OMPI users] "Value out of bounds in file" error
Hi, Any idea on this ??? Thank you. -Hiral On Mon, Apr 11, 2011 at 6:34 PM, hi <hiralsmaill...@gmail.com> wrote: > Hi, > > For the attached test program (reference: > http://www.netlib.org/blacs/BLACS/Examples.html#HELLO), I am observing > following message and binary halts... > > [:03864] [[16991,0],0] ORTE_ERROR_LOG: Value out of bounds in > file ..\..\orte\mca\oob\tcp\oob_tcp.c at line 1193 > > > *Command used to compile is as follow: > 1) ifort blacs_ex01.f -c -I"C:\Program Files > (x86)\Intel\Compiler\11.1\065\mkl/include" > > 2) link /SUBSYSTEM:CONSOLE -NODEFAULTLIB /INCREMENTAL:NO /MAP > /MAPINFO:EXPORTS /DEBUG -opt:ref,icf /out:blacs_ex01.exe blacs_ex01.obj > /LIBPATH:"C:/Program Files (x86)/Intel/Compiler/11.1/065\\Lib\ia32" > libirc.lib libifcorert.lib /LIBPATH:"C:\Program Files > (x86)\Intel\Compiler\11.1\065\lib\ia32" ifqwin.lib /LIBPATH:"C:\Program > Files (x86)\Intel\Compiler\11.1\065\mkl/ia32/lib" mkl_blacs_intelmpi.lib > mkl_core.lib mkl_core_dll.lib /LIBPATH:"C:/Program Files > (x86)/Intel/Compiler/11.1/065/mkl\\ia32\\lib" mkl_lapack95.lib > mkl_core_dll.lib mkl_intel_c_dll.lib mkl_intel_thread_dll.lib > /LIBPATH:"C:/Program Files (x86)/Intel/Compiler/11.1/065/mkl/ia32/lib/" > mkl_scalapack_core.lib mkl_blacs_dll.lib > /LIBPATH:"C:\openmpi-1.5.2\installed_vs2008\lib" libmpi_f77d.lib libmpid.lib > libopen-pald.lib libopen-rted.lib /LIBPATH:"C:\Program Files\Microsoft > SDKs\Windows\v6.1\\\Lib" /LIBPATH:"C:/Program Files (x86)/Microsoft Visual > Studio 9.0/VC\\Lib" msvcrt.lib msvcprt.lib kernel32.lib > > * Environment: > OS: Windows 7 (64-bit) > Compiler: cl.exe (32-bit) and ifort (32-bit) > MPI: openmpi-1.5.2 (local build) > > Is it the case that I am combining mkl_intelmpi with locally built openmpi > and hence this problem??? > > Thank you in advance. > -Hiral >
[OMPI users] "Value out of bounds in file" error
Hi, For the attached test program (reference: http://www.netlib.org/blacs/BLACS/Examples.html#HELLO), I am observing following message and binary halts... [:03864] [[16991,0],0] ORTE_ERROR_LOG: Value out of bounds in file ..\..\orte\mca\oob\tcp\oob_tcp.c at line 1193 *Command used to compile is as follow: 1) ifort blacs_ex01.f -c -I"C:\Program Files (x86)\Intel\Compiler\11.1\065\mkl/include" 2) link /SUBSYSTEM:CONSOLE -NODEFAULTLIB /INCREMENTAL:NO /MAP /MAPINFO:EXPORTS /DEBUG -opt:ref,icf /out:blacs_ex01.exe blacs_ex01.obj /LIBPATH:"C:/Program Files (x86)/Intel/Compiler/11.1/065\\Lib\ia32" libirc.lib libifcorert.lib /LIBPATH:"C:\Program Files (x86)\Intel\Compiler\11.1\065\lib\ia32" ifqwin.lib /LIBPATH:"C:\Program Files (x86)\Intel\Compiler\11.1\065\mkl/ia32/lib" mkl_blacs_intelmpi.lib mkl_core.lib mkl_core_dll.lib /LIBPATH:"C:/Program Files (x86)/Intel/Compiler/11.1/065/mkl\\ia32\\lib" mkl_lapack95.lib mkl_core_dll.lib mkl_intel_c_dll.lib mkl_intel_thread_dll.lib /LIBPATH:"C:/Program Files (x86)/Intel/Compiler/11.1/065/mkl/ia32/lib/" mkl_scalapack_core.lib mkl_blacs_dll.lib /LIBPATH:"C:\openmpi-1.5.2\installed_vs2008\lib" libmpi_f77d.lib libmpid.lib libopen-pald.lib libopen-rted.lib /LIBPATH:"C:\Program Files\Microsoft SDKs\Windows\v6.1\\\Lib" /LIBPATH:"C:/Program Files (x86)/Microsoft Visual Studio 9.0/VC\\Lib" msvcrt.lib msvcprt.lib kernel32.lib * Environment: OS: Windows 7 (64-bit) Compiler: cl.exe (32-bit) and ifort (32-bit) MPI: openmpi-1.5.2 (local build) Is it the case that I am combining mkl_intelmpi with locally built openmpi and hence this problem??? Thank you in advance. -Hiral blacs_ex01.f Description: Binary data
Re: [OMPI users] Building OpenMPI on Windows 7
Hi Shiqing, While building my application (on Windows 7, Vistual Studio 2008 32-bit application) with openmpi-1.5.2, getting following error... util.o : error LNK2001: unresolved external symbol _ompi_mpi_byte util.o : error LNK2001: unresolved external symbol _ompi_mpi_op_max util.o : error LNK2001: unresolved external symbol _ompi_mpi_int util.o : error LNK2001: unresolved external symbol _ompi_mpi_char util.o : error LNK2001: unresolved external symbol _ompi_mpi_comm_world util.o : error LNK2001: unresolved external symbol _ompi_mpi_op_sum Linking options... /LIBPATH:""c:\openmpi-1.5.2\installed"/lib/" libmpi_cxxd.lib libmpid.lib libmpi_f77d.lib libopen-pald.lib libopen-rted.lib I seems that 'dllexport' is missing for above symbols. Thank you. -Hiral On Fri, Mar 18, 2011 at 1:53 AM, Shiqing Fan <f...@hlrs.de> wrote: > Hi Hiral, > > > > > There is no f90 bindings at moment for Windows. > Any idea when this available? > > At moment, no. But only if there is strong requirements. > > > > Regards, > Shiqing > > > Thank you. > -Hiral > > On Thu, Mar 17, 2011 at 5:21 PM, Shiqing Fan <f...@hlrs.de> wrote: > >> >> I tried building openmpi-1.5.2 on Windows 7 (as described below >> environment) with OMPI_WANT_F77_BINDINGS_ON and >> OMPI_WANT_F90_BINDINGS_ON using "ifort". >> >> I observed that it has generated mpif77.exe but didn't generated >> mpif90.exe, any idea??? >> >> >> There is no f90 bindings at moment for Windows. >> >> >> BTW: while using above generated mpif77.exe to compile hello_f77.f got >> following errors... >> >> c:\openmpi-1.5.2\examples> mpif77 hello_f77.f >> Intel(R) Visual Fortran Compiler Professional for applications running on >> IA-32, >> Version 11.1Build 20100414 Package ID: w_cprof_p_11.1.065 >> Copyright (C) 1985-2010 Intel Corporation. All rights reserved. >> C:/openmpi-1.5.2/installed/include\mpif-config.h(91): error #5082: Syntax >> error, >> found ')' when expecting one of: ( >> > _KIND_PARAM> ... >> parameter (MPI_STATUS_SIZE=) >> -^ >> compilation aborted for hello_f77.f (code 1) >> >> It seems MPI_STATUS_SIZE is not set. Could you please send me your >> CMakeCache.txt to me off the mailing list, so that I can check what is going >> wrong? A quick solution would be just set it to 0. >> >> >> Regards, >> Shiqing >> >> Thank you. >> -Hiral >> >> >> On Wed, Mar 16, 2011 at 8:11 PM, Damien <dam...@khubla.com> wrote: >> >> >>> Hiral, >>> >>> To add to Shiqing's comments, 1.5 has been running great for me on >>> Windows for over 6 months since it was in beta. You should give it a try. >>> >>> Damien >>> >>> On 16/03/2011 8:34 AM, Shiqing Fan wrote: >>> >>> Hi Hiral, >>> >>> >>> >>> > it's only experimental in 1.4 series. And there is only F77 bingdings >>> on Windows, no F90 bindings. >>> Can you please provide steps to build 1.4.3 with experimental f77 >>> bindings on Windows? >>> >>> Well, I highly recommend to use 1.5 series, but I can also take a look >>> and probably provide you a patch for 1.4 . >>> >>> >>> >>> BTW: Do you have any idea on: when next stable release with full fortran >>> support on Windows would be available? >>> >>> There is no plan yet. >>> >>> >>> Regards, >>> Shiqing >>> >>> >>> >>> >>> Thank you. >>> -Hiral >>> >>> On Wed, Mar 16, 2011 at 6:59 PM, Shiqing Fan <f...@hlrs.de> wrote: >>> >>> >>>> Hi Hiral, >>>> >>>> 1.3.4 is quite old, please use the latest version. As Damien noted, the >>>> full fortran support is in 1.5 series, it's only experimental in 1.4 >>>> series. >>>> And there is only F77 bingdings on Windows, no F90 bindings. Another choice >>>> is to use the released binary installers to avoid compiling everything by >>>> yourself. >>>> >>>> >>>> Best Regards, >>>> Shiqing >>>> >>>> On 3/16/2011 11:47 AM, hi wrote: >>>> >>>> Greetings!!! >>>> >>>> >>>> >>>> I am trying to build openmpi-1.3.4 and openmpi-1.4.3 on Windows 7 >>>> (64-bit OS), but getting some difficuty... >>>> >>>
[OMPI users] Comparison among OpenMPI, MPICH2 and MSPICH on Windows
Hi, Does anybody have idea about... Where I can get comparison of OpenMPI, MPICH2 and MSPICH? What they support and Which one is performance wise better on Windows platform ? Thank you in advance. -Hiral
Re: [OMPI users] Building OpenMPI on Windows 7
Hi Shiqing, Yes, it was parameter (MPI_STATUS_SIZE=) in mpif-config.h file. BTW: see the attached CMakeCache.txt. > There is no f90 bindings at moment for Windows. Any idea when this available? Thank you. -Hiral On Thu, Mar 17, 2011 at 5:21 PM, Shiqing Fan <f...@hlrs.de> wrote: > > I tried building openmpi-1.5.2 on Windows 7 (as described below > environment) with OMPI_WANT_F77_BINDINGS_ON and > OMPI_WANT_F90_BINDINGS_ON using "ifort". > > I observed that it has generated mpif77.exe but didn't generated > mpif90.exe, any idea??? > > > There is no f90 bindings at moment for Windows. > > > BTW: while using above generated mpif77.exe to compile hello_f77.f got > following errors... > > c:\openmpi-1.5.2\examples> mpif77 hello_f77.f > Intel(R) Visual Fortran Compiler Professional for applications running on > IA-32, > Version 11.1Build 20100414 Package ID: w_cprof_p_11.1.065 > Copyright (C) 1985-2010 Intel Corporation. All rights reserved. > C:/openmpi-1.5.2/installed/include\mpif-config.h(91): error #5082: Syntax > error, > found ')' when expecting one of: ( > _KIND_PARAM> ... > parameter (MPI_STATUS_SIZE=) > -^ > compilation aborted for hello_f77.f (code 1) > > It seems MPI_STATUS_SIZE is not set. Could you please send me your > CMakeCache.txt to me off the mailing list, so that I can check what is going > wrong? A quick solution would be just set it to 0. > > > Regards, > Shiqing > > Thank you. > -Hiral > > > On Wed, Mar 16, 2011 at 8:11 PM, Damien <dam...@khubla.com> wrote: > > >> Hiral, >> >> To add to Shiqing's comments, 1.5 has been running great for me on Windows >> for over 6 months since it was in beta. You should give it a try. >> >> Damien >> >> On 16/03/2011 8:34 AM, Shiqing Fan wrote: >> >> Hi Hiral, >> >> >> >> > it's only experimental in 1.4 series. And there is only F77 bingdings on >> Windows, no F90 bindings. >> Can you please provide steps to build 1.4.3 with experimental f77 bindings >> on Windows? >> >> Well, I highly recommend to use 1.5 series, but I can also take a look and >> probably provide you a patch for 1.4 . >> >> >> >> BTW: Do you have any idea on: when next stable release with full fortran >> support on Windows would be available? >> >> There is no plan yet. >> >> >> Regards, >> Shiqing >> >> >> >> >> Thank you. >> -Hiral >> >> On Wed, Mar 16, 2011 at 6:59 PM, Shiqing Fan <f...@hlrs.de> wrote: >> >> >>> Hi Hiral, >>> >>> 1.3.4 is quite old, please use the latest version. As Damien noted, the >>> full fortran support is in 1.5 series, it's only experimental in 1.4 series. >>> And there is only F77 bingdings on Windows, no F90 bindings. Another choice >>> is to use the released binary installers to avoid compiling everything by >>> yourself. >>> >>> >>> Best Regards, >>> Shiqing >>> >>> On 3/16/2011 11:47 AM, hi wrote: >>> >>> Greetings!!! >>> >>> >>> >>> I am trying to build openmpi-1.3.4 and openmpi-1.4.3 on Windows 7 (64-bit >>> OS), but getting some difficuty... >>> >>> >>> >>> My build environment: >>> >>> OS : Windows 7 (64-bit) >>> >>> C/C++ compiler : Visual Studio 2008 and Visual Studio 2010 >>> >>> Fortran compiler: Intel "ifort" >>> >>> >>> >>> Approach: followed the "First Approach" described in README.WINDOWS file. >>> >>> >>> >>> *1) Using openmpi-1.3.4:*** >>> >>> Observed build time error in version.cc(136). This error is related >>> to getting SVN version information as described in >>> http://www.open-mpi.org/community/lists/users/2010/01/11860.php. As we >>> are using this openmpi-1.3.4 stable version on Linux platform, is there any >>> fix to this compile time error? >>> >>> >>> >>> *2) Using openmpi-1.4.3:*** >>> >>> Builds properly without F77/F90 support (i.e. i.e. Skipping MPI F77 >>> interface). >>> >>> Now to get the "mpif*.exe" for fortran programs, I provided proper >>> "ifort" path and enabled "OMPI_WANT_F77_BINDINGS=ON" and/or >>> OMPI_WANT_F90_BINDINGS=ON flag; but getting following errors... >>> >>
Re: [OMPI users] Building OpenMPI on Windows 7
Hi, I tried building openmpi-1.5.2 on Windows 7 (as described below environment) with OMPI_WANT_F77_BINDINGS_ON and OMPI_WANT_F90_BINDINGS_ON using "ifort". I observed that it has generated mpif77.exe but didn't generated mpif90.exe, any idea??? BTW: while using above generated mpif77.exe to compile hello_f77.f got following errors... c:\openmpi-1.5.2\examples> mpif77 hello_f77.f Intel(R) Visual Fortran Compiler Professional for applications running on IA-32, Version 11.1Build 20100414 Package ID: w_cprof_p_11.1.065 Copyright (C) 1985-2010 Intel Corporation. All rights reserved. C:/openmpi-1.5.2/installed/include\mpif-config.h(91): error #5082: Syntax error, found ')' when expecting one of: ( ... parameter (MPI_STATUS_SIZE=) -^ compilation aborted for hello_f77.f (code 1) Thank you. -Hiral On Wed, Mar 16, 2011 at 8:11 PM, Damien <dam...@khubla.com> wrote: > Hiral, > > To add to Shiqing's comments, 1.5 has been running great for me on Windows > for over 6 months since it was in beta. You should give it a try. > > Damien > > On 16/03/2011 8:34 AM, Shiqing Fan wrote: > > Hi Hiral, > > > > > it's only experimental in 1.4 series. And there is only F77 bingdings on > Windows, no F90 bindings. > Can you please provide steps to build 1.4.3 with experimental f77 bindings > on Windows? > > Well, I highly recommend to use 1.5 series, but I can also take a look and > probably provide you a patch for 1.4 . > > > > BTW: Do you have any idea on: when next stable release with full fortran > support on Windows would be available? > > There is no plan yet. > > > Regards, > Shiqing > > > > > Thank you. > -Hiral > > On Wed, Mar 16, 2011 at 6:59 PM, Shiqing Fan <f...@hlrs.de> wrote: > > >> Hi Hiral, >> >> 1.3.4 is quite old, please use the latest version. As Damien noted, the >> full fortran support is in 1.5 series, it's only experimental in 1.4 series. >> And there is only F77 bingdings on Windows, no F90 bindings. Another choice >> is to use the released binary installers to avoid compiling everything by >> yourself. >> >> >> Best Regards, >> Shiqing >> >> On 3/16/2011 11:47 AM, hi wrote: >> >> Greetings!!! >> >> >> >> I am trying to build openmpi-1.3.4 and openmpi-1.4.3 on Windows 7 (64-bit >> OS), but getting some difficuty... >> >> >> >> My build environment: >> >> OS : Windows 7 (64-bit) >> >> C/C++ compiler : Visual Studio 2008 and Visual Studio 2010 >> >> Fortran compiler: Intel "ifort" >> >> >> >> Approach: followed the "First Approach" described in README.WINDOWS file. >> >> >> >> *1) Using openmpi-1.3.4:*** >> >> Observed build time error in version.cc(136). This error is related to >> getting SVN version information as described in >> http://www.open-mpi.org/community/lists/users/2010/01/11860.php. As we >> are using this openmpi-1.3.4 stable version on Linux platform, is there any >> fix to this compile time error? >> >> >> >> *2) Using openmpi-1.4.3:*** >> >> Builds properly without F77/F90 support (i.e. i.e. Skipping MPI F77 >> interface). >> >> Now to get the "mpif*.exe" for fortran programs, I provided proper >> "ifort" path and enabled "OMPI_WANT_F77_BINDINGS=ON" and/or >> OMPI_WANT_F90_BINDINGS=ON flag; but getting following errors... >> >> * 2.a) "ifort" with OMPI_WANT_F77_BINDINGS=ON gave following errors... >> * >> >> Check ifort external symbol convention... >> >> Check ifort external symbol convention...single underscore >> >> Check if Fortran 77 compiler supports LOGICAL... >> >> Check if Fortran 77 compiler supports LOGICAL...done >> >> Check size of Fortran 77 LOGICAL... >> >> CMake Error at contrib/platform/win32/CMakeModules/f77_get_sizeof.cmake:76 >> (MESSAGE): >> >> Could not determine size of LOGICAL. >> >> Call Stack (most recent call first): >> >> contrib/platform/win32/CMakeModules/f77_check.cmake:82 >> (OMPI_F77_GET_SIZEOF) >> >> contrib/platform/win32/CMakeModules/ompi_configure.cmake:1123 >> (OMPI_F77_CHECK) >> >> CMakeLists.txt:87 (INCLUDE) >> >> Configuring incomplete, errors occurred! >> >> >> >> * 2.b) "ifort" with OMPI_WANT_F90_BINDINGS=ON gave following errors... >> * >> >> Skipping MPI F77 interface >> >> CMake
Re: [OMPI users] Building OpenMPI on Windows 7
Hi Shiquing / Damien, Thanks for the quick reply. > it's only experimental in 1.4 series. And there is only F77 bingdings on Windows, no F90 bindings. Can you please provide steps to build 1.4.3 with experimental f77 bindings on Windows? BTW: Do you have any idea on: when next stable release with full fortran support on Windows would be available? Thank you. -Hiral On Wed, Mar 16, 2011 at 6:59 PM, Shiqing Fan <f...@hlrs.de> wrote: > Hi Hiral, > > 1.3.4 is quite old, please use the latest version. As Damien noted, the > full fortran support is in 1.5 series, it's only experimental in 1.4 series. > And there is only F77 bingdings on Windows, no F90 bindings. Another choice > is to use the released binary installers to avoid compiling everything by > yourself. > > > Best Regards, > Shiqing > > > On 3/16/2011 11:47 AM, hi wrote: > > Greetings!!! > > > > I am trying to build openmpi-1.3.4 and openmpi-1.4.3 on Windows 7 (64-bit > OS), but getting some difficuty... > > > > My build environment: > > OS : Windows 7 (64-bit) > > C/C++ compiler : Visual Studio 2008 and Visual Studio 2010 > > Fortran compiler: Intel "ifort" > > > > Approach: followed the "First Approach" described in README.WINDOWS file. > > > > *1) Using openmpi-1.3.4:*** > > Observed build time error in version.cc(136). This error is related to > getting SVN version information as described in > http://www.open-mpi.org/community/lists/users/2010/01/11860.php. As we are > using this openmpi-1.3.4 stable version on Linux platform, is there any fix > to this compile time error? > > > > *2) Using openmpi-1.4.3:*** > > Builds properly without F77/F90 support (i.e. i.e. Skipping MPI F77 > interface). > > Now to get the "mpif*.exe" for fortran programs, I provided proper > "ifort" path and enabled "OMPI_WANT_F77_BINDINGS=ON" and/or > OMPI_WANT_F90_BINDINGS=ON flag; but getting following errors... > > * 2.a) "ifort" with OMPI_WANT_F77_BINDINGS=ON gave following errors... * > > Check ifort external symbol convention... > > Check ifort external symbol convention...single underscore > > Check if Fortran 77 compiler supports LOGICAL... > > Check if Fortran 77 compiler supports LOGICAL...done > > Check size of Fortran 77 LOGICAL... > > CMake Error at contrib/platform/win32/CMakeModules/f77_get_sizeof.cmake:76 > (MESSAGE): > > Could not determine size of LOGICAL. > > Call Stack (most recent call first): > > contrib/platform/win32/CMakeModules/f77_check.cmake:82 > (OMPI_F77_GET_SIZEOF) > > contrib/platform/win32/CMakeModules/ompi_configure.cmake:1123 > (OMPI_F77_CHECK) > > CMakeLists.txt:87 (INCLUDE) > > Configuring incomplete, errors occurred! > > > > * 2.b) "ifort" with OMPI_WANT_F90_BINDINGS=ON gave following errors... * > > Skipping MPI F77 interface > > CMake Error: File > C:/openmpi-1.4.3/contrib/platform/win32/ConfigFiles/mpif90-wrapper-data.txt.cmake > does not exist. > > CMake Error at ompi/tools/CMakeLists.txt:93 (CONFIGURE_FILE): > > configure_file Problem configuring file > > CMake Error: File > C:/openmpi-1.4.3/contrib/platform/win32/ConfigFiles/mpif90-wrapper-data.txt.cmake > does not exist. > > CMake Error at ompi/tools/CMakeLists.txt:97 (CONFIGURE_FILE): > > configure_file Problem configuring file > > looking for ccp... > > looking for ccp...not found. > > looking for ccp... > > looking for ccp...not found. > > Configuring incomplete, errors occurred! > > > > * 2.c) "ifort" with OMPI_WANT_F77_BINDINGS=ON and > OMPI_WANT_F90_BINDINGS=ON gave following errors... * > > Check ifort external symbol convention... > > Check ifort external symbol convention...single underscore > > Check if Fortran 77 compiler supports LOGICAL... > > Check if Fortran 77 compiler supports LOGICAL...done > > Check size of Fortran 77 LOGICAL... > > CMake Error at contrib/platform/win32/CMakeModules/f77_get_sizeof.cmake:76 > (MESSAGE): > > Could not determine size of LOGICAL. > > Call Stack (most recent call first): > > contrib/platform/win32/CMakeModules/f77_check.cmake:82 > (OMPI_F77_GET_SIZEOF) > > contrib/platform/win32/CMakeModules/ompi_configure.cmake:1123 > (OMPI_F77_CHECK) > > CMakeLists.txt:87 (INCLUDE) > > Configuring incomplete, errors occurred! > > > > Any idea on resolving above errors to get mpif*.exe generated on Windows > platform using "ifort"? > > Please let me know if more information is required. > Thank you in advance. > > -Hiral > > > ___ > users mailing > listusers@open-mpi.orghttp://www.open-mpi.org/mailman/listinfo.cgi/users > > > > -- > --- > Shiqing Fan > High Performance Computing Center Stuttgart (HLRS) > Tel: ++49(0)711-685-87234 Nobelstrasse 19 > Fax: ++49(0)711-685-65832 70569 > Stuttgarthttp://www.hlrs.de/organization/people/shiqing-fan/ > email: f...@hlrs.de > >
[OMPI users] Building OpenMPI on Windows 7
Greetings!!! I am trying to build openmpi-1.3.4 and openmpi-1.4.3 on Windows 7 (64-bit OS), but getting some difficuty... My build environment: OS : Windows 7 (64-bit) C/C++ compiler : Visual Studio 2008 and Visual Studio 2010 Fortran compiler: Intel "ifort" Approach: followed the "First Approach" described in README.WINDOWS file. *1) Using openmpi-1.3.4:*** Observed build time error in version.cc(136). This error is related to getting SVN version information as described in http://www.open-mpi.org/community/lists/users/2010/01/11860.php. As we are using this openmpi-1.3.4 stable version on Linux platform, is there any fix to this compile time error? *2) Using openmpi-1.4.3:*** Builds properly without F77/F90 support (i.e. i.e. Skipping MPI F77 interface). Now to get the "mpif*.exe" for fortran programs, I provided proper "ifort" path and enabled "OMPI_WANT_F77_BINDINGS=ON" and/or OMPI_WANT_F90_BINDINGS=ON flag; but getting following errors... * 2.a) "ifort" with OMPI_WANT_F77_BINDINGS=ON gave following errors... * Check ifort external symbol convention... Check ifort external symbol convention...single underscore Check if Fortran 77 compiler supports LOGICAL... Check if Fortran 77 compiler supports LOGICAL...done Check size of Fortran 77 LOGICAL... CMake Error at contrib/platform/win32/CMakeModules/f77_get_sizeof.cmake:76 (MESSAGE): Could not determine size of LOGICAL. Call Stack (most recent call first): contrib/platform/win32/CMakeModules/f77_check.cmake:82 (OMPI_F77_GET_SIZEOF) contrib/platform/win32/CMakeModules/ompi_configure.cmake:1123 (OMPI_F77_CHECK) CMakeLists.txt:87 (INCLUDE) Configuring incomplete, errors occurred! * 2.b) "ifort" with OMPI_WANT_F90_BINDINGS=ON gave following errors... * Skipping MPI F77 interface CMake Error: File C:/openmpi-1.4.3/contrib/platform/win32/ConfigFiles/mpif90-wrapper-data.txt.cmake does not exist. CMake Error at ompi/tools/CMakeLists.txt:93 (CONFIGURE_FILE): configure_file Problem configuring file CMake Error: File C:/openmpi-1.4.3/contrib/platform/win32/ConfigFiles/mpif90-wrapper-data.txt.cmake does not exist. CMake Error at ompi/tools/CMakeLists.txt:97 (CONFIGURE_FILE): configure_file Problem configuring file looking for ccp... looking for ccp...not found. looking for ccp... looking for ccp...not found. Configuring incomplete, errors occurred! * 2.c) "ifort" with OMPI_WANT_F77_BINDINGS=ON and OMPI_WANT_F90_BINDINGS=ON gave following errors... * Check ifort external symbol convention... Check ifort external symbol convention...single underscore Check if Fortran 77 compiler supports LOGICAL... Check if Fortran 77 compiler supports LOGICAL...done Check size of Fortran 77 LOGICAL... CMake Error at contrib/platform/win32/CMakeModules/f77_get_sizeof.cmake:76 (MESSAGE): Could not determine size of LOGICAL. Call Stack (most recent call first): contrib/platform/win32/CMakeModules/f77_check.cmake:82 (OMPI_F77_GET_SIZEOF) contrib/platform/win32/CMakeModules/ompi_configure.cmake:1123 (OMPI_F77_CHECK) CMakeLists.txt:87 (INCLUDE) Configuring incomplete, errors occurred! Any idea on resolving above errors to get mpif*.exe generated on Windows platform using "ifort"? Please let me know if more information is required. Thank you in advance. -Hiral
