Hi,
well, I don't have a lot of experience with VS+MPI, but these are the
steps taht I followed to make my projects run:
1. Select your project from the Solution explorer, right-click and select
"Properties"
2. From the list on the left, select "Debugging"
3. Set "Debugger to launch" to "MPI
Can someone comments on my post below? I just wonder if this is
something that should be fixed in OMPI's configure script or elsewhere.
Ning
On 27/06/11 10:24, Ning Li wrote:
Hello,
I built OpenMPI 1.5.3 using NAG compiler v 5.2 on a new system running
Fedora 15 (with gcc 4.6). OpenMPI can
If you download a 1.5 tarball tagged at r24853 or above, the problem should be
fixed.
On Jul 4, 2011, at 12:34 PM, Rodrigo Oliveira wrote:
>
> Thanks for the response, Ralph.
>
> I checked my application and it seems not have a race condition in the accept
> stage. The server is started and
Thanks for the response, Ralph.
I checked my application and it seems not have a race condition in the
accept stage. The server is started and it stores the port name in a file.
When a client is started, it gets this port name and tries to connect. In my
tests the error happens about 1 time in 10
Hi,
In this regard I have following two questions...
1) For Release build using VS2008, why it generates *msv*.dll* files?
They are dependent libraries for OMPI libraries. It's the default
behavior using CMake.
2) For Release build using VS2008, why it generates **d.dll* files
(i.e. debug
Greetings!
On doing Release build for Visual Studio 2008 I am observing following debug
files along with other files
...
libmpi*d.dll*
libmpi_cxx*d.dll*
libmpi_f77*d.dll* etc...
*msvcm90.dll*
* msvcp90.dll*
* msvcr90.dll*
In this regard I have following two questions...
1) For Release
