Re: [OMPI users] error compiling openmpi-1.6.1 on Windows 7
We've added "lo" back into the list, but I'm curious as to why 127.0.0.1/8 doesn't work. If you run ipconfig, what does it say for the localhost entry? I.e., what's its IP address and netmask? On Sep 9, 2012, at 1:27 PM, Siegmar Gross wrote: > Hi Shiqing, > > I disabled IPv6 in my network adpaters and activated the entry > "127.0.0.1 localhost" in file c:\Windows\System32\drivers\etc\hosts > to overwrite the IPv6 address for localhost in the registry. > > > "ping localhost" displays the following output. > > Ping wird ausgeführt für hermes [127.0.0.1] mit 32 Bytes Daten: > Antwort von 127.0.0.1: Bytes=32 Zeit<1ms TTL=128 > ... > > > Nevertheless I get the warning from "mpiexec" before the output of > my program. > > c:\...>mpiexec init_finalize.exe > -- > WARNING: An invalid value was given for btl_tcp_if_exclude. This > value will be ignored. > > Local host: hermes > Value: 127.0.0.1/8 > Message:Did not find interface matching this subnet > -- > > Hello! > > > > I can avoid the warning with the following command line. > > c:\...>mpiexec -mca btl_tcp_if_exclude lo init_finalize.exe > > Hello! > > > > c:\...>ompi_info --param btl tcp | \cygwin\bin\grep if_exclude > Comma-delimited list of devices or CIDR notation of networks to use > for MPI communication (e.g., "eth0,eth1" or > "192.168.0.0/16,10.1.4.0/24"). Mutually exclusive with > btl_tcp_if_exclude. > MCA btl: parameter "btl_tcp_if_exclude" (current value: > <127.0.0.1/8,sppp>, data source: default value) > > Perhaps it is necessary to add "lo" once more to the list to make > Windows 7 happy. > > > Kind regards > > Siegmar > > >>> The warning message is because the loopback adapter is excluded by >>> default, but this adapter is actually not installed on Windows. >>> >>> One solution might be installing the loopback adapter on Windows. It >>> very easy, only a few minutes. >> >> I have installed the loopback adapter but it has the wrong IP address >> so that I still have the same warning message. >> >> >> Ethernet-Adapter LAN-Verbindung 3: >> >> Verbindungsspezifisches DNS-Suffix: >> Beschreibung. . . . . . . . . . . : Microsoft Loopbackadapter >> Physikalische Adresse . . . . . . : 02-00-4C-4F-4F-50 >> DHCP aktiviert. . . . . . . . . . : Ja >> Autokonfiguration aktiviert . . . : Ja >> Verbindungslokale IPv6-Adresse . : fe80::25d7:866d:f5c9:7295%31(Bevorzugt) >> IPv4-Adresse (Auto. Konfiguration): 169.254.114.149(Bevorzugt) >> Subnetzmaske . . . . . . . . . . : 255.255.0.0 >> Standardgateway . . . . . . . . . : >> DHCPv6-IAID . . . . . . . . . . . : 671219788 >> DHCPv6-Client-DUID. . . . . . . . : > 00-01-00-01-15-A4-69-BD-C0-F8-DA-35-64-02 >> DNS-Server . . . . . . . . . . . : fec0:0:0:::1%1 >> fec0:0:0:::2%1 >> fec0:0:0:::3%1 >> NetBIOS über TCP/IP . . . . . . . : Aktiviert >> >> >> I tried to change the address to 127.0.0.1 without luck. When I switch >> from "automatic" to "manual" in the properties menue and start the >> IP address with 127 a window pops up announcing that an IP address >> starting with 127 is reserved for the loopback adapter so that I couldn't >> change the address. How did you manage to get the loopback adapter address >> 127.0.0.1 or do you live with the message from Open MPI? Thank you very >> much for a short answer in advance. >> >> >> Kind regards >> >> Siegmar > > > ___ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
Re: [OMPI users] error compiling openmpi-1.6.1 on Windows 7
Hi Shiqing, I disabled IPv6 in my network adpaters and activated the entry "127.0.0.1 localhost" in file c:\Windows\System32\drivers\etc\hosts to overwrite the IPv6 address for localhost in the registry. "ping localhost" displays the following output. Ping wird ausgeführt für hermes [127.0.0.1] mit 32 Bytes Daten: Antwort von 127.0.0.1: Bytes=32 Zeit<1ms TTL=128 ... Nevertheless I get the warning from "mpiexec" before the output of my program. c:\...>mpiexec init_finalize.exe -- WARNING: An invalid value was given for btl_tcp_if_exclude. This value will be ignored. Local host: hermes Value: 127.0.0.1/8 Message:Did not find interface matching this subnet -- Hello! I can avoid the warning with the following command line. c:\...>mpiexec -mca btl_tcp_if_exclude lo init_finalize.exe Hello! c:\...>ompi_info --param btl tcp | \cygwin\bin\grep if_exclude Comma-delimited list of devices or CIDR notation of networks to use for MPI communication (e.g., "eth0,eth1" or "192.168.0.0/16,10.1.4.0/24"). Mutually exclusive with btl_tcp_if_exclude. MCA btl: parameter "btl_tcp_if_exclude" (current value: <127.0.0.1/8,sppp>, data source: default value) Perhaps it is necessary to add "lo" once more to the list to make Windows 7 happy. Kind regards Siegmar > > The warning message is because the loopback adapter is excluded by > > default, but this adapter is actually not installed on Windows. > > > > One solution might be installing the loopback adapter on Windows. It > > very easy, only a few minutes. > > I have installed the loopback adapter but it has the wrong IP address > so that I still have the same warning message. > > > Ethernet-Adapter LAN-Verbindung 3: > >Verbindungsspezifisches DNS-Suffix: >Beschreibung. . . . . . . . . . . : Microsoft Loopbackadapter >Physikalische Adresse . . . . . . : 02-00-4C-4F-4F-50 >DHCP aktiviert. . . . . . . . . . : Ja >Autokonfiguration aktiviert . . . : Ja >Verbindungslokale IPv6-Adresse . : fe80::25d7:866d:f5c9:7295%31(Bevorzugt) >IPv4-Adresse (Auto. Konfiguration): 169.254.114.149(Bevorzugt) >Subnetzmaske . . . . . . . . . . : 255.255.0.0 >Standardgateway . . . . . . . . . : >DHCPv6-IAID . . . . . . . . . . . : 671219788 >DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-15-A4-69-BD-C0-F8-DA-35-64-02 >DNS-Server . . . . . . . . . . . : fec0:0:0:::1%1 >fec0:0:0:::2%1 >fec0:0:0:::3%1 >NetBIOS über TCP/IP . . . . . . . : Aktiviert > > > I tried to change the address to 127.0.0.1 without luck. When I switch > from "automatic" to "manual" in the properties menue and start the > IP address with 127 a window pops up announcing that an IP address > starting with 127 is reserved for the loopback adapter so that I couldn't > change the address. How did you manage to get the loopback adapter address > 127.0.0.1 or do you live with the message from Open MPI? Thank you very > much for a short answer in advance. > > > Kind regards > > Siegmar
Re: [OMPI users] error compiling openmpi-1.6.1 on Windows 7
Hi Siegmar, Glad to hear that it's working for you. The warning message is because the loopback adapter is excluded by default, but this adapter is actually not installed on Windows. One solution might be installing the loopback adapter on Windows. It very easy, only a few minutes. Or it may be possible to avoid this message from internal Open MPI. But I'm not sure about how this can be done. Regards, Shiqing On 2012-09-06 7:48 AM, Siegmar Gross wrote: Hi Shiqing, I have solved the problem with the double quotes in OPENMPI_HOME but there is still something wrong. set OPENMPI_HOME="c:\Program Files (x86)\openmpi-1.6.1" mpicc init_finalize.c Cannot open configuration file "c:\Program Files (x86)\openmpi-1.6.1"/share/openmpi\mpicc-wrapper-data.txt Error parsing data file mpicc: Not found Everything is OK if you remove the double quotes which Windows automatically adds. set OPENMPI_HOME=c:\Program Files (x86)\openmpi-1.6.1 mpicc init_finalize.c Microsoft (R) 32-Bit C/C++-Optimierungscompiler Version 16.00.40219.01 für 80x86 ... mpiexec init_finalize.exe -- WARNING: An invalid value was given for btl_tcp_if_exclude. This value will be ignored. Local host: hermes Value: 127.0.0.1/8 Message:Did not find interface matching this subnet -- Hello! I get the output from my program but also a warning from Open MPI. The new value for the loopback device was introduced a short time ago when I have had problems with the loopback device on Solaris (it used "lo0" instead of your default "lo"). How can I avoid this message? The 64-bit version of my program still hangs. Kind regards Siegmar Could you try set OPENMPI_HOME env var to the root of the Open MPI dir? This env is a backup option for the registry. It solves one problem but there is a new problem now :-(( Without OPENMPI_HOME: Wrong pathname to help files. D:\...\prog\mpi\small_prog>mpiexec init_finalize.exe -- Sorry! You were supposed to get help about: invalid if_inexclude But I couldn't open the help file: D:\...\prog\mpi\small_prog\..\share\openmpi\help-mpi-btl-tcp.txt: No such file or directory. Sorry! -- ... With OPENMPI_HOME: It nearly uses the correct directory. Unfortunately the pathname contains the character " in the wrong place so that it couldn't find the available help file. set OPENMPI_HOME="c:\Program Files (x86)\openmpi-1.6.1" D:\...\prog\mpi\small_prog>mpiexec init_finalize.exe -- Sorry! You were supposed to get help about: no-hostfile But I couldn't open the help file: "c:\Program Files (x86)\openmpi-1.6.1"\share\openmpi\help-hostfile.txt: Invalid argument. Sorry ! -- [hermes:04964] [[12187,0],0] ORTE_ERROR_LOG: Not found in file ..\..\openmpi-1.6.1\orte\mca\ras\base \ras_base_allocate.c at line 200 [hermes:04964] [[12187,0],0] ORTE_ERROR_LOG: Not found in file ..\..\openmpi-1.6.1\orte\mca\plm\base \plm_base_launch_support.c at line 99 [hermes:04964] [[12187,0],0] ORTE_ERROR_LOG: Not found in file ..\..\openmpi-1.6.1\orte\mca\plm\proc ess\plm_process_module.c at line 996 It looks like that the environment variable can also solve my problem in the 64-bit environment. D:\g...\prog\mpi\small_prog>mpicc init_finalize.c Microsoft (R) C/C++-Optimierungscompiler Version 16.00.40219.01 für x64 ... The process hangs without OPENMPI_HOME. D:\...\prog\mpi\small_prog>mpiexec init_finalize.exe ^C With OPENMPI_HOME: set OPENMPI_HOME="c:\Program Files\openmpi-1.6.1" D:\...\prog\mpi\small_prog>mpiexec init_finalize.exe -- Sorry! You were supposed to get help about: no-hostfile But I couldn't open the help file: "c:\Program Files\openmpi-1.6.1"\share\openmpi\help-hostfile.txt: Invalid argument. S orry! -- [hermes:05248] [[10367,0],0] ORTE_ERROR_LOG: Not found in file ..\..\openmpi-1.6.1\orte\mc a\ras\base\ras_base_allocate.c at line 200 [hermes:05248] [[10367,0],0] ORTE_ERROR_LOG: Not found in file ..\..\openmpi-1.6.1\orte\mc a\plm\base\plm_base_launch_support.c at line 99 [hermes:05248] [[10367,0],0] ORTE_ERROR_LOG: Not found in file ..\..\openmpi-1.6.1\orte\mc a\plm\process\plm_process_module.c at line 996 At least the program doesn't block any longer. Do you have any ideas how this new problem can be solved? Kind regards Siegmar On 2012-09-05 1:02 PM, Siegmar Gross wrote: Hi Shiqing, D:\...\prog\mpi\small_prog>mpiexec init_finalize.exe
Re: [OMPI users] error compiling openmpi-1.6.1 on Windows 7
Hi Shiqing, I have solved the problem with the double quotes in OPENMPI_HOME but there is still something wrong. set OPENMPI_HOME="c:\Program Files (x86)\openmpi-1.6.1" mpicc init_finalize.c Cannot open configuration file "c:\Program Files (x86)\openmpi-1.6.1"/share/openmpi\mpicc-wrapper-data.txt Error parsing data file mpicc: Not found Everything is OK if you remove the double quotes which Windows automatically adds. set OPENMPI_HOME=c:\Program Files (x86)\openmpi-1.6.1 mpicc init_finalize.c Microsoft (R) 32-Bit C/C++-Optimierungscompiler Version 16.00.40219.01 für 80x86 ... mpiexec init_finalize.exe -- WARNING: An invalid value was given for btl_tcp_if_exclude. This value will be ignored. Local host: hermes Value: 127.0.0.1/8 Message:Did not find interface matching this subnet -- Hello! I get the output from my program but also a warning from Open MPI. The new value for the loopback device was introduced a short time ago when I have had problems with the loopback device on Solaris (it used "lo0" instead of your default "lo"). How can I avoid this message? The 64-bit version of my program still hangs. Kind regards Siegmar > > Could you try set OPENMPI_HOME env var to the root of the Open MPI dir? > > This env is a backup option for the registry. > > It solves one problem but there is a new problem now :-(( > > > Without OPENMPI_HOME: Wrong pathname to help files. > > D:\...\prog\mpi\small_prog>mpiexec init_finalize.exe > -- > Sorry! You were supposed to get help about: > invalid if_inexclude > But I couldn't open the help file: > D:\...\prog\mpi\small_prog\..\share\openmpi\help-mpi-btl-tcp.txt: > No such file or directory. Sorry! > -- > ... > > > > With OPENMPI_HOME: It nearly uses the correct directory. Unfortunately > the pathname contains the character " in the wrong place so that it > couldn't find the available help file. > > set OPENMPI_HOME="c:\Program Files (x86)\openmpi-1.6.1" > > D:\...\prog\mpi\small_prog>mpiexec init_finalize.exe > -- > Sorry! You were supposed to get help about: > no-hostfile > But I couldn't open the help file: > "c:\Program Files (x86)\openmpi-1.6.1"\share\openmpi\help-hostfile.txt: > Invalid argument. Sorry > ! > -- > [hermes:04964] [[12187,0],0] ORTE_ERROR_LOG: Not found in file > ..\..\openmpi-1.6.1\orte\mca\ras\base > \ras_base_allocate.c at line 200 > [hermes:04964] [[12187,0],0] ORTE_ERROR_LOG: Not found in file > ..\..\openmpi-1.6.1\orte\mca\plm\base > \plm_base_launch_support.c at line 99 > [hermes:04964] [[12187,0],0] ORTE_ERROR_LOG: Not found in file > ..\..\openmpi-1.6.1\orte\mca\plm\proc > ess\plm_process_module.c at line 996 > > > > It looks like that the environment variable can also solve my > problem in the 64-bit environment. > > D:\g...\prog\mpi\small_prog>mpicc init_finalize.c > > Microsoft (R) C/C++-Optimierungscompiler Version 16.00.40219.01 für x64 > ... > > > The process hangs without OPENMPI_HOME. > > D:\...\prog\mpi\small_prog>mpiexec init_finalize.exe > ^C > > > With OPENMPI_HOME: > > set OPENMPI_HOME="c:\Program Files\openmpi-1.6.1" > > D:\...\prog\mpi\small_prog>mpiexec init_finalize.exe > -- > Sorry! You were supposed to get help about: > no-hostfile > But I couldn't open the help file: > "c:\Program Files\openmpi-1.6.1"\share\openmpi\help-hostfile.txt: Invalid > argument. S > orry! > -- > [hermes:05248] [[10367,0],0] ORTE_ERROR_LOG: Not found in file > ..\..\openmpi-1.6.1\orte\mc > a\ras\base\ras_base_allocate.c at line 200 > [hermes:05248] [[10367,0],0] ORTE_ERROR_LOG: Not found in file > ..\..\openmpi-1.6.1\orte\mc > a\plm\base\plm_base_launch_support.c at line 99 > [hermes:05248] [[10367,0],0] ORTE_ERROR_LOG: Not found in file > ..\..\openmpi-1.6.1\orte\mc > a\plm\process\plm_process_module.c at line 996 > > > At least the program doesn't block any longer. Do you have any ideas > how this new problem can be solved? > > > Kind regards > > Siegmar > > > > > On 2012-09-05 1:02 PM, Siegmar Gross wrote: > > > Hi Shiqing, > > > > > D:\...\prog\mpi\small_prog>mpiexec init_finalize.exe > > - > > Sorry! You were supposed to get help about: > > invalid if_inexclude > > But I couldn't open the help file: > > D:\...\prog\mpi\small_prog\..\share\openmpi\help-mpi-btl-tcp.txt:
Re: [OMPI users] error compiling openmpi-1.6.1 on Windows 7
Hi Shiqing, > Could you try set OPENMPI_HOME env var to the root of the Open MPI dir? > This env is a backup option for the registry. It solves one problem but there is a new problem now :-(( Without OPENMPI_HOME: Wrong pathname to help files. D:\...\prog\mpi\small_prog>mpiexec init_finalize.exe -- Sorry! You were supposed to get help about: invalid if_inexclude But I couldn't open the help file: D:\...\prog\mpi\small_prog\..\share\openmpi\help-mpi-btl-tcp.txt: No such file or directory. Sorry! -- ... With OPENMPI_HOME: It nearly uses the correct directory. Unfortunately the pathname contains the character " in the wrong place so that it couldn't find the available help file. set OPENMPI_HOME="c:\Program Files (x86)\openmpi-1.6.1" D:\...\prog\mpi\small_prog>mpiexec init_finalize.exe -- Sorry! You were supposed to get help about: no-hostfile But I couldn't open the help file: "c:\Program Files (x86)\openmpi-1.6.1"\share\openmpi\help-hostfile.txt: Invalid argument. Sorry ! -- [hermes:04964] [[12187,0],0] ORTE_ERROR_LOG: Not found in file ..\..\openmpi-1.6.1\orte\mca\ras\base \ras_base_allocate.c at line 200 [hermes:04964] [[12187,0],0] ORTE_ERROR_LOG: Not found in file ..\..\openmpi-1.6.1\orte\mca\plm\base \plm_base_launch_support.c at line 99 [hermes:04964] [[12187,0],0] ORTE_ERROR_LOG: Not found in file ..\..\openmpi-1.6.1\orte\mca\plm\proc ess\plm_process_module.c at line 996 It looks like that the environment variable can also solve my problem in the 64-bit environment. D:\g...\prog\mpi\small_prog>mpicc init_finalize.c Microsoft (R) C/C++-Optimierungscompiler Version 16.00.40219.01 für x64 ... The process hangs without OPENMPI_HOME. D:\...\prog\mpi\small_prog>mpiexec init_finalize.exe ^C With OPENMPI_HOME: set OPENMPI_HOME="c:\Program Files\openmpi-1.6.1" D:\...\prog\mpi\small_prog>mpiexec init_finalize.exe -- Sorry! You were supposed to get help about: no-hostfile But I couldn't open the help file: "c:\Program Files\openmpi-1.6.1"\share\openmpi\help-hostfile.txt: Invalid argument. S orry! -- [hermes:05248] [[10367,0],0] ORTE_ERROR_LOG: Not found in file ..\..\openmpi-1.6.1\orte\mc a\ras\base\ras_base_allocate.c at line 200 [hermes:05248] [[10367,0],0] ORTE_ERROR_LOG: Not found in file ..\..\openmpi-1.6.1\orte\mc a\plm\base\plm_base_launch_support.c at line 99 [hermes:05248] [[10367,0],0] ORTE_ERROR_LOG: Not found in file ..\..\openmpi-1.6.1\orte\mc a\plm\process\plm_process_module.c at line 996 At least the program doesn't block any longer. Do you have any ideas how this new problem can be solved? Kind regards Siegmar > On 2012-09-05 1:02 PM, Siegmar Gross wrote: > > Hi Shiqing, > > > D:\...\prog\mpi\small_prog>mpiexec init_finalize.exe > - > Sorry! You were supposed to get help about: > invalid if_inexclude > But I couldn't open the help file: > D:\...\prog\mpi\small_prog\..\share\openmpi\help-mpi-btl-tcp.txt: > No such file or directory. Sorry! > - > >>> ... > Why does "mpiexec" look for the help file relativ to my current > program and not relative to itself? The file is part of the > package. > >>> Do you know how I can solve this problem? > >> I have similar issue with message from tcp, but it's not finding the > >> file, it's something else, which doesn't affect the execution of the > >> application. Could you make sure the help-mpi-btl-tcp.txt is actually in > >> the path D:\...\prog\mpi\small_prog\..\share\openmpi\? > > That wouldn't be a good idea because I have MPI programs in different > > directories so that I would have to install all help files in several > > places (/../share/openmpi/help*.txt). All help files are > > available in the installation directory of Open MPI. > > > > dir "c:\Program Files (x86)\openmpi-1.6.1\bin\mpiexec.exe" > > ... > > 29.08.2012 10:5938.912 mpiexec.exe > > ... > > dir "c:\Program Files > > (x86)\openmpi-1.6.1\bin\..\share\openmpi\help-mpi-btl-tcp.txt" > > ... > > 03.04.2012 16:30 631 help-mpi-btl-tcp.txt > > ... > > > > I don't know if "mpiexec" or my program "init_finilize" is responsible > > for the error message but whoever is responsible shouldn't use the path > > to my program but the prefix_dir from MPI to find the help files. Perhaps > > you can change the behaviour in the Open MPI source code. > > > > > I can also
Re: [OMPI users] error compiling openmpi-1.6.1 on Windows 7
Hi Shiqing, > Could you please send the output of ompi_info command under you 64 bit > env? And could you please also check if you have CCP or HPC pack > installed? The incorrect configuration of that might cause Open MPI hanging. I haven't installed Microsoft's Compute Cluster Pack or High Performance Computing Pack. At the moment I'm testing Open MPI on my Acer notebook with Windows 7 Professional SP1. "ompi_info" hangs as well before it prints any information about mca modules. C:\Program Files\openmpi-1.6.1\bin>ompi_info Package: Open MPI Admin@HERMES Distribution Open MPI: 1.6.1 Open MPI SVN revision: r27106 Open MPI release date: Aug 22, 2012 Open RTE: 1.6.1 Open RTE SVN revision: r27106 Open RTE release date: Aug 22, 2012 OPAL: 1.6.1 OPAL SVN revision: r27106 OPAL release date: Aug 22, 2012 MPI API: 2.1 Ident string: 1.6.1 Prefix: C:\Program Files\openmpi-1.6.1\bin/.. Configured architecture: Windows-6.1 64 bit Configure host: HERMES Configured by: Admin Configured on: 14:40 27.08.2012 Configure host: HERMES Built by: Admin Built on: 14:40 27.08.2012 Built host: HERMES C bindings: yes C++ bindings: yes Fortran77 bindings: no Fortran90 bindings: no Fortran90 bindings size: na C compiler: cl C compiler absolute: cl C compiler family name: MICROSOFT C compiler version: 1600 C++ compiler: cl C++ compiler absolute: cl Fortran77 compiler: none Fortran77 compiler abs: none Fortran90 compiler: none Fortran90 compiler abs: none C profiling: yes C++ profiling: yes Fortran77 profiling: no Fortran90 profiling: no C++ exceptions: no Thread support: no Sparse Groups: no Internal debug support: no MPI interface warnings: no MPI parameter check: never Memory profiling support: no Memory debugging support: no libltdl support: no Heterogeneous support: yes mpirun default --prefix: yes MPI I/O support: yes MPI_WTIME support: gettimeofday Symbol vis. support: yes Host topology support: no MPI extensions: none FT Checkpoint support: yes (checkpoint thread: no) VampirTrace support: no MPI_MAX_PROCESSOR_NAME: 256 MPI_MAX_ERROR_STRING: 256 MPI_MAX_OBJECT_NAME: 64 MPI_MAX_INFO_KEY: 36 MPI_MAX_INFO_VAL: 256 MPI_MAX_PORT_NAME: 1024 MPI_MAX_DATAREP_STRING: 128 Kind regards Siegmar > On 2012-08-29 12:33 PM, Siegmar Gross wrote: > > Hi Shiqing, > > > >> It seems that the runtime environment is messed up with the different > >> versions of Open MPI. I suggest you completely remove all the > >> installations and install 1.6.1 again (just build the installation > >> project again). It should work without any problem under Cygwin too. > > I removed openmpi-1.6 und rebuilt openmpi-1.6.1. Now I can compile and > > run a program in 32-bit mode but have still some problems. > > > > D:\...\prog\mpi\small_prog>mpicc init_finalize.c > > Microsoft (R) 32-Bit C/C++-Optimierungscompiler Version > >16.00.40219.01 für 80x86 > > Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten. > > > > init_finalize.c > > Microsoft (R) Incremental Linker Version 10.00.40219.01 > > Copyright (C) Microsoft Corporation. All rights reserved. > > > > /out:init_finalize.exe > > "/LIBPATH:C:\Program Files (x86)\openmpi-1.6.1\bin/../lib" > > libmpi.lib > > libopen-pal.lib > > libopen-rte.lib > > advapi32.lib > > Ws2_32.lib > > shlwapi.lib > > init_finalize.obj > > > > D:\...\prog\mpi\small_prog>mpiexec init_finalize.exe > > - > > Sorry! You were supposed to get help about: > > invalid if_inexclude > > But I couldn't open the help file: > > D:\...\prog\mpi\small_prog\..\share\openmpi\help-mpi-btl-tcp.txt: > > No such file or directory. Sorry! > > - > > > > Hello! > > > > > > Why does "mpiexec" look for the help file relativ to my current > > program and not relative to itself? The file is part of the > > package. > > > > dir "c:\Program Files (x86)\openmpi-1.6.1\share\openmpi\help-mpi-btl-tcp.txt" > > ... > > 03.04.2012 16:30 631 help-mpi-btl-tcp.txt > > > > Must I change something in the source code or can I set an environment > > variable for help files? Why does "mpiexec" want to give some help at all? > > I don't get this message for openmpi-1.5.1. > > > > > > D:\...\prog\mpi\small_prog>mpicc init_finalize.c > > Microsoft (R) 32-Bit C/C++-Optimierungscompiler Version 16.00.40219.01 > >für 80x86 > > Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten. > > > > init_finalize.c >
Re: [OMPI users] error compiling openmpi-1.6.1 on Windows 7
Hi Siegmar,
Could you please send the output of ompi_info command under you 64 bit
env? And could you please also check if you have CCP or HPC pack
installed? The incorrect configuration of that might cause Open MPI hanging.
Regards,
Shiqing
On 2012-08-29 12:33 PM, Siegmar Gross wrote:
Hi Shiqing,
It seems that the runtime environment is messed up with the different
versions of Open MPI. I suggest you completely remove all the
installations and install 1.6.1 again (just build the installation
project again). It should work without any problem under Cygwin too.
I removed openmpi-1.6 und rebuilt openmpi-1.6.1. Now I can compile and
run a program in 32-bit mode but have still some problems.
D:\...\prog\mpi\small_prog>mpicc init_finalize.c
Microsoft (R) 32-Bit C/C++-Optimierungscompiler Version
16.00.40219.01 für 80x86
Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten.
init_finalize.c
Microsoft (R) Incremental Linker Version 10.00.40219.01
Copyright (C) Microsoft Corporation. All rights reserved.
/out:init_finalize.exe
"/LIBPATH:C:\Program Files (x86)\openmpi-1.6.1\bin/../lib"
libmpi.lib
libopen-pal.lib
libopen-rte.lib
advapi32.lib
Ws2_32.lib
shlwapi.lib
init_finalize.obj
D:\...\prog\mpi\small_prog>mpiexec init_finalize.exe
-
Sorry! You were supposed to get help about:
invalid if_inexclude
But I couldn't open the help file:
D:\...\prog\mpi\small_prog\..\share\openmpi\help-mpi-btl-tcp.txt:
No such file or directory. Sorry!
-
Hello!
Why does "mpiexec" look for the help file relativ to my current
program and not relative to itself? The file is part of the
package.
dir "c:\Program Files (x86)\openmpi-1.6.1\share\openmpi\help-mpi-btl-tcp.txt"
...
03.04.2012 16:30 631 help-mpi-btl-tcp.txt
Must I change something in the source code or can I set an environment
variable for help files? Why does "mpiexec" want to give some help at all?
I don't get this message for openmpi-1.5.1.
D:\...\prog\mpi\small_prog>mpicc init_finalize.c
Microsoft (R) 32-Bit C/C++-Optimierungscompiler Version 16.00.40219.01
für 80x86
Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten.
init_finalize.c
Microsoft (R) Incremental Linker Version 10.00.40219.01
Copyright (C) Microsoft Corporation. All rights reserved.
/out:init_finalize.exe
"/LIBPATH:C:/Program Files (x86)/openmpi-1.5.1/lib"
libmpi.lib
libopen-pal.lib
libopen-rte.lib
advapi32.lib
Ws2_32.lib
shlwapi.lib
init_finalize.obj
D:\...\prog\mpi\small_prog>mpiexec init_finalize.exe
Hello!
D:\...\prog\mpi\small_prog>
I can also compile in 64-bit mode but the program hangs.
D:\...\prog\mpi\small_prog>mpicc init_finalize.c
Microsoft (R) C/C++-Optimierungscompiler Version 16.00.40219.01 für x64
Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten.
init_finalize.c
Microsoft (R) Incremental Linker Version 10.00.40219.01
Copyright (C) Microsoft Corporation. All rights reserved.
/out:init_finalize.exe
"/LIBPATH:C:\Program Files\openmpi-1.6.1\bin/../lib"
libmpi.lib
libopen-pal.lib
libopen-rte.lib
advapi32.lib
Ws2_32.lib
shlwapi.lib
init_finalize.obj
D:\...\prog\mpi\small_prog>mpiexec init_finalize.exe
^C
D:\...\prog\mpi\small_prog>
It's the same if I compile a 64-bit program with openmpi-1.5.1. The program
itself is very small.
#include
#include
#include "mpi.h"
int main (int argc, char *argv[])
{
MPI_Init (, );
printf ("Hello!\n");
MPI_Finalize ();
return EXIT_SUCCESS;
}
Any ideas why the 64-bit version hangs? Thank you very much for any help
in advance.
Kind regards
Siegmar
___
users mailing list
us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users
--
---
Shiqing Fan
High Performance Computing Center Stuttgart (HLRS)
Tel: ++49(0)711-685-87234 Nobelstrasse 19
Fax: ++49(0)711-685-65832 70569 Stuttgart
http://www.hlrs.de/organization/people/shiqing-fan/
email: f...@hlrs.de
Re: [OMPI users] error compiling openmpi-1.6.1 on Windows 7
Hi Shiqing,
> It seems that the runtime environment is messed up with the different
> versions of Open MPI. I suggest you completely remove all the
> installations and install 1.6.1 again (just build the installation
> project again). It should work without any problem under Cygwin too.
I removed openmpi-1.6 und rebuilt openmpi-1.6.1. Now I can compile and
run a program in 32-bit mode but have still some problems.
D:\...\prog\mpi\small_prog>mpicc init_finalize.c
Microsoft (R) 32-Bit C/C++-Optimierungscompiler Version
16.00.40219.01 für 80x86
Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten.
init_finalize.c
Microsoft (R) Incremental Linker Version 10.00.40219.01
Copyright (C) Microsoft Corporation. All rights reserved.
/out:init_finalize.exe
"/LIBPATH:C:\Program Files (x86)\openmpi-1.6.1\bin/../lib"
libmpi.lib
libopen-pal.lib
libopen-rte.lib
advapi32.lib
Ws2_32.lib
shlwapi.lib
init_finalize.obj
D:\...\prog\mpi\small_prog>mpiexec init_finalize.exe
-
Sorry! You were supposed to get help about:
invalid if_inexclude
But I couldn't open the help file:
D:\...\prog\mpi\small_prog\..\share\openmpi\help-mpi-btl-tcp.txt:
No such file or directory. Sorry!
-
Hello!
Why does "mpiexec" look for the help file relativ to my current
program and not relative to itself? The file is part of the
package.
dir "c:\Program Files (x86)\openmpi-1.6.1\share\openmpi\help-mpi-btl-tcp.txt"
...
03.04.2012 16:30 631 help-mpi-btl-tcp.txt
Must I change something in the source code or can I set an environment
variable for help files? Why does "mpiexec" want to give some help at all?
I don't get this message for openmpi-1.5.1.
D:\...\prog\mpi\small_prog>mpicc init_finalize.c
Microsoft (R) 32-Bit C/C++-Optimierungscompiler Version 16.00.40219.01
für 80x86
Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten.
init_finalize.c
Microsoft (R) Incremental Linker Version 10.00.40219.01
Copyright (C) Microsoft Corporation. All rights reserved.
/out:init_finalize.exe
"/LIBPATH:C:/Program Files (x86)/openmpi-1.5.1/lib"
libmpi.lib
libopen-pal.lib
libopen-rte.lib
advapi32.lib
Ws2_32.lib
shlwapi.lib
init_finalize.obj
D:\...\prog\mpi\small_prog>mpiexec init_finalize.exe
Hello!
D:\...\prog\mpi\small_prog>
I can also compile in 64-bit mode but the program hangs.
D:\...\prog\mpi\small_prog>mpicc init_finalize.c
Microsoft (R) C/C++-Optimierungscompiler Version 16.00.40219.01 für x64
Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten.
init_finalize.c
Microsoft (R) Incremental Linker Version 10.00.40219.01
Copyright (C) Microsoft Corporation. All rights reserved.
/out:init_finalize.exe
"/LIBPATH:C:\Program Files\openmpi-1.6.1\bin/../lib"
libmpi.lib
libopen-pal.lib
libopen-rte.lib
advapi32.lib
Ws2_32.lib
shlwapi.lib
init_finalize.obj
D:\...\prog\mpi\small_prog>mpiexec init_finalize.exe
^C
D:\...\prog\mpi\small_prog>
It's the same if I compile a 64-bit program with openmpi-1.5.1. The program
itself is very small.
#include
#include
#include "mpi.h"
int main (int argc, char *argv[])
{
MPI_Init (, );
printf ("Hello!\n");
MPI_Finalize ();
return EXIT_SUCCESS;
}
Any ideas why the 64-bit version hangs? Thank you very much for any help
in advance.
Kind regards
Siegmar
Re: [OMPI users] error compiling openmpi-1.6.1 on Windows 7
Hi Siegmar, It seems that the runtime environment is messed up with the different versions of Open MPI. I suggest you completely remove all the installations and install 1.6.1 again (just build the installation project again). It should work without any problem under Cygwin too. Shiqing On 2012-08-27 4:02 PM, Siegmar Gross wrote: Hi, thank you very much for your reply. I compiled and installed openmpi-1.6.1. Unfortunately I cannot compile programs because "mpicc" uses wrong path names. I have set an environment for openmpi-1.6.1 as you can see from the following output. D:\...prog\mpi\small_prog>set | c:\cygwin\bin\grep openmpi LIB=C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\lib\amd64; C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\atlmfc\lib\amd64; C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Lib\x64; C:\Program Files\openmpi-1.6.1\lib LIBPATH=C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\lib\amd64; C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\atlmfc\lib\amd64; C:\Program Files\openmpi-1.6.1\lib Path=C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\amd64; C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\vcpackages; C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\; C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\Tools\; C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin\NETFX 4.0 Tools\x64; C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin\x64; C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin\; C:\Windows\System32; C:\Windows; C:\Windows\System32\Wbem; C:\Program Files\openmpi-1.6.1\bin; C:\cmd;. I get the following error when I try to compile my program because of "/LIBPATH:C:\Program Files (x86)\openmpi-1.6/lib". D:\...\prog\mpi\small_prog>mpicc init_finalize.c Microsoft (R) C/C++-Optimierungscompiler Version 16.00.40219.01 für x64 Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten. init_finalize.c Microsoft (R) Incremental Linker Version 10.00.40219.01 Copyright (C) Microsoft Corporation. All rights reserved. /out:init_finalize.exe "/LIBPATH:C:\Program Files (x86)\openmpi-1.6/lib" libmpi.lib libopen-pal.lib libopen-rte.lib advapi32.lib Ws2_32.lib shlwapi.lib init_finalize.obj init_finalize.obj : error LNK2019: Verweis auf nicht aufgelöstes externes Symbol "__imp_MP I_Finalize" in Funktion "main". init_finalize.obj : error LNK2019: Verweis auf nicht aufgelöstes externes Symbol "__imp_MP I_Init" in Funktion "main". init_finalize.exe : fatal error LNK1120: 2 nicht aufgelöste externe Verweise. When I start in a new command shell without my MPI environment, I get the following outputs for "mpicc -show". The first one is OK, but both others are wrong because they point to 32-bit libraries instead of 64-bit ones. Why do both versions point to openmpi-1.6? I downloaded and installed the precompiled 32- and 64-bit version 1.6 from open-mpi.org. C:\Program Files>openmpi-1.5.1\bin\mpicc -show cl.exe /I"C:/Program Files/openmpi-1.5.1/include" /TC /D "OMPI_IMPORTS" /D "OPAL_IMPORTS" /D "ORTE_IMPORTS" /link /LIBPATH:"C:/Program Files/openmpi-1.5.1/lib" libmpi.lib libopen-p al.lib libopen-rte.lib advapi32.lib Ws2_32.lib shlwapi.lib C:\Program Files>openmpi-1.6\bin\mpicc -show cl.exe /I"C:\Program Files (x86)\openmpi-1.6/include" /TC /DOMPI_IMPORTS /DOPAL_IMPORTS /D ORTE_IMPORTS /link /LIBPATH:"C:\Program Files (x86)\openmpi-1.6/lib" libmpi.lib libopen-pa l.lib libopen-rte.lib advapi32.lib Ws2_32.lib shlwapi.lib C:\Program Files>openmpi-1.6.1\bin\mpicc -show cl.exe /I"C:\Program Files (x86)\openmpi-1.6/include" /TC /DOMPI_IMPORTS /DOPAL_IMPORTS /D ORTE_IMPORTS /link /LIBPATH:"C:\Program Files (x86)\openmpi-1.6/lib" libmpi.lib libopen-pa l.lib libopen-rte.lib advapi32.lib Ws2_32.lib shlwapi.lib Do you have any idea what I have done wrong? Thank you very much for any help in advance. Kind regards Siegmar I didn't have this problem when building the binary release. But to solve the problem is very easy. You can just open \openmpi-1.6.1\ompi\mca\osc\rdma\osc_rdma_data_move.c, and go to line 1099, change "void*" to "void**". This will get rid of the error. For the warnings, they are just some redefinitions that cannot be avoided, they are totally harmless. Regards, Shiqing On 2012-08-27 1:02 PM, Siegmar Gross wrote: Hi, I tried to compile openmpi-1.6.1 with CMake-2.8.3 and Visual Studio 2010 on Windows 7. All service packs and patches from Microsoft are installed. I changed the following options: CMAKE_BUILD_TYPE: "Debug" modified to "Release" CMAKE_INSTALL_PREFIX: modified to "c:/Program Files (x86)/openmpi-1.6.1" OMPI_ENABLE_THREAD_MULTIPLE: "no" changed to "yes" OMPI_RELEASE_BUILD: "no" changed to "yes" OPAL_ENABLE_HETEREOGENEOUS:SUPPORT: "no" changed to "yes" OPAL_ENABLE_IPV6: "yes" changed to "no" OPAL_ENABLE_MULTI_THREADS: "no" changed to "yes" I also selected "Release" in "Visual Studio".
Re: [OMPI users] error compiling openmpi-1.6.1 on Windows 7
Hi,
thank you very much for your reply. I compiled and installed
openmpi-1.6.1. Unfortunately I cannot compile programs because
"mpicc" uses wrong path names. I have set an environment for
openmpi-1.6.1 as you can see from the following output.
D:\...prog\mpi\small_prog>set | c:\cygwin\bin\grep openmpi
LIB=C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\lib\amd64;
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\atlmfc\lib\amd64;
C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Lib\x64;
C:\Program Files\openmpi-1.6.1\lib
LIBPATH=C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\lib\amd64;
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\atlmfc\lib\amd64;
C:\Program Files\openmpi-1.6.1\lib
Path=C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\amd64;
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\vcpackages;
C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\;
C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\Tools\;
C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin\NETFX 4.0 Tools\x64;
C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin\x64;
C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin\;
C:\Windows\System32;
C:\Windows;
C:\Windows\System32\Wbem;
C:\Program Files\openmpi-1.6.1\bin;
C:\cmd;.
I get the following error when I try to compile my program
because of "/LIBPATH:C:\Program Files (x86)\openmpi-1.6/lib".
D:\...\prog\mpi\small_prog>mpicc init_finalize.c
Microsoft (R) C/C++-Optimierungscompiler Version 16.00.40219.01 für x64
Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten.
init_finalize.c
Microsoft (R) Incremental Linker Version 10.00.40219.01
Copyright (C) Microsoft Corporation. All rights reserved.
/out:init_finalize.exe
"/LIBPATH:C:\Program Files (x86)\openmpi-1.6/lib"
libmpi.lib
libopen-pal.lib
libopen-rte.lib
advapi32.lib
Ws2_32.lib
shlwapi.lib
init_finalize.obj
init_finalize.obj : error LNK2019: Verweis auf nicht aufgelöstes externes
Symbol "__imp_MP
I_Finalize" in Funktion "main".
init_finalize.obj : error LNK2019: Verweis auf nicht aufgelöstes externes
Symbol "__imp_MP
I_Init" in Funktion "main".
init_finalize.exe : fatal error LNK1120: 2 nicht aufgelöste externe Verweise.
When I start in a new command shell without my MPI environment,
I get the following outputs for "mpicc -show". The first one
is OK, but both others are wrong because they point to 32-bit
libraries instead of 64-bit ones. Why do both versions point
to openmpi-1.6? I downloaded and installed the precompiled
32- and 64-bit version 1.6 from open-mpi.org.
C:\Program Files>openmpi-1.5.1\bin\mpicc -show
cl.exe /I"C:/Program Files/openmpi-1.5.1/include" /TC /D "OMPI_IMPORTS" /D
"OPAL_IMPORTS"
/D "ORTE_IMPORTS" /link /LIBPATH:"C:/Program Files/openmpi-1.5.1/lib"
libmpi.lib libopen-p
al.lib libopen-rte.lib advapi32.lib Ws2_32.lib shlwapi.lib
C:\Program Files>openmpi-1.6\bin\mpicc -show
cl.exe /I"C:\Program Files (x86)\openmpi-1.6/include" /TC /DOMPI_IMPORTS
/DOPAL_IMPORTS /D
ORTE_IMPORTS /link /LIBPATH:"C:\Program Files (x86)\openmpi-1.6/lib" libmpi.lib
libopen-pa
l.lib libopen-rte.lib advapi32.lib Ws2_32.lib shlwapi.lib
C:\Program Files>openmpi-1.6.1\bin\mpicc -show
cl.exe /I"C:\Program Files (x86)\openmpi-1.6/include" /TC /DOMPI_IMPORTS
/DOPAL_IMPORTS /D
ORTE_IMPORTS /link /LIBPATH:"C:\Program Files (x86)\openmpi-1.6/lib" libmpi.lib
libopen-pa
l.lib libopen-rte.lib advapi32.lib Ws2_32.lib shlwapi.lib
Do you have any idea what I have done wrong? Thank you very
much for any help in advance.
Kind regards
Siegmar
> I didn't have this problem when building the binary release.
>
> But to solve the problem is very easy. You can just open
> \openmpi-1.6.1\ompi\mca\osc\rdma\osc_rdma_data_move.c, and go
> to line 1099, change "void*" to "void**". This will get rid of the error.
>
> For the warnings, they are just some redefinitions that cannot
> be avoided, they are totally harmless.
>
>
> Regards,
> Shiqing
>
>
>
>
> On 2012-08-27 1:02 PM, Siegmar Gross wrote:
> > Hi,
> >
> > I tried to compile openmpi-1.6.1 with CMake-2.8.3 and Visual Studio
> > 2010 on Windows 7. All service packs and patches from Microsoft are
> > installed.
> >
> > I changed the following options:
> >
> > CMAKE_BUILD_TYPE: "Debug" modified to "Release"
> > CMAKE_INSTALL_PREFIX: modified to "c:/Program Files (x86)/openmpi-1.6.1"
> > OMPI_ENABLE_THREAD_MULTIPLE: "no" changed to "yes"
> > OMPI_RELEASE_BUILD: "no" changed to "yes"
> > OPAL_ENABLE_HETEREOGENEOUS:SUPPORT: "no" changed to "yes"
> > OPAL_ENABLE_IPV6: "yes" changed to "no"
> > OPAL_ENABLE_MULTI_THREADS: "no" changed to "yes"
> >
> > I also selected "Release" in "Visual Studio". Unfortunately I got the
> > following error ("void *" cannot be converted to "void **").
> >
> > Fehler 77 error C2440: '=': 'void *' kann nicht in 'void **'
> >konvertiert werden
> >...\openmpi-1.6.1\ompi\mca\osc\rdma\osc_rdma_data_move.c
> >1099
Re: [OMPI users] error compiling openmpi-1.6.1 on Windows 7
Hi Siegmar,
I didn't have this problem when building the binary release.
But to solve the problem is very easy. You can just open
\openmpi-1.6.1\ompi\mca\osc\rdma\osc_rdma_data_move.c, and go to line 1099, change
"void*" to "void**". This will get rid of the error.
For the warnings, they are just some redefinitions that cannot be avoided, they
are totally harmless.
Regards,
Shiqing
On 2012-08-27 1:02 PM, Siegmar Gross wrote:
Hi,
I tried to compile openmpi-1.6.1 with CMake-2.8.3 and Visual Studio
2010 on Windows 7. All service packs and patches from Microsoft are
installed.
I changed the following options:
CMAKE_BUILD_TYPE: "Debug" modified to "Release"
CMAKE_INSTALL_PREFIX: modified to "c:/Program Files (x86)/openmpi-1.6.1"
OMPI_ENABLE_THREAD_MULTIPLE: "no" changed to "yes"
OMPI_RELEASE_BUILD: "no" changed to "yes"
OPAL_ENABLE_HETEREOGENEOUS:SUPPORT: "no" changed to "yes"
OPAL_ENABLE_IPV6: "yes" changed to "no"
OPAL_ENABLE_MULTI_THREADS: "no" changed to "yes"
I also selected "Release" in "Visual Studio". Unfortunately I got the
following error ("void *" cannot be converted to "void **").
Fehler 77 error C2440: '=': 'void *' kann nicht in 'void **'
konvertiert werden
...\openmpi-1.6.1\ompi\mca\osc\rdma\osc_rdma_data_move.c
1099 1 libmpi
Fehler 90 error LNK1181: Eingabedatei "..\..\..\Release\libmpi.lib"
kann nicht geöffnet werden.
...\openmpi-1.6.1-Windows_VS2010_x32\ompi\tools\ompi-server\LINK
ompi-server
Fehler 94 error LNK1181: Eingabedatei "..\..\..\Release\libmpi.lib"
kann nicht geöffnet werden.
...\openmpi-1.6.1-Windows_VS2010_x32\ompi\tools\ompi_info\LINK
ompi_info
Fehler 162 error LNK1181: Eingabedatei "..\..\..\Release\libmpi.lib"
kann nicht geöffnet werden.
...\openmpi-1.6.1-Windows_VS2010_x32\ompi\mpi\cxx\LINK
libmpi_cxx
I get also a lot of warnings, from wich I have listed a few.
Warnung 1 warning C4005: 'PACKAGE_BUGREPORT': Makro-Neudefinition
...\openmpi-1.6.1\opal\event\win32-code\config.h
185 1 libopen-pal
Warnung 2 warning C4005: 'PACKAGE_NAME': Makro-Neudefinition
...\openmpi-1.6.1\opal\event\win32-code\config.h
188 1 libopen-pal
Warnung 3 warning C4005: 'PACKAGE_STRING': Makro-Neudefinition
...\openmpi-1.6.1\opal\event\win32-code\config.h
191 1 libopen-pal
Warnung 4 warning C4005: 'PACKAGE_TARNAME': Makro-Neudefinition
...\openmpi-1.6.1\opal\event\win32-code\config.h
194 1 libopen-pal
Warnung 5 warning C4005: 'PACKAGE_VERSION': Makro-Neudefinition
...\openmpi-1.6.1\opal\event\win32-code\config.h
197 1 libopen-pal
Warnung 6 warning C4005: '__func__': Makro-Neudefinition
...\openmpi-1.6.1\opal\event\win32-code\config.h
212 1 libopen-pal
Warnung 7 warning C4013: 'opal_event_warn' undefiniert;
Annahme: extern mit Rückgabetyp int
...\openmpi-1.6.1\opal\event\WIN32-Code\win32.c
170 1 libopen-pal
Warnung 8 warning C4005: 'INT8_MIN': Makro-Neudefinition
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\stdint.h
72 1 libopen-pal
Warnung 9 warning C4005: 'INT16_MIN': Makro-Neudefinition
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\stdint.h
73 1 libopen-pal
Warnung 10 warning C4005: 'INT32_MIN': Makro-Neudefinition
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\stdint.h
74 1 libopen-pal
Warnung 11 warning C4005: 'INT8_MAX': Makro-Neudefinition
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\stdint.h
76 1 libopen-pal
Warnung 12 warning C4005: 'INT16_MAX': Makro-Neudefinition
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\stdint.h
77 1 libopen-pal
Warnung 13 warning C4005: 'INT32_MAX': Makro-Neudefinition
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\stdint.h
78 1 libopen-pal
Warnung 14 warning C4005: 'UINT8_MAX': Makro-Neudefinition
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\stdint.h
79 1 libopen-pal
Warnung 15 warning C4005: 'UINT16_MAX': Makro-Neudefinition
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\stdint.h
80 1 libopen-pal
Warnung 16 warning C4005: 'UINT32_MAX': Makro-Neudefinition
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\stdint.h
81 1 libopen-pal
Warnung 17 warning C4018: '<': Konflikt zwischen 'signed' und 'unsigned'
...\openmpi-1.6.1-Windows_VS2010_x32\opal\keyval_lex.c
libopen-pal
Warnung 18 warning C4273: '_isatty': Inkonsistente DLL-Bindung.
...\openmpi-1.6.1-Windows_VS2010_x32\opal\keyval_lex.c
libopen-pal
...
What can I do to get around the error so that I can compile Open MPI?
Thank you very much for any suggestions in advance.
Kind regards
Siegmar
___
users mailing
[OMPI users] error compiling openmpi-1.6.1 on Windows 7
Hi,
I tried to compile openmpi-1.6.1 with CMake-2.8.3 and Visual Studio
2010 on Windows 7. All service packs and patches from Microsoft are
installed.
I changed the following options:
CMAKE_BUILD_TYPE: "Debug" modified to "Release"
CMAKE_INSTALL_PREFIX: modified to "c:/Program Files (x86)/openmpi-1.6.1"
OMPI_ENABLE_THREAD_MULTIPLE: "no" changed to "yes"
OMPI_RELEASE_BUILD: "no" changed to "yes"
OPAL_ENABLE_HETEREOGENEOUS:SUPPORT: "no" changed to "yes"
OPAL_ENABLE_IPV6: "yes" changed to "no"
OPAL_ENABLE_MULTI_THREADS: "no" changed to "yes"
I also selected "Release" in "Visual Studio". Unfortunately I got the
following error ("void *" cannot be converted to "void **").
Fehler 77 error C2440: '=': 'void *' kann nicht in 'void **'
konvertiert werden
...\openmpi-1.6.1\ompi\mca\osc\rdma\osc_rdma_data_move.c
1099 1 libmpi
Fehler 90 error LNK1181: Eingabedatei "..\..\..\Release\libmpi.lib"
kann nicht geöffnet werden.
...\openmpi-1.6.1-Windows_VS2010_x32\ompi\tools\ompi-server\LINK
ompi-server
Fehler 94 error LNK1181: Eingabedatei "..\..\..\Release\libmpi.lib"
kann nicht geöffnet werden.
...\openmpi-1.6.1-Windows_VS2010_x32\ompi\tools\ompi_info\LINK
ompi_info
Fehler 162 error LNK1181: Eingabedatei "..\..\..\Release\libmpi.lib"
kann nicht geöffnet werden.
...\openmpi-1.6.1-Windows_VS2010_x32\ompi\mpi\cxx\LINK
libmpi_cxx
I get also a lot of warnings, from wich I have listed a few.
Warnung 1 warning C4005: 'PACKAGE_BUGREPORT': Makro-Neudefinition
...\openmpi-1.6.1\opal\event\win32-code\config.h
185 1 libopen-pal
Warnung 2 warning C4005: 'PACKAGE_NAME': Makro-Neudefinition
...\openmpi-1.6.1\opal\event\win32-code\config.h
188 1 libopen-pal
Warnung 3 warning C4005: 'PACKAGE_STRING': Makro-Neudefinition
...\openmpi-1.6.1\opal\event\win32-code\config.h
191 1 libopen-pal
Warnung 4 warning C4005: 'PACKAGE_TARNAME': Makro-Neudefinition
...\openmpi-1.6.1\opal\event\win32-code\config.h
194 1 libopen-pal
Warnung 5 warning C4005: 'PACKAGE_VERSION': Makro-Neudefinition
...\openmpi-1.6.1\opal\event\win32-code\config.h
197 1 libopen-pal
Warnung 6 warning C4005: '__func__': Makro-Neudefinition
...\openmpi-1.6.1\opal\event\win32-code\config.h
212 1 libopen-pal
Warnung 7 warning C4013: 'opal_event_warn' undefiniert;
Annahme: extern mit Rückgabetyp int
...\openmpi-1.6.1\opal\event\WIN32-Code\win32.c
170 1 libopen-pal
Warnung 8 warning C4005: 'INT8_MIN': Makro-Neudefinition
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\stdint.h
721 libopen-pal
Warnung 9 warning C4005: 'INT16_MIN': Makro-Neudefinition
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\stdint.h
731 libopen-pal
Warnung 10 warning C4005: 'INT32_MIN': Makro-Neudefinition
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\stdint.h
741 libopen-pal
Warnung 11 warning C4005: 'INT8_MAX': Makro-Neudefinition
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\stdint.h
761 libopen-pal
Warnung 12 warning C4005: 'INT16_MAX': Makro-Neudefinition
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\stdint.h
771 libopen-pal
Warnung 13 warning C4005: 'INT32_MAX': Makro-Neudefinition
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\stdint.h
781 libopen-pal
Warnung 14 warning C4005: 'UINT8_MAX': Makro-Neudefinition
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\stdint.h
791 libopen-pal
Warnung 15 warning C4005: 'UINT16_MAX': Makro-Neudefinition
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\stdint.h
801 libopen-pal
Warnung 16 warning C4005: 'UINT32_MAX': Makro-Neudefinition
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\stdint.h
811 libopen-pal
Warnung 17 warning C4018: '<': Konflikt zwischen 'signed' und 'unsigned'
...\openmpi-1.6.1-Windows_VS2010_x32\opal\keyval_lex.c
libopen-pal
Warnung 18 warning C4273: '_isatty': Inkonsistente DLL-Bindung.
...\openmpi-1.6.1-Windows_VS2010_x32\opal\keyval_lex.c
libopen-pal
...
What can I do to get around the error so that I can compile Open MPI?
Thank you very much for any suggestions in advance.
Kind regards
Siegmar
