> -Original Message-
> From: Shiqing Fan [mailto:f...@hlrs.de]
> Sent: 30 November 2010 23:39
> To: Open MPI Users
> Cc: Hicham Mouline; Rainer Keller
> Subject: Re: [OMPI users] failure to launch MPMD program on win32 w
> 1.4.3
>
> Hi,
>
> I don't have boost on my Windows, so I made a ve
Hello,
>mpic++ -showme:link
/TP /EHsc /link /LIBPATH:"C:/Program Files (x86)/openmpi/lib" libmpi.lib
libopen-pal.lib libopen-rte.lib libmpi_cxx.lib libmpi.lib libopen-pal.lib
libopen-rte.lib advapi32.lib Ws2_32.lib shlwapi.lib
reports using the 4 mpi libs twice.
I've followed the cmake way in RE
Hi Hicham,
I've had this issue with -np 3 : -np 3 but not with -np 2: -np 2 or
-np 1: -np 4 or other combinations.
I've also rebuilt from vs2008 with the libs advapi32.lib Ws2_32.lib
shlwapi.lib as visible in the text file:
share\openmpi\mpic++.exe-wrapper-data.txt, and the problem seemed to
Hi Hicham,
Thanks for noticing it. It's now been fixed on trunk.
Regards,
Shiqing
On 2010-12-1 10:02 AM, Hicham Mouline wrote:
Hello,
mpic++ -showme:link
/TP /EHsc /link /LIBPATH:"C:/Program Files (x86)/openmpi/lib" libmpi.lib
libopen-pal.lib libopen-rte.lib libmpi_cxx.lib libmpi.lib libop
Hi Kalin,
Which version of Open MPI did you use? It seems that the ess component
couldn't be selected. Could you please send me the output of ompi_info?
Regards,
Shiqing
On 2010-11-30 12:32 AM, Kalin Kanov wrote:
Hi Shiqing,
I must have missed your response among all the e-mails that get s
On Mon, Nov 22, 2010 at 04:40:14PM -0700, James Overfelt wrote:
> Hello,
>
> I have a small test case where a file created with MPI_File_open
> is still open at the time MPI_Finalize is called. In the actual
> program there are lots of open files and it would be nice to avoid the
> resulting
Hi Shiqing,
I am using OpenMPI version 1.4.2
Here is the output of ompi_info:
Package: Open MPI Kalin Kanov@LAZAR Distribution
Open MPI: 1.4.2
Open MPI SVN revision: r23093
Open MPI release date: May 04, 2010
Open RTE: 1.4.2
Open RTE SVN
On Wed, Dec 1, 2010 at 8:28 AM, Rob Latham wrote:
> On Mon, Nov 22, 2010 at 04:40:14PM -0700, James Overfelt wrote:
>> Hello,
>>
>> I have a small test case where a file created with MPI_File_open
>> is still open at the time MPI_Finalize is called. In the actual
>> program there are lots of
OpenMPI version: 1.4.3
Platform: IBM P5, 32 processors, 256 GB memory, Symmetric Multi-Threading (SMT)
enabled
Application: starts up 48 processes and does MPI using MPI_Barrier, MPI_Get,
MPI_Put (lots of transfers, large amounts of data)
Issue: When implemented using Open MPI vs. IBM's MPI ('po
Sorry, one more question: I don't completely understand the version
numbering, but can/will this fix go into 1.5.1 at some point? I notice
that the trunk is labeled as 1.7.
Thanks again
Jesse Ziser wrote:
It turned out I was using development version 1.5.0. After going back
to the release v
I can schedule it into the 1.5 series, but I don't think it will make 1.5.1
(too close to release). Have to ask...
On Dec 1, 2010, at 2:12 PM, Jesse Ziser wrote:
> Sorry, one more question: I don't completely understand the version
> numbering, but can/will this fix go into 1.5.1 at some point?
On Dec 1, 2010, at 4:12 PM, Jesse Ziser wrote:
> Sorry, one more question: I don't completely understand the version
> numbering, but can/will this fix go into 1.5.1 at some point? I notice that
> the trunk is labeled as 1.7.
Here's an explanation of our version numbering:
http://www.open
On Dec 1, 2010, at 10:28 AM, Rob Latham wrote:
> under openmpi, this test program fails because openmpi is trying to
> help you out. I'm going to need some help from the openmpi folks
> here, but the backtrace makes it look like MPI_Finalize is setting the
> "no more mpi calls allowed" flag, and
> -Original Message-
> From: Shiqing Fan [mailto:f...@hlrs.de]
> Sent: 01 December 2010 11:29
> To: Open MPI Users
> Cc: Hicham Mouline
> Subject: Re: [OMPI users] win: mpic++ -showme reports duplicate .libs
>
> Hi Hicham,
>
> Thanks for noticing it. It's now been fixed on trunk.
>
>
>
Hi,
Following the instructions from Readme.windows, I've used cmake and 4 build
directories to generate release and debug win32 and x64 builds. When it came
to install, I wondered: there are 4 directories involved, bin, lib, share
and include.
Are include and share identical across the 4 configur
15 matches
Mail list logo