[OMPI users] Windows CMake build problems ...

2010-01-12 Thread cjohnson 
The OpenMPI build problem I'm having occurs in both OpenMPI 1.4 and 1.3.4.I am on a Windows 7 (US) Enterprise (x86) OS on an HP system with Intel core 2 extreme x9000 (4GB RAM), using the 2005 Visual Studio for S/W Architects (release 8.0.50727.867). [That release has everything the platform SDK would have.]I'm using CMake 2.8 to generate code, I used it correctly, pointing at the root directory where the makelists are located for the source side and to an empty directory for the build side: did configure, click debug, configure again, generate and opened the OpenMPI.sln file created by CMake. Then I right-clicked on the "ALL_BUILD" project and selected "build".1 project built, 13 did not. I have the build listing. [I'm afraid of what the mailing list server would do if I attached it to this email.;The first error in the listing points to source line: C:\prog\openmpi-1.3.4\opal/class/opal_object.h(182),After that critical error, the compile falls apart due to it. Here's the section of the listing with the first error in the center:1>Generating Code...1>Compiling...1>signal.c1>select.c1>log.c1>evutil.c1>event.c1>win32.c1>c:\prog\openmpi-1.3.4\opal\event\win32-code\./config.h(185) : warning C4005: 'PACKAGE_BUGREPORT' : macro redefinition1>    c:\prog\mon\opal\include\opal_config.h(1307) : see previous definition of 'PACKAGE_BUGREPORT'1>c:\prog\openmpi-1.3.4\opal\event\win32-code\./config.h(188) : warning C4005: 'PACKAGE_NAME' : macro redefinition1>    c:\prog\mon\opal\include\opal_config.h(1310) : see previous definition of 'PACKAGE_NAME'1>c:\prog\openmpi-1.3.4\opal\event\win32-code\./config.h(191) : warning C4005: 'PACKAGE_STRING' : macro redefinition1>    c:\prog\mon\opal\include\opal_config.h(1313) : see previous definition of 'PACKAGE_STRING'1>c:\prog\openmpi-1.3.4\opal\event\win32-code\./config.h(194) : warning C4005: 'PACKAGE_TARNAME' : macro redefinition1>    c:\prog\mon\opal\include\opal_config.h(1316) : see previous definition of 'PACKAGE_TARNAME'1>c:\prog\openmpi-1.3.4\opal\event\win32-code\./config.h(197) : warning C4005: 'PACKAGE_VERSION' : macro redefinition1>    c:\prog\mon\opal\include\opal_config.h(1319) : see previous definition of 'PACKAGE_VERSION'1>c:\prog\openmpi-1.3.4\opal\event\win32-code\./config.h(212) : warning C4005: '__func__' : macro redefinition1>    C:\prog\openmpi-1.3.4\opal\include\opal_config_bottom.h(449) : see previous definition of '__func__'** First error in build listing, below:1>C:\prog\openmpi-1.3.4\opal/class/opal_object.h(182) : error C2016: C requires that a struct or union has at least one member1>C:\prog\openmpi-1.3.4\opal/class/opal_object.h(182) : error C2061: syntax error : identifier '__uint64_t'1>C:\prog\openmpi-1.3.4\opal/class/opal_object.h(190) : error C2059: syntax error : '}'1>C:\prog\openmpi-1.3.4\opal/class/opal_object.h(248) : error C2037: left of 'obj_magic_id' specifies undefined struct/union 'opal_object_t'1>C:\prog\openmpi-1.3.4\opal/class/opal_object.h(249) : error C2037: left of 'cls_init_file_name' specifies undefined struct/union 'opal_object_t'1>C:\prog\openmpi-1.3.4\opal/class/opal_object.h(250) : error C2037: left of 'cls_init_lineno' specifies undefined struct/union 'opal_object_t'1>C:\prog\openmpi-1.3.4\opal/class/opal_object.h(421) : error C2037: left of 'obj_class' specifies undefined struct/union 'opal_object_t'1>C:\prog\openmpi-1.3.4\opal/class/opal_object.h(423) : error C2037: left of 'obj_class' specifies undefined struct/union 'opal_object_t'1>C:\prog\openmpi-1.3.4\opal/class/opal_object.h(443) : error C2037: left of 'obj_class' specifies undefined struct/union 'opal_object_t'1>C:\prog\openmpi-1.3.4\opal/class/opal_object.h(445) : error C2037: left of 'obj_class' specifies undefined struct/union 'opal_object_t'1>C:\prog\openmpi-1.3.4\opal/class/opal_object.h(466) : error C2027: use of undefined type 'opal_object_t'1>    C:\prog\openmpi-1.3.4\opal/class/opal_object.h(178) : see declaration of 'opal_object_t'1>C:\prog\openmpi-1.3.4\opal/class/opal_object.h(473) : error C2037: left of 'obj_class' specifies undefined struct/union 'opal_object_t'1>C:\prog\openmpi-1.3.4\opal/class/opal_object.h(474) : error C2037: left of 'obj_reference_count' specifies undefined struct/union 'opal_object_t'1>C:\prog\openmpi-1.3.4\opal/class/opal_object.h(497) : error C2037: left of 'obj_reference_count' specifies undefined struct/union 'opal_object_t'1>C:\prog\openmpi-1.3.4\opal/class/opal_object.h(498) : error C2037: left of 'obj_reference_count' specifies undefined struct/union 'opal_object_t'1>C:\prog\openmpi-1.3.4\opal/class/opal_object.h(498) : warning C4033: 'opal_obj_update' must return a value1>C:\prog\openmpi-1.3.4\opal/util/output.h(99) : error C2079: 'super' uses undefined struct 'opal_object_t'Here's the source file section with the error line indicated:---> Opal_object.h (lines 173-190)/** * For static initializations of OBJects. * * @param NAME   Name of the class to initialize */#if

[OMPI users] Windows CMake build problems ... (cont.)

2010-01-14 Thread cjohnson 
The OpenMPI build problem I'm having occurs in both OpenMPI 1.4 and 1.3.4.I am on a Windows 7 (US) Enterprise (x86) OS on an HP system with Intel core 2 extreme x9000 (4GB RAM), using the 2005 Visual Studio for S/W Architects (release 8.0.50727.867).[That release has everything the platform SDK would have.]I'm using CMake 2.8 to generate code, I used it correctly, pointing at the root directory where the makelists are located for the source side and to an empty directory for the build side: did configure, I did not click debug this time as suggested by Shiqing, configure again, generate and opened the OpenMPI.sln file created by CMake. Then I right-clicked on the "ALL_BUILD" project and selected "build". Then did one "rebuild", just in case build order might get one more success (which it seemed to, but I could not find).2 projects built, 12 did not. I have the build listing. [I'm afraid of what the mailing list server would do if I attached it to this email.]All the compiles were successful (warnings at most.) All the errors were were from linking the VC projects:1>libopen-pal - 0 error(s), 9 warning(s)3>opal-restart - 32 error(s), 0 warning(s)4>opal-wrapper - 21 error(s), 0 warning(s)2>libopen-rte - 749 error(s), 7 warning(s)5>orte-checkpoint - 32 error(s), 0 warning(s)7>orte-ps - 28 error(s), 0 warning(s)8>orted - 2 error(s), 0 warning(s)9>orte-clean - 13 error(s), 0 warning(s)10>orterun - 100 error(s), 3 warning(s)6>libmpi - 2133 error(s), 42 warning(s)12>ompi-server - 27 error(s), 0 warning(s)11>ompi_info - 146 error(s), 0 warning(s)13>libmpi_cxx - 456 error(s), 61 warning(s)== Rebuild All: 2 succeeded, 12 failed, 0 skipped ==It said that 2 succeeded, I could not find the second build success in the listing.However, everything did compile, and thank you Shiqing !Here is the listing for the first failed link, on "opal-restart":3>-- Rebuild All started: Project: opal-restart, Configuration: Debug Win32 --3>Deleting intermediate and output files for project 'opal-restart', configuration 'Debug|Win32'3>Compiling...3>opal-restart.c2>Compiling...2>snapc_base_select.c3>Compiling manifest to resources...3>Linking...2>snapc_base_open.c3>opal-restart.obj : error LNK2001: unresolved external symbol __imp__opal_crs3>opal-restart.obj : error LNK2001: unresolved external symbol __imp__opal_crs_base_snapshot_t_class3>opal-restart.obj : error LNK2001: unresolved external symbol __imp__opal_crs_base_selected_component3>opal-restart.obj : error LNK2019: unresolved external symbol __imp__opal_crs_base_select referenced in function _main3>opal-restart.obj : error LNK2019: unresolved external symbol __imp__opal_crs_base_open referenced in function _main3>opal-restart.obj : error LNK2019: unresolved external symbol __imp__opal_output_verbose referenced in function _main3>opal-restart.obj : error LNK2019: unresolved external symbol __imp__opal_crs_base_extract_expected_component referenced in function _main3>opal-restart.obj : error LNK2019: unresolved external symbol __imp__opal_crs_base_get_snapshot_directory referenced in function _main3>opal-restart.obj : error LNK2019: unresolved external symbol __imp__opal_setenv referenced in function _main3>opal-restart.obj : error LNK2019: unresolved external symbol __imp__mca_base_param_env_var referenced in function _main3>opal-restart.obj : error LNK2019: unresolved external symbol __imp__opal_show_help referenced in function _main3>opal-restart.obj : error LNK2019: unresolved external symbol __imp__opal_class_initialize referenced in function "struct opal_object_t * __cdecl opal_obj_new(struct opal_class_t *)" (?opal_obj_new@@YAPAUopal_object_t@@PAUopal_class_t@@@Z)3>opal-restart.obj : error LNK2001: unresolved external symbol __imp__opal_cr_is_tool3>opal-restart.obj : error LNK2019: unresolved external symbol __imp__opal_init referenced in function "int __cdecl initialize(int,char * * const)" (?initialize@@YAHHQAPAD@Z)3>opal-restart.obj : error LNK2019: unresolved external symbol __imp__opal_output_set_verbosity referenced in function "int __cdecl initialize(int,char * * const)" (?initialize@@YAHHQAPAD@Z)3>opal-restart.obj : error LNK2019: unresolved external symbol __imp__opal_output_open referenced in function "int __cdecl initialize(int,char * * const)" (?initialize@@YAHHQAPAD@Z)3>opal-restart.obj : error LNK2019: unresolved external symbol __imp__opal_init_util referenced in function "int __cdecl initialize(int,char * * const)" (?initialize@@YAHHQAPAD@Z)3>opal-restart.obj : error LNK2019: unresolved external symbol __imp__opal_finalize referenced in function "int __cdecl finalize(void)" (?finalize@@YAHXZ)3>opal-restart.obj : error LNK2019: unresolved external symbol __imp__opal_argv_join referenced in function "int __cdecl parse_args(int,char * * const)" (?parse_args@@YAHHQAPAD@Z)3>opal-restart.obj : error LNK2019: unresolved external symbol __imp__opal_cmd_line_get_tail referenced in function "int __cdecl parse_args(int,char * * const)" (?parse_arg

Re: [OMPI users] Windows CMake build problems ... (cont.)

2010-01-15 Thread cjohnson 
Yes that was it.A much improved result now from CMake 2.6.4, no errors from compiling openmpi-1.4:1>libopen-pal - 0 error(s), 9 warning(s)2>libopen-rte - 0 error(s), 7 warning(s)3>opal-restart - 0 error(s), 0 warning(s)4>opal-wrapper - 0 error(s), 0 warning(s)5>libmpi - 0 error(s), 42 warning(s)6>orte-checkpoint - 0 error(s), 0 warning(s)7>orte-ps - 0 error(s), 0 warning(s)8>orted - 0 error(s), 0 warning(s)9>orte-clean - 0 error(s), 0 warning(s)10>orterun - 0 error(s), 3 warning(s)11>ompi_info - 0 error(s), 0 warning(s)12>ompi-server - 0 error(s), 0 warning(s)13>libmpi_cxx - 0 error(s), 61 warning(s)== Build: 13 succeeded, 0 failed, 1 up-to-date, 0 skipped ==And only one failure from compiling openmpi-1.3.4 (the ompi_info project):> 1>libopen-pal - 0 error(s), 9 warning(s)> 2>libopen-rte - 0 error(s), 7 warning(s)> 3>opal-restart - 0 error(s), 0 warning(s)> 4>opal-wrapper - 0 error(s), 0 warning(s)> 5>orte-checkpoint - 0 error(s), 0 warning(s)> 6>libmpi - 0 error(s), 42 warning(s)> 7>orte-ps - 0 error(s), 0 warning(s)> 8>orted - 0 error(s), 0 warning(s)> 9>orte-clean - 0 error(s), 0 warning(s)> 10>orterun - 0 error(s), 3 warning(s)> 11>ompi_info - 3 error(s), 0 warning(s)> 12>ompi-server - 0 error(s), 0 warning(s)> 13>libmpi_cxx - 0 error(s), 61 warning(s)> == Rebuild All: 13 succeeded, 1 failed, 0 skipped ==Here's the listing from the non-linking project:11>-- Rebuild All started: Project: ompi_info, Configuration: Debug Win32 --11>Deleting intermediate and output files for project 'ompi_info', configuration 'Debug|Win32'11>Compiling...11>version.cc11>..\..\..\..\openmpi-1.3.4\ompi\tools\ompi_info\version.cc(136) : error C2059: syntax error : ','11>..\..\..\..\openmpi-1.3.4\ompi\tools\ompi_info\version.cc(147) : error C2059: syntax error : ','11>..\..\..\..\openmpi-1.3.4\ompi\tools\ompi_info\version.cc(158) : error C2059: syntax error : ','11>param.cc11>output.cc11>ompi_info.cc11>components.cc11>Generating Code...11>Build log was saved at "file://c:\prog\mon\ompi\tools\ompi_info\ompi_info.dir\Debug\BuildLog.htm"11>ompi_info - 3 error(s), 0 warning(s)Thank you Shiqing !Charlie ...


 Original Message 
Subject: Re: [OMPI users] Windows CMake build problems ... (cont.)
From: Shiqing Fan 
List-Post: users@lists.open-mpi.org
Date: Thu, January 14, 2010 11:20 am
To: Open MPI Users , cjohn...@valverdecomputing.com


Hi Charlie,

The problem turns out to be the different behavior of one CMake macro in 
different version of CMake. And it's fixed in Open MPI trunk with 
r22405. I also created a ticket to move the fix over to 1.4 branch, see 
#2169: https://svn.open-mpi.org/trac/ompi/ticket/2169 .

So you could either switch to use OMPI trunk or use CMake 2.6 to solve 
the problem. Thanks a lot.


Best Regards,
Shiqing


cjohn...@valverdecomputing.com wrote:
> The OpenMPI build problem I'm having occurs in both OpenMPI 1.4 and 1.3.4.
>
> I am on a Windows 7 (US) Enterprise (x86) OS on an HP system with 
> Intel core 2 extreme x9000 (4GB RAM), using the 2005 Visual Studio for 
> S/W Architects (release 8.0.50727.867).
>
> [That release has everything the platform SDK would have.]
>
> I'm using CMake 2.8 to generate code, I used it correctly, pointing at 
> the root directory where the makelists are located for the source side 
> and to an empty directory for the build side: did configure, _*I did 
> not click debug this time as suggested by Shiqing*_, configure again, 
> generate and opened the OpenMPI.sln file created by CMake. Then I 
> right-clicked on the "ALL_BUILD" project and selected "build". Then 
> did one "rebuild", just in case build order might get one more success 
> (which it seemed to, but I could not find).
>
> 2 projects built, 12 did not. I have the build listing. [I'm afraid of 
> what the mailing list server would do if I attached it to this email.]
>
> All the compiles were successful (warnings at most.) All the errors 
> were were from linking the VC projects:
>
> *1>libopen-pal - 0 error(s), 9 warning(s)*
> 3>opal-restart - 32 error(s), 0 warning(s)
> 4>opal-wrapper - 21 error(s), 0 warning(s)
> 2>libopen-rte - 749 error(s), 7 warning(s)
> 5>orte-checkpoint - 32 error(s), 0 warning(s)
> 7>orte-ps - 28 error(s), 0 warning(s)
> 8>orted - 2 error(s), 0 warning(s)
> 9>orte-clean - 13 error(s), 0 warning(s)
> 10>orterun - 100 error(s), 3 warning(s)
> 6>libmpi - 2133 error(s), 42 warning(s)
> 12>ompi-server - 27 error(s), 0 warning(s)
> 11>ompi_info - 146 error(s), 0 warning(s)
> 13>libmpi_cxx - 456 error(s), 61 warning(s)
> == Rebuild All: 2 succeeded, 12 failed, 0 skipped ==
>
> It said that 2 succeeded, I could not find the second build success in 
> the listing.
>
> *However, everything did compile, and thank you Shiqing !*
>
> Here is the listing for the first failed link, on "opal-restart":
>
> 3>-- Rebuild All started: Project: opal-restart, Configuration: 
> Debug Win32 --
> 3>Deleting intermediate and output fil

Re: [OMPI users] Windows CMake build problems ... (cont.)

2010-01-25 Thread cjohnson 
OK, so I'm a little farther on and perplexed.
 
As I said, Visual C++ 2005 (release 8.0.50727.867) build of OpenMPI 1.4, using CMake 2.6.4, built everything and it all linked.
 
Went ahead and built the PACKAGE item in the OpenMPI.sln project, which made a zip file and an installer (although it was not obvious where to look for this , what its name was, etc., I figured it out by dates on files).
 
Another thing that''s not obvious, is how to shoehorn your code into a VCC project that will successfully build.
 
I created a project from existing files in a place where the include on the mpi.h would be found and examples, etc. did compile.
 
However, they did not find any of the library routines. Link errors.
 
So, I added in the generated libraries location into the search locations for libraries.
 
No good.
 
So, I added all of the generated libraries into the VCC project I created.
 
No good.
 
How does one do this (aside from rigging up something through CMake, cygwin, minGW, or MS SFU)?
 
Charlie ...
 

 Original Message Subject: Re: [OMPI users] Windows CMake build problems ... (cont.)From: Shiqing Fan Date: Fri, January 15, 2010 2:56 amTo: cjohn...@valverdecomputing.comCc: Open MPI Users Hi Charlie,Glad to hear that you compiled it successfully.The error you got with 1.3.4 is a bug that the CMake script didn't set the SVN information correctly, and it has been fixed in 1.4 and later.Thanks,Shiqingcjohn...@valverdecomputing.com wrote:> Yes that was it.>> A much improved result now from CMake 2.6.4, no errors from compiling > openmpi-1.4:>> 1>libopen-pal - 0 error(s), 9 warning(s)> 2>libopen-rte - 0 error(s), 7 warning(s)> 3>opal-restart - 0 error(s), 0 warning(s)> 4>opal-wrapper - 0 error(s), 0 warning(s)> 5>libmpi - 0 error(s), 42 warning(s)> 6>orte-checkpoint - 0 error(s), 0 warning(s)> 7>orte-ps - 0 error(s), 0 warning(s)> 8>orted - 0 error(s), 0 warning(s)> 9>orte-clean - 0 error(s), 0 warning(s)> 10>orterun - 0 error(s), 3 warning(s)> 11>ompi_info - 0 error(s), 0 warning(s)> 12>ompi-server - 0 error(s), 0 warning(s)> 13>libmpi_cxx - 0 error(s), 61 warning(s)> == Build: 13 succeeded, 0 failed, 1 up-to-date, 0 skipped > ==>> And only one failure from compiling openmpi-1.3.4 (the ompi_info project):>> > 1>libopen-pal - 0 error(s), 9 warning(s)> > 2>libopen-rte - 0 error(s), 7 warning(s)> > 3>opal-restart - 0 error(s), 0 warning(s)> > 4>opal-wrapper - 0 error(s), 0 warning(s)> > 5>orte-checkpoint - 0 error(s), 0 warning(s)> > 6>libmpi - 0 error(s), 42 warning(s)> > 7>orte-ps - 0 error(s), 0 warning(s)> > 8>orted - 0 error(s), 0 warning(s)> > 9>orte-clean - 0 error(s), 0 warning(s)> > 10>orterun - 0 error(s), 3 warning(s)> > 11>ompi_info - 3 error(s), 0 warning(s)> > 12>ompi-server - 0 error(s), 0 warning(s)> > 13>libmpi_cxx - 0 error(s), 61 warning(s)> > == Rebuild All: 13 succeeded, 1 failed, 0 skipped ==>> Here's the listing from the non-linking project:>> 11>-- Rebuild All started: Project: ompi_info, Configuration: > Debug Win32 --> 11>Deleting intermediate and output files for project 'ompi_info', > configuration 'Debug|Win32'> 11>Compiling...> 11>version.cc> 11>..\..\..\..\openmpi-1.3.4\ompi\tools\ompi_info\version.cc(136) : > error C2059: syntax error : ','> 11>..\..\..\..\openmpi-1.3.4\ompi\tools\ompi_info\version.cc(147) : > error C2059: syntax error : ','> 11>..\..\..\..\openmpi-1.3.4\ompi\tools\ompi_info\version.cc(158) : > error C2059: syntax error : ','> 11>param.cc> 11>output.cc> 11>ompi_info.cc> 11>components.cc> 11>Generating Code...> 11>Build log was saved at > "file://c:\prog\mon\ompi\tools\ompi_info\ompi_info.dir\Debug\BuildLog.htm"> 11>ompi_info - 3 error(s), 0 warning(s)>> Thank you Shiqing !>> Charlie ...>>  Original Message > Subject: Re: [OMPI users] Windows CMake build problems ... (cont.)> From: Shiqing Fan > Date: Thu, January 14, 2010 11:20 am> To: Open MPI Users ,> cjohn...@valverdecomputing.com>>> Hi Charlie,>> The problem turns out to be the different behavior of one CMake> macro in> different version of CMake. And it's fixed in Open MPI trunk with> r22405. I also created a ticket to move the fix over to 1.4> branch, see> #2169: https://svn.open-mpi.org/trac/ompi/ticket/2169 .>> So you could either switch to use OMPI trunk or use CMake 2.6 to> solve> the problem. Thanks a lot.>>> Best Regards,> Shiqing>>> cjohn...@valverdecomputing.com wrote:> > The OpenMPI build problem I'm having occurs in both OpenMPI 1.4> and 1.3.4.> >> > I am on a Windows 7 (US) Enterprise (x86) OS on an HP system with> > Intel core 2 extreme x9000 (4GB RAM), using the 2005 Visual> Studio for> > S/W Architects (release 8.0.50727.867).> >> > [That release has everything the platform SDK would have.]> >> > I'm using CMake 2.8 to generate code, I used it correctly,> pointing at> > the root directory where the makelists are located for the source> side> > and to an empty directory for the build side: did configure, _*I did> > not cli

Re: [OMPI users] Windows CMake build problems ... (cont.)

2010-01-25 Thread cjohnson 
Thanks, that second part about the wrappers was what I was looking for.
 
Charlie ... 
 

 Original Message Subject: Re: [OMPI users] Windows CMake build problems ... (cont.)From: Shiqing Fan Date: Mon, January 25, 2010 2:09 amTo: cjohn...@valverdecomputing.comCc: Open MPI Users Hi Charlie,Actually, to compile and link your application with Open MPI on Windows is similar as on Linux. You have to link your application against the generated Open MPI libraries, e.g. libopen-mpi.lib (don't forget the suffix 'd' if you build debug version of the OMPI libraries, e.g. libopen-mpid.lib).But according to the information you provided, I assume that you only added the search path into the project, that's not enough, you should probably add the library names into "Project Property Pages" -> "Configuration Properties" -> Linker -> Input -> "Additional Dependencies", normally only libopen-mpi.lib (or libopen-mpid.lib) would be enough, so that Visual Studio will know which libraries to link to.Besides, the Open MPI compiler wrappers should also work on Windows, in this case you just need to open a "Visual Studio command prompt" with the Open MPI path env added (e.g. "set PATH=c:\Program Files\OpenMPI_v1.4\bin;%PATH%"), and simply run command like:> mpicc app.cand> mpirun -np 2 app.exePlease note that, before executing the application, Open MPI has to be installed somewhere either by build the "INSTALL" project or by running the generated installer, so that the correct Open MPI folder structure could be created.Regards,Shiqingcjohn...@valverdecomputing.com wrote:> OK, so I'm a little farther on and perplexed.> > As I said, Visual C++ 2005 (release 8.0.50727.867) build > of OpenMPI 1.4, using CMake 2.6.4, built everything and it all linked.> > Went ahead and built the PACKAGE item in the OpenMPI.sln project, > which made a zip file and an installer (although it was not obvious > where to look for this , what its name was, etc., I figured it out by > dates on files).> > Another thing that''s not obvious, is how to shoehorn your code into a > VCC project that will successfully build.> > I created a project from existing files in a place where the include > on the mpi.h would be found and examples, etc. did compile.> > However, they did not find any of the library routines. Link errors.> > So, I added in the generated libraries location into the search > locations for libraries.> > No good.> > So, I added all of the generated libraries into the VCC project I created.> > No good.> > How does one do this (aside from rigging up something through CMake, > cygwin, minGW, or MS SFU)?> > Charlie ...> >>  Original Message > Subject: Re: [OMPI users] Windows CMake build problems ... (cont.)> From: Shiqing Fan > Date: Fri, January 15, 2010 2:56 am> To: cjohn...@valverdecomputing.com> Cc: Open MPI Users >>> Hi Charlie,>> Glad to hear that you compiled it successfully.>> The error you got with 1.3.4 is a bug that the CMake script didn't> set> the SVN information correctly, and it has been fixed in 1.4 and later.>>> Thanks,> Shiqing>>> cjohn...@valverdecomputing.com wrote:> > Yes that was it.> >> > A much improved result now from CMake 2.6.4, no errors from> compiling> > openmpi-1.4:> >> > 1>libopen-pal - 0 error(s), 9 warning(s)> > 2>libopen-rte - 0 error(s), 7 warning(s)> > 3>opal-restart - 0 error(s), 0 warning(s)> > 4>opal-wrapper - 0 error(s), 0 warning(s)> > 5>libmpi - 0 error(s), 42 warning(s)> > 6>orte-checkpoint - 0 error(s), 0 warning(s)> > 7>orte-ps - 0 error(s), 0 warning(s)> > 8>orted - 0 error(s), 0 warning(s)> > 9>orte-clean - 0 error(s), 0 warning(s)> > 10>orterun - 0 error(s), 3 warning(s)> > 11>ompi_info - 0 error(s), 0 warning(s)> > 12>ompi-server - 0 error(s), 0 warning(s)> > 13>libmpi_cxx - 0 error(s), 61 warning(s)> > == Build: 13 succeeded, 0 failed, 1 up-to-date, 0 skipped> > ==> >> > And only one failure from compiling openmpi-1.3.4 (the ompi_info> project):> >> > > 1>libopen-pal - 0 error(s), 9 warning(s)> > > 2>libopen-rte - 0 error(s), 7 warning(s)> > > 3>opal-restart - 0 error(s), 0 warning(s)> > > 4>opal-wrapper - 0 error(s), 0 warning(s)> > > 5>orte-checkpoint - 0 error(s), 0 warning(s)> > > 6>libmpi - 0 error(s), 42 warning(s)> > > 7>orte-ps - 0 error(s), 0 warning(s)> > > 8>orted - 0 error(s), 0 warning(s)> > > 9>orte-clean - 0 error(s), 0 warning(s)> > > 10>orterun - 0 error(s), 3 warning(s)> > > 11>ompi_info - 3 error(s), 0 warning(s)> > > 12>ompi-server - 0 error(s), 0 warning(s)> > > 13>libmpi_cxx - 0 error(s), 61 warning(s)> > > == Rebuild All: 13 succeeded, 1 failed, 0 skipped> ==> >> > Here's the listing from the non-linking project:> >> > 11>-- Rebuild All started: Project: ompi_info, Configuration:> > Debug Win32 --> > 11>Deleting intermediate and output files for project 'ompi_info',> > configuration 'Debug|Win32'> > 11>Compiling...> > 11>version.cc> > 11>..\..\..\..\openmpi-1.3.4\ompi\tools\ompi_info\version.cc(136) :> > err

[OMPI users] Windows CMake build problems ...

2010-01-26 Thread cjohnson 
The mpicc, mpic++ and mpicxx apparently don't work, even though the rest of the wrapper commands do:C:\prog\mon\examples>ompi_info Package: Open MPI Charles Johnson@WORK Distribution    Open MPI: 1.4   Open MPI SVN revision: r22285   Open MPI release date: Dec 08, 2009    Open RTE: 1.4   Open RTE SVN revision: r22285   Open RTE release date: Dec 08, 2009    OPAL: 1.4   OPAL SVN revision: r22285   OPAL release date: Dec 08, 2009    Ident string: 1.4  Prefix: C:\Program Files\OpenMPI_v1.4-win32 Configured architecture: x86 Windows-6.1  Configure host: WORK   Configured by: Charles Johnson   Configured on: 02:27 AM Sun 01/24/2010  Configure host: WORK    Built by: Charles Johnson    Built on: 02:27 AM Sun 01/24/2010  Built host: WORK  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: cl   C++ compiler absolute: cl  Fortran77 compiler: CMAKE_Fortran_COMPILER-NOTFOUND  Fortran77 compiler abs: none  Fortran90 compiler:  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 parameter check: runtimeMemory profiling support: noMemory debugging support: no libltdl support: no   Heterogeneous support: no mpirun default --prefix: yes MPI I/O support: yes   MPI_WTIME support: gettimeofdaySymbol visibility support: yes   FT Checkpoint support: yes  (checkpoint thread: no)   MCA backtrace: none (MCA v2.0, API v2.0, Component v1.4)   MCA paffinity: windows (MCA v2.0, API v2.0, Component v1.4)   MCA carto: auto_detect (MCA v2.0, API v2.0, Component v1.4)   MCA maffinity: first_use (MCA v2.0, API v2.0, Component v1.4)   MCA timer: windows (MCA v2.0, API v2.0, Component v1.4) MCA installdirs: windows (MCA v2.0, API v2.0, Component v1.4) MCA installdirs: env (MCA v2.0, API v2.0, Component v1.4) MCA installdirs: config (MCA v2.0, API v2.0, Component v1.4) MCA crs: none (MCA v2.0, API v2.0, Component v1.4) MCA dpm: orte (MCA v2.0, API v2.0, Component v1.4)  MCA pubsub: orte (MCA v2.0, API v2.0, Component v1.4)   MCA allocator: basic (MCA v2.0, API v2.0, Component v1.4)   MCA allocator: bucket (MCA v2.0, API v2.0, Component v1.4)    MCA coll: basic (MCA v2.0, API v2.0, Component v1.4)    MCA coll: hierarch (MCA v2.0, API v2.0, Component v1.4)    MCA coll: self (MCA v2.0, API v2.0, Component v1.4)    MCA coll: sm (MCA v2.0, API v2.0, Component v1.4)    MCA coll: sync (MCA v2.0, API v2.0, Component v1.4)   MCA mpool: rdma (MCA v2.0, API v2.0, Component v1.4)   MCA mpool: sm (MCA v2.0, API v2.0, Component v1.4) MCA pml: ob1 (MCA v2.0, API v2.0, Component v1.4) MCA bml: r2 (MCA v2.0, API v2.0, Component v1.4) MCA btl: self (MCA v2.0, API v2.0, Component v1.4) MCA btl: sm (MCA v2.0, API v2.0, Component v1.4) MCA btl: tcp (MCA v2.0, API v2.0, Component v1.4)    MCA topo: unity (MCA v2.0, API v2.0, Component v1.4) MCA osc: pt2pt (MCA v2.0, API v2.0, Component v1.4) MCA osc: rdma (MCA v2.0, API v2.0, Component v1.4) MCA iof: hnp (MCA v2.0, API v2.0, Component v1.4) MCA iof: orted (MCA v2.0, API v2.0, Component v1.4) MCA iof: tool (MCA v2.0, API v2.0, Component v1.4) MCA oob: tcp (MCA v2.0, API v2.0, Component v1.4)    MCA odls: process (MCA v2.0, API v2.0, Component v1.4)   MCA rmaps: round_robin (MCA v2.0, API v2.0, Component v1.4)   MCA rmaps: seq (MCA v2.0, API v2.0, Component v1.4) MCA rml: ftrm (MCA v2.0, API v2.0, Component v1.4) MCA rml: oob (MCA v2.0, API v2.0, Component v1.4)  MCA routed: binomial (MCA v2.0, API v2.0, Component v1.4)  MCA routed: linear (MCA v2.0, API v2.0, Component v1.4) MCA plm: process (MCA v2.0, API v2.0, Component v1.4)  MCA errmgr: default (MCA v2.0, API v2.0, Component v1.4) MCA ess: env (MCA v2.0, API v2.0, Component v1.4) MCA ess: hnp (MCA v2.0, API v2.0, Component v1.4) MCA ess: singleton (MCA v2.0, API v2.0, Component v1.4) MCA grpcomm: basic (MCA v2.0, API v2.0, Component v1.4)C:\prog\mon\examples>mpirun --helpmpirun (Open MPI) 1.4Usage: mpirun [OPTION]...  [PROGRAM]...St

Re: [OMPI users] Windows CMake build problems ... (cont.)

2010-01-26 Thread cjohnson 
Oh, and here's the directory that was built from the OpenMPI build:C:\Program Files\OpenMPI_v1.4-win32\bin>dir Volume in drive C is Work Volume Serial Number is 6A2D-3CBC Directory of C:\Program Files\OpenMPI_v1.4-win32\bin01/24/2010  05:14 AM      .01/24/2010  05:14 AM      ..01/24/2010  02:39 AM 2,637,824 libmpid.dll01/24/2010  02:39 AM    11,268,096 libmpid.pdb01/24/2010  02:39 AM   139,264 libmpi_cxxd.dll01/24/2010  02:39 AM   962,560 libmpi_cxxd.pdb01/24/2010  02:29 AM   458,752 libopen-pald.dll01/24/2010  02:29 AM 1,953,792 libopen-pald.pdb01/24/2010  02:30 AM   860,160 libopen-rted.dll01/24/2010  02:30 AM 2,936,832 libopen-rted.pdb07/11/2009  07:10 PM 1,870 Microsoft.VC80.CRT.manifest01/24/2010  02:29 AM    44,544 mpic++.exe01/24/2010  02:29 AM    44,544 mpicc.exe01/24/2010  02:29 AM    44,544 mpicxx.exe01/24/2010  02:29 AM    44,544 mpiexec.exe01/24/2010  02:30 AM    98,304 mpirun.exe07/12/2009  01:55 AM   479,232 msvcm80.dll07/12/2009  01:55 AM   554,832 msvcp80.dll07/12/2009  01:55 AM   632,656 msvcr80.dll01/24/2010  02:30 AM    38,912 ompi-checkpoint.exe01/24/2010  02:30 AM    31,744 ompi-clean.exe01/24/2010  02:30 AM    48,640 ompi-ps.exe01/24/2010  02:39 AM    34,304 ompi-server.exe01/24/2010  02:39 AM   229,376 ompi_info.exe01/24/2010  02:29 AM    37,888 opal-restart.exe01/24/2010  02:29 AM    44,544 opal-wrapper.exe01/24/2010  02:30 AM    38,912 orte-checkpoint.exe01/24/2010  02:30 AM    31,744 orte-clean.exe01/24/2010  02:30 AM    48,640 orte-ps.exe01/24/2010  02:30 AM    29,184 orted.exe01/24/2010  02:30 AM    98,304 orterun.exe  29 File(s) 23,874,542 bytes   2 Dir(s)  135,862,136,832 bytes free


 Original Message 
Subject: [OMPI users] Windows CMake build problems ...
From: cjohn...@valverdecomputing.com
List-Post: users@lists.open-mpi.org
Date: Tue, January 26, 2010 1:43 am
To: f...@hlrs.de
Cc: "Open MPI Users" 

The mpicc, mpic++ and mpicxx apparently don't work, even though the rest of the wrapper commands do:C:\prog\mon\examples>ompi_info Package: Open MPI Charles Johnson@WORK Distribution    Open MPI: 1.4   Open MPI SVN revision: r22285   Open MPI release date: Dec 08, 2009    Open RTE: 1.4   Open RTE SVN revision: r22285   Open RTE release date: Dec 08, 2009    OPAL: 1.4   OPAL SVN revision: r22285   OPAL release date: Dec 08, 2009    Ident string: 1.4  Prefix: C:\Program Files\OpenMPI_v1.4-win32 Configured architecture: x86 Windows-6.1  Configure host: WORK   Configured by: Charles Johnson   Configured on: 02:27 AM Sun 01/24/2010  Configure host: WORK    Built by: Charles Johnson    Built on: 02:27 AM Sun 01/24/2010  Built host: WORK  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: cl   C++ compiler absolute: cl  Fortran77 compiler: CMAKE_Fortran_COMPILER-NOTFOUND  Fortran77 compiler abs: none  Fortran90 compiler:  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 parameter check: runtimeMemory profiling support: noMemory debugging support: no libltdl support: no   Heterogeneous support: no mpirun default --prefix: yes MPI I/O support: yes   MPI_WTIME support: gettimeofdaySymbol visibility support: yes   FT Checkpoint support: yes  (checkpoint thread: no)   MCA backtrace: none (MCA v2.0, API v2.0, Component v1.4)   MCA paffinity: windows (MCA v2.0, API v2.0, Component v1.4)   MCA carto: auto_detect (MCA v2.0, API v2.0, Component v1.4)   MCA maffinity: first_use (MCA v2.0, API v2.0, Component v1.4)   MCA timer: windows (MCA v2.0, API v2.0, Component v1.4) MCA installdirs: windows (MCA v2.0, API v2.0, Component v1.4) MCA installdirs: env (MCA v2.0, API v2.0, Component v1.4) MCA installdirs: config (MCA v2.0, API v2.0, Component v1.4) MCA crs: none (MCA v2.0, API v2.0, Component v1.4) MCA dpm: orte (MCA v2.0, API v2.0, Component v1.4)  MCA pubsub: orte (MCA v2.0, API v2.0, Component v1.4)   MCA allocator: basic (MCA v2.0, API v2.0, Component v1.4)   MCA allocator: bucket (MCA v2.0, API v2.0, Component v1.4)    MCA coll: basic (MCA v2.0, API v2.0, Component v1.4)    MCA coll: hierarch

Re: [OMPI users] Windows CMake build problems ...

2010-01-26 Thread cjohnson 
Yeah, that was it. Thanks.Charlie ...


 Original Message 
Subject: Re: [OMPI users] Windows CMake build problems ...
From: Shiqing Fan 
List-Post: users@lists.open-mpi.org
Date: Tue, January 26, 2010 1:57 am
To: cjohn...@valverdecomputing.com
Cc: Open MPI Users 


Hi Charlie ,

Did you run the mpicc command in the Visual Studio Command Prompt? Is it 
possible for you to call cl.exe from there? Because it sounds like the 
VS compiler was not found.


Regards,
Shiqing


cjohn...@valverdecomputing.com wrote:
> The mpicc, mpic++ and mpicxx apparently don't work, even though the 
> rest of the wrapper commands do:
>
>
> C:\prog\mon\examples>ompi_info
>  Package: Open MPI Charles Johnson@WORK Distribution
> Open MPI: 1.4
>Open MPI SVN revision: r22285
>Open MPI release date: Dec 08, 2009
> Open RTE: 1.4
>Open RTE SVN revision: r22285
>Open RTE release date: Dec 08, 2009
> OPAL: 1.4
>OPAL SVN revision: r22285
>OPAL release date: Dec 08, 2009
> Ident string: 1.4
>   Prefix: C:\Program Files\OpenMPI_v1.4-win32
>  Configured architecture: x86 Windows-6.1
>   Configure host: WORK
>Configured by: Charles Johnson
>Configured on: 02:27 AM Sun 01/24/2010
>   Configure host: WORK
> Built by: Charles Johnson
> Built on: 02:27 AM Sun 01/24/2010
>   Built host: WORK
>   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: cl
>C++ compiler absolute: cl
>   Fortran77 compiler: CMAKE_Fortran_COMPILER-NOTFOUND
>   Fortran77 compiler abs: none
>   Fortran90 compiler:
>   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 parameter check: runtime
> Memory profiling support: no
> Memory debugging support: no
>  libltdl support: no
>Heterogeneous support: no
>  mpirun default --prefix: yes
>  MPI I/O support: yes
>MPI_WTIME support: gettimeofday
> Symbol visibility support: yes
>FT Checkpoint support: yes  (checkpoint thread: no)
>MCA backtrace: none (MCA v2.0, API v2.0, Component v1.4)
>MCA paffinity: windows (MCA v2.0, API v2.0, Component v1.4)
>MCA carto: auto_detect (MCA v2.0, API v2.0, Component v1.4)
>MCA maffinity: first_use (MCA v2.0, API v2.0, Component v1.4)
>MCA timer: windows (MCA v2.0, API v2.0, Component v1.4)
>  MCA installdirs: windows (MCA v2.0, API v2.0, Component v1.4)
>  MCA installdirs: env (MCA v2.0, API v2.0, Component v1.4)
>  MCA installdirs: config (MCA v2.0, API v2.0, Component v1.4)
>  MCA crs: none (MCA v2.0, API v2.0, Component v1.4)
>  MCA dpm: orte (MCA v2.0, API v2.0, Component v1.4)
>   MCA pubsub: orte (MCA v2.0, API v2.0, Component v1.4)
>MCA allocator: basic (MCA v2.0, API v2.0, Component v1.4)
>MCA allocator: bucket (MCA v2.0, API v2.0, Component v1.4)
> MCA coll: basic (MCA v2.0, API v2.0, Component v1.4)
> MCA coll: hierarch (MCA v2.0, API v2.0, Component v1.4)
> MCA coll: self (MCA v2.0, API v2.0, Component v1.4)
> MCA coll: sm (MCA v2.0, API v2.0, Component v1.4)
> MCA coll: sync (MCA v2.0, API v2.0, Component v1.4)
>MCA mpool: rdma (MCA v2.0, API v2.0, Component v1.4)
>MCA mpool: sm (MCA v2.0, API v2.0, Component v1.4)
>  MCA pml: ob1 (MCA v2.0, API v2.0, Component v1.4)
>  MCA bml: r2 (MCA v2.0, API v2.0, Component v1.4)
>  MCA btl: self (MCA v2.0, API v2.0, Component v1.4)
>  MCA btl: sm (MCA v2.0, API v2.0, Component v1.4)
>  MCA btl: tcp (MCA v2.0, API v2.0, Component v1.4)
> MCA topo: unity (MCA v2.0, API v2.0, Component v1.4)
>  MCA osc: pt2pt (MCA v2.0, API v2.0, Component v1.4)
>  MCA osc: rdma (MCA v2.0, API v2.0, Component v1.4)
>  MCA iof: hnp (MCA v2.0, API v2.0, Component v1.4)
>  MCA iof: orted (MCA v2.0, API v2.0, Component v1.4)
>  MCA iof: tool (MCA v2.0, API v2.0, Component v1.4)
>  MCA oob: tcp (MCA v2.0, API v2.0, Component v1.4)
> MCA odls: process (MCA v2.0, API v2.0, Component v1.4)
>MCA rmaps: round_robin (MCA v2.0, API v2.0, Component v1.4)
>MCA rmaps: seq (MCA v2.0, API v2.0

Re: [OMPI users] Windows CMake build problems ...

2010-01-26 Thread cjohnson 
Was able to build and run all the c examples from the tutorial at However, none of the extended or simple c++ examples work, they all die with the same link error.For instance: mpi_gather.cc__#include #include #include using namespace MPI;int main(int argc, char* argv[]) {  int rank;  int recvcount,sendcount;  int reap[8];  int sow[2];  Init(argc,argv);  rank=COMM_WORLD.Get_rank();  sendcount=2;  sow[0]=rank; sow[1]=-rank;  if(rank==1) {    recvcount=2;  }  COMM_WORLD.Gather(sow,sendcount,INT,reap,recvcount,INT,1);  if(rank==1) {    printf("P:%d",rank);    for(int i=0;i<8;++i) {  printf(" %2d ",reap[i]);    }    printf("\n");  }  Finalize();}__Here's the compile output from mpic++:C:\prog\mon\examples>mpic++ mpi_gather.ccMicrosoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50727.762 for 80x86Copyright (C) Microsoft Corporation.  All rights reserved.mpi_gather.ccMicrosoft (R) Incremental Linker Version 8.00.50727.762Copyright (C) Microsoft Corporation.  All rights reserved./out:mpi_gather.exe"/LIBPATH:C:\Program Files\OpenMPI_v1.4-win32\lib"libmpid.liblibopen-pald.liblibopen-rted.liblibmpi_cxxd.liblibmpid.liblibopen-pald.liblibopen-rted.libadvapi32.libWs2_32.libshlwapi.libmpi_gather.objmpi_gather.obj : error LNK2019: unresolved external symbol "void __cdecl MPI::InitializeIntercepts(void)" (?InitializeIntercepts@MPI@@YAXXZ)referenced in function "void __cdecl MPI::Real_init(void)" (?Real_init@MPI@@YAXXZ)mpi_gather.exe : fatal error LNK1120: 1 unresolved externalsEvery c++ dies with this link error.Charlie ...


 Original Message 
Subject: RE: [OMPI users] Windows CMake build problems ...
From: cjohn...@valverdecomputing.com
List-Post: users@lists.open-mpi.org
Date: Tue, January 26, 2010 2:10 am
To: f...@hlrs.de
Cc: "Open MPI Users" 

Yeah, that was it. Thanks.Charlie ...    Original Message  Subject: Re: [OMPI users] Windows CMake build problems ... From: Shiqing Fan  Date: Tue, January 26, 2010 1:57 am To: cjohn...@valverdecomputing.com Cc: Open MPI UsersHi Charlie ,  Did you run the mpicc command in the Visual Studio Command Prompt? Is it  possible for you to call cl.exe from there? Because it sounds like the  VS compiler was not found.   Regards, Shiqing

[OMPI users] Windows: problems running on a second system.

2010-03-14 Thread cjohnson 
Finally got a second development system procured and up and running.Got things working pretty wellon one node, installed on the second and things work there.This may be a similar problem to Charles Shuller's a month ago, maybe not. Tried to launch a program from node work on node work2:C:\prog\mon\debug>mpirun -npernode 1 -host work2 C:\prog\mon\examples\solvers\C\sjacobi.execonnecting to work2username:charles johnsonpassword:**Save Credential?(Y/N) y[Work:03468] This feature hasn't been implemented yet.[Work:03468] Could not connect to namespace cimv2 on node work2. Error code =-2147024891--mpirun was unable to start the specified application as it encountered an error.More information may be available above.--So I tried some of the things you asked from him:C:\prog\mon\debug>wmic /node:192.168.1.37 /user:"charles johnson" process call create notepad.exeEnter the password :**ERROR:Description = Access is denied.Then I tried this:C:\prog\mon\debug>mpirun -np 1 -host work2 notepad.execonnecting to work2username:charles johnsonpassword:**Save Credential?(Y/N) n[Work:03108] Could not connect to namespace cimv2 on node work2. Error code =-2147024891--mpirun was unable to start the specified application as it encountered an error.More information may be available above.--My case may be simpler than his, some misconfiguration or something.As before: , built with   using the VC++ info below (probably more than you want):Microsoft Visual Studio 2005Version 8.0.50727.867  (vsvista.050727-8600)Microsoft .NET FrameworkVersion 2.0.50727 SP2Installed Edition: Enterprise ArchitectMicrosoft Visual C++ 2005   77637-163-905-41563Microsoft Visual C++ 2005Microsoft Visual Studio 2005 Team Edition for Software Architects - ENU Service Pack 1 (KB926601)   Security Update for Microsoft Visual Studio 2005 Team Edition for Software Architects - ENU (KB937061)   Security Update for Microsoft Visual Studio 2005 Team Edition for Software Architects - ENU (KB971023)   Security Update for Microsoft Visual Studio 2005 Team Edition for Software Architects - ENU (KB971090)   Security Update for Microsoft Visual Studio 2005 Team Edition for Software Architects - ENU (KB973673)   Update for Microsoft Visual Studio 2005 Team Edition for Software Architects - ENU (KB932232)   Thanks in advance for any kind help.C.S. Johnson

[OMPI users] Windows: problems running on a second system. 2nd try.

2010-03-14 Thread cjohnson 
For some reason the OpenMPI content filter tossed this message, so I'm sending it again:___Finally got a second development system procured and up and running.Got things working pretty well on one node, installed on the second and things work there.This
may be a similar problem to Charles Shuller's a month ago, maybe not.
Tried to launch a program from node work on node work2:C:\prog\mon\debug>mpirun -npernode 1 -host work2 C:\prog\mon\examples\solvers\C\sjacobi.execonnecting to work2username:charles johnsonpassword:**Save Credential?(Y/N) y[Work:03468] This feature hasn't been implemented yet.[Work:03468] Could not connect to namespace cimv2 on node work2. Error code =-2147024891--mpirun was unable to start the specified application as it encountered an error.More information may be available above.--So I tried some of the things you asked from him:C:\prog\mon\debug>wmic /node:192.168.1.37 /user:"charles johnson" process call create notepad.exeEnter the password :**ERROR:Description = Access is denied.Then I tried this:C:\prog\mon\debug>mpirun -np 1 -host work2 notepad.execonnecting to work2username:charles johnsonpassword:**Save Credential?(Y/N) n[Work:03108] Could not connect to namespace cimv2 on node work2. Error code =-2147024891--mpirun was unable to start the specified application as it encountered an error.More information may be available above.--My case may be simpler than his, some misconfiguration or something.My configuration: Two Windows 7 boxes, using , built with   using the VC++ info below (probably more than you want):Microsoft Visual Studio 2005Version 8.0.50727.867  (vsvista.050727-8600)Microsoft .NET FrameworkVersion 2.0.50727 SP2Installed Edition: Enterprise ArchitectMicrosoft Visual C++ 2005   77637-163-905-41563Microsoft Visual C++ 2005Microsoft Visual Studio 2005 Team Edition for Software Architects - ENU Service Pack 1 (KB926601)   Security Update for Microsoft Visual Studio 2005 Team Edition for Software Architects - ENU (KB937061)   Security Update for Microsoft Visual Studio 2005 Team Edition for Software Architects - ENU (KB971023)   Security Update for Microsoft Visual Studio 2005 Team Edition for Software Architects - ENU (KB971090)   Security Update for Microsoft Visual Studio 2005 Team Edition for Software Architects - ENU (KB973673)   Update for Microsoft Visual Studio 2005 Team Edition for Software Architects - ENU (KB932232)   Thanks in advance for any kind help.C.S. Johnson

Re: [OMPI users] Windows: problems running on a second system.

2010-03-16 Thread cjohnson 
I went and did this in every conceivable combination of ways. I did the DCOMCNFG thing with both the launch and the remote access permissions, granting my local logon on each node everything. Then I did the namespaces with wmimgmt.msc, first on every object in both the CIMV2 (which had ms_409 and Applications branches) and DEFAULT (which had an ms_409 branch), and then on the CIMV2 and DEFAULT namespaces themselves, granting every checkbox permission.Nothing changed, same error code which is a "DCOM access denied" error.I noticed that the name mentioned in the error from mpirun is cimv2 in lower case, while the namespace in WMI security box is upper case CIMV2. Is that a problem?Charlie ...


 Original Message 
Subject: Re: [OMPI users] Windows: problems running on a second system.
From: Shiqing Fan 
List-Post: users@lists.open-mpi.org
Date: Mon, March 15, 2010 3:18 am
To: cjohn...@valverdecomputing.com
Cc: Open MPI Users 


Hi Johnson,

I was trying to reproduce it, so that I could give you a direct 
solution. The problem might be the DCOM configure is not correct. Have 
you done it as described in this link: 
http://msdn.microsoft.com/en-us/library/aa393266(VS.85).aspx, you need 
give the user "remote activate" permission on namespace CIMV2 and DEFAULT.


Regards,
Shiqing


cjohn...@valverdecomputing.com wrote:
> Finally got a second development system procured and up and running.
>
> Got things working pretty wellon one node, installed on the second and 
> things work there.
>
> This may be a similar problem to Charles Shuller's a month ago, maybe 
> not. Tried to launch a program from node work on node work2:
>
> C:\prog\mon\debug>mpirun -npernode 1 -host work2 
> C:\prog\mon\examples\solvers\C\sjacobi.exe
> connecting to work2
> username:charles johnson
> password:**
> Save Credential?(Y/N) y
> [Work:03468] This feature hasn't been implemented yet.
> [Work:03468] Could not connect to namespace cimv2 on node work2. Error 
> code =-2147024891
> --
> mpirun was unable to start the specified application as it encountered 
> an error.
> More information may be available above.
> --
>
> So I tried some of the things you asked from him:
>
> C:\prog\mon\debug>wmic /node:192.168.1.37 /user:"charles johnson" 
> process call create notepad.exe
> Enter the password :**
>
> ERROR:
> Description = Access is denied.
>
> Then I tried this:
>
> C:\prog\mon\debug>mpirun -np 1 -host work2 notepad.exe
> connecting to work2
> username:charles johnson
> password:**
> Save Credential?(Y/N) n
> [Work:03108] Could not connect to namespace cimv2 on node work2. Error 
> code =-2147024891
> --
> mpirun was unable to start the specified application as it encountered 
> an error.
> More information may be available above.
> --
>
> My case may be simpler than his, some misconfiguration or something.
>
> As before: , built with   
> using the VC++ info below (probably more than you want):
>
> Microsoft Visual Studio 2005
> Version 8.0.50727.867  (vsvista.050727-8600)
> Microsoft .NET Framework
> Version 2.0.50727 SP2
>
> Installed Edition: Enterprise Architect
>
> Microsoft Visual C++ 2005   77637-163-905-41563
> Microsoft Visual C++ 2005
>
> Microsoft Visual Studio 2005 Team Edition for Software Architects - 
> ENU Service Pack 1 (KB926601)  
>
> Security Update for Microsoft Visual Studio 2005 Team Edition for 
> Software Architects - ENU (KB937061)  
>
> Security Update for Microsoft Visual Studio 2005 Team Edition for 
> Software Architects - ENU (KB971023)  
>
> Security Update for Microsoft Visual Studio 2005 Team Edition for 
> Software Architects - ENU (KB971090)  
>
> Security Update for Microsoft Visual Studio 2005 Team Edition for 
> Software Architects - ENU (KB973673)  
>
> Update for Microsoft Visual Studio 2005 Team Edition for Software 
> Architects - ENU (KB932232)  
>
> Thanks in advance for any kind help.
>
> C.S. Johnson
>
> 
>
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users


-- 
--
Shiqing Fan  http://www.hlrs.de/people/fan
High Performance Computing   Tel.: +49 711 685 87234
  Center Stuttgart (HLRS)Fax.: +49 711 685 65832
Address:Allmandring 30   email: f...@hlrs.de
70569 Stuttgart

Re: [OMPI users] Windows: problems running on a second system.

2010-03-16 Thread cjohnson 
No, I granted everything, clicked all the boxes.In DCOMCNFG.exe, got to the COM Security tab, there are two "edit limits" sections, for Access Permissions and for Launch and Activation Permissions. I added myself as a user in both, and granted all 2 permissions in the first, and all 4 permissions in the second.Charlie ...


 Original Message 
Subject: Re: [OMPI users] Windows: problems running on a second system.
From: Shiqing Fan 
List-Post: users@lists.open-mpi.org
Date: Tue, March 16, 2010 2:33 am
To: cjohn...@valverdecomputing.com
Cc: Open MPI Users 

Hi,

The lower case in the mpirun warning message shouldn't matter, as long 
as the wmic launch doesn't work, mpirun doesn't neither.

According to your description, I think you missed some settings in 
DCOMCNFG, that you probably have to grant the user "remote activation" 
and "remote launch" permissions in the "launch and activation 
permissions" section; the local/remote access permissions don't help.


Regards,
Shiqing



cjohn...@valverdecomputing.com wrote:
> I went and did this in every conceivable combination of ways. I did 
> the *DCOMCNFG* thing with both the launch and the remote access 
> permissions, granting my local logon on each node everything. Then I 
> did the namespaces with *wmimgmt.msc*, first on every object in both 
> the CIMV2 (which had ms_409 and Applications branches) and DEFAULT 
> (which had an ms_409 branch), and then on the CIMV2 and DEFAULT 
> namespaces themselves, granting every checkbox permission.
>
> Nothing changed, same error code which is a "DCOM access denied" error.
>
> I noticed that the name mentioned in the error from mpirun is cimv2 in 
> lower case, while the namespace in WMI security box is upper case 
> CIMV2. Is that a problem?
>
> Charlie ...
>
>  Original Message 
> Subject: Re: [OMPI users] Windows: problems running on a second
> system.
> From: Shiqing Fan 
> Date: Mon, March 15, 2010 3:18 am
> To: cjohn...@valverdecomputing.com
> Cc: Open MPI Users 
>
>
> Hi Johnson,
>
> I was trying to reproduce it, so that I could give you a direct
> solution. The problem might be the DCOM configure is not correct.
> Have
> you done it as described in this link:
> http://msdn.microsoft.com/en-us/library/aa393266(VS.85).aspx
> ,
> you need
> give the user "remote activate" permission on namespace CIMV2 and
> DEFAULT.
>
>
> Regards,
> Shiqing
>
>
> cjohn...@valverdecomputing.com wrote:
> > Finally got a second development system procured and up and running.
> >
> > Got things working pretty wellon one node, installed on the
> second and
> > things work there.
> >
> > This may be a similar problem to Charles Shuller's a month ago,
> maybe
> > not. Tried to launch a program from node work on node work2:
> >
> > C:\prog\mon\debug>mpirun -npernode 1 -host work2
> > C:\prog\mon\examples\solvers\C\sjacobi.exe
> > connecting to work2
> > username:charles johnson
> > password:**
> > Save Credential?(Y/N) y
> > [Work:03468] This feature hasn't been implemented yet.
> > [Work:03468] Could not connect to namespace cimv2 on node work2.
> Error
> > code =-2147024891
> > --
> > mpirun was unable to start the specified application as it
> encountered
> > an error.
> > More information may be available above.
> > --
> >
> > So I tried some of the things you asked from him:
> >
> > C:\prog\mon\debug>wmic /node:192.168.1.37 /user:"charles johnson"
> > process call create notepad.exe
> > Enter the password :**
> >
> > ERROR:
> > Description = Access is denied.
> >
> > Then I tried this:
> >
> > C:\prog\mon\debug>mpirun -np 1 -host work2 notepad.exe
> > connecting to work2
> > username:charles johnson
> > password:**
> > Save Credential?(Y/N) n
> > [Work:03108] Could not connect to namespace cimv2 on node work2.
> Error
> > code =-2147024891
> > --
> > mpirun was unable to start the specified application as it
> encountered
> > an error.
> > More information may be available above.
> > --
> >
> > My case may be simpler than his, some misconfiguration or something.
> >
> > As before: , built with 
> > using the VC++ info below (probably more than you want):
> >
> > Microsoft Visual Studio 2005
> > Version 8.0.50727.867 (vsvista.050727-8600)
> > Microsoft .NET Framework
> > Version 2.0.50727 SP2
> >
> > Ins

Re: [OMPI users] Windows: problems running on a second system.

2010-03-16 Thread cjohnson 
Like I said initially, these are two Windows 7 boxes. Could that be a difference?Charlie ...


 Original Message 
Subject: Re: [OMPI users] Windows: problems running on a second system.
From: Shiqing Fan 
List-Post: users@lists.open-mpi.org
Date: Tue, March 16, 2010 5:52 am
To: cjohn...@valverdecomputing.com
Cc: Open MPI Users 


Hi Charlie,

I have tested with creating a new user on my Windows XP box, and 
everything works just fine, wmic can launch remote process without problem.

There are several possibilities that the "Access is denied" could 
happen. It could be the DCOM setting is wrong, i.e. the user doesn't 
have the permission to use it; or it could also be that the user 
name/password provided is not correct, so that the authentication just 
fails. However, your settings look good to me.


Regards,
Shiqing



cjohn...@valverdecomputing.com wrote:
> No, I granted everything, clicked all the boxes.
>
> In DCOMCNFG.exe, got to the COM Security tab, there are two "edit 
> limits" sections, for Access Permissions and for Launch and Activation 
> Permissions. I added myself as a user in both, and granted all 2 
> permissions in the first, and all 4 permissions in the second.
>
> Charlie ...
>
>  Original Message 
> Subject: Re: [OMPI users] Windows: problems running on a second
> system.
> From: Shiqing Fan 
> Date: Tue, March 16, 2010 2:33 am
> To: cjohn...@valverdecomputing.com
> Cc: Open MPI Users 
>
> Hi,
>
> The lower case in the mpirun warning message shouldn't matter, as
> long
> as the wmic launch doesn't work, mpirun doesn't neither.
>
> According to your description, I think you missed some settings in
> DCOMCNFG, that you probably have to grant the user "remote
> activation"
> and "remote launch" permissions in the "launch and activation
> permissions" section; the local/remote access permissions don't help.
>
>
> Regards,
> Shiqing
>
>
>
> cjohn...@valverdecomputing.com wrote:
> > I went and did this in every conceivable combination of ways. I did
> > the *DCOMCNFG* thing with both the launch and the remote access
> > permissions, granting my local logon on each node everything. Then I
> > did the namespaces with *wmimgmt.msc*, first on every object in both
> > the CIMV2 (which had ms_409 and Applications branches) and DEFAULT
> > (which had an ms_409 branch), and then on the CIMV2 and DEFAULT
> > namespaces themselves, granting every checkbox permission.
> >
> > Nothing changed, same error code which is a "DCOM access denied"
> error.
> >
> > I noticed that the name mentioned in the error from mpirun is
> cimv2 in
> > lower case, while the namespace in WMI security box is upper case
> > CIMV2. Is that a problem?
> >
> > Charlie ...
> >
> >  Original Message 
> > Subject: Re: [OMPI users] Windows: problems running on a second
> > system.
> > From: Shiqing Fan 
> > Date: Mon, March 15, 2010 3:18 am
> > To: cjohn...@valverdecomputing.com
> > Cc: Open MPI Users 
> >
> >
> > Hi Johnson,
> >
> > I was trying to reproduce it, so that I could give you a direct
> > solution. The problem might be the DCOM configure is not correct.
> > Have
> > you done it as described in this link:
> > http://msdn.microsoft.com/en-us/library/aa393266(VS.85).aspx
> 
> > ,
> > you need
> > give the user "remote activate" permission on namespace CIMV2 and
> > DEFAULT.
> >
> >
> > Regards,
> > Shiqing
> >
> >
> > cjohn...@valverdecomputing.com wrote:
> > > Finally got a second development system procured and up and
> running.
> > >
> > > Got things working pretty wellon one node, installed on the
> > second and
> > > things work there.
> > >
> > > This may be a similar problem to Charles Shuller's a month ago,
> > maybe
> > > not. Tried to launch a program from node work on node work2:
> > >
> > > C:\prog\mon\debug>mpirun -npernode 1 -host work2
> > > C:\prog\mon\examples\solvers\C\sjacobi.exe
> > > connecting to work2
> > > username:charles johnson
> > > password:**
> > > Save Credential?(Y/N) y
> > > [Work:03468] This feature hasn't been implemented yet.
> > > [Work:03468] Could not connect to namespace cimv2 on node work2.
> > Error
> > > code =-2147024891
> > >
> --
> > > mpirun was unable to start the specified application as it
> > encountered
> > > an error.
> > > More information may be available above.
> > >
> --
>