l define min and max.
Hopefully this is helpful.
BUT I would still like help on how to build in native windows.
Thanks Nev
-Original Message-
From: Neville Clark
Reply-To: Open MPI Users
To: Open MPI Users
Subject: Re: [OMPI users] Fwd: Problems installing in Cygwin
List-Post: users@lis
ere a MSVC
project file? Or should I use Cygwin to run configure, but use the
microsoft compiler and linker?
I have not yet looked into using SFU.
Thank you in advance
Nev
-Original Message-
From: George Bosilca
Reply-To: Open MPI Users
To: Open MPI Users
Subject: Re: [OMPI users] Fwd
On Oct 31, 2008, at 3:20 PM, Gustavo Seabra wrote:
As Jeff mentioned this component is not required on Windows. You
can disable
it completely in Open MPI and everything will continue to work
correctly.
Please add --enable-mca-no-build=memory_mallopt o maybe the more
generic (as
there is no
Gustavo,
I guess that if you disable the vt contrib package, this is take you
one step further :) Hopefully at the end of the compile stage ... and
at the beginning of troubles with running the cygwin parallel
applications ...
Meanwhile, there is a special option to disable contrib packag
Ok, I'll CC the VT guys on the ticket and let them know. They'll
likely slurp in whatever fix we do for OMPI into VT.
FWIW: you can disable the VT package with:
--enable-contrib-no-build=vt
On Oct 31, 2008, at 3:02 PM, Gustavo Seabra wrote:
As I keep trying to install OpenMPI in Cygwi
On Thu, Oct 30, 2008 at 9:04 AM, George Bosilca wrote:
Hi George,
I'm sorry for taking too long to respond. As you mentioned, config
takes a veeery long time in cygwin, and then the install itself
takes many ties that :-(
> As Jeff mentioned this component is not required on Windows. You can
As I keep trying to install OpenMPI in Cygwin, I found another
instance where RTFD_NEXT is assumed to be present. Will keep trying...
Gustavo.
=
Making all in vtlib
make[5]: Entering directory
`/home/seabra/local/openmpi-1.3b1/ompi/contrib/vt/vt/vtlib'
gcc -DHAVE_CONFI
On Oct 30, 2008, at 9:18 AM, Gustavo Seabra wrote:
Understood; this was a more complete/precise meaning for my
question "Is
there any other OS where
dlsym() is present by RTLD_NEXT is not?" I suppose we can extend the
configure test to check for RTLD_NEXT as well. In this way, that
compone
On Thu, Oct 30, 2008 at 8:40 AM, Jeff Squyres wrote:
> On Oct 29, 2008, at 4:31 PM, Gustavo Seabra wrote:
>
>>> Ugh. IMHO, Cygwin != POSIX.
>>>
>>> The problem is that we're making the assumption that if dlsym() is
>>> present,
>>> RTLD_NEXT is defined. I guess that's not true for cygwin (lame).
Gustavo,
As Jeff mentioned this component is not required on Windows. You can
disable it completely in Open MPI and everything will continue to work
correctly. Please add --enable-mca-no-build=memory_mallopt o maybe the
more generic (as there is no need for any memory manager on Windows --
On Oct 29, 2008, at 4:31 PM, Gustavo Seabra wrote:
Ugh. IMHO, Cygwin != POSIX.
The problem is that we're making the assumption that if dlsym() is
present,
RTLD_NEXT is defined. I guess that's not true for cygwin (lame).
I suppose
that we could also check for RTLD_NEXT...? Is there any o
On Wed, Oct 29, 2008 at 1:49 PM, Jeff Squyres wrote:
> Ugh. IMHO, Cygwin != POSIX.
>
> The problem is that we're making the assumption that if dlsym() is present,
> RTLD_NEXT is defined. I guess that's not true for cygwin (lame). I suppose
> that we could also check for RTLD_NEXT...? Is there a
Ugh. IMHO, Cygwin != POSIX.
The problem is that we're making the assumption that if dlsym() is
present, RTLD_NEXT is defined. I guess that's not true for cygwin
(lame). I suppose that we could also check for RTLD_NEXT...? Is
there any other OS where dlsym() is present by RTLD_NEXT is no
On Wed, Oct 29, 2008 at 10:48 AM, George Bosilca wrote:
> Gustavo,
>
> I think we have a problem in the "make dist" for the 1.2. I just downloaded
> the latest 1.2.8, and the windows timer component header file is not in the
> tarball. This file is not automatically generated, and it is in the svn
George --
Do you want to make a CMR for that fix for v1.2 anyway? It's still up
in the air as to whether there will be a 1.2.9 or not (let's hope not,
but...). If nothing else, we can have an unreleased 1.2.9 beta (or
somesuch) with a handful of fixes like this to close out the 1.2 series
Gustavo,
I think we have a problem in the "make dist" for the 1.2. I just
downloaded the latest 1.2.8, and the windows timer component header
file is not in the tarball. This file is not automatically generated,
and it is in the svn version.
Anyway, the 1.3 is nearly ready to replace the
On Mon, Oct 27, 2008 at 4:52 PM, Jeff Squyres wrote:
> Sorry for the lack of reply; several of us were at the MPI Forum meeting
> last week, and although I can't speak for everyone else, I know that I
> always fall [way] behind on e-mail when I travel. :-\
>
> The windows port is very much a work-
On Tue, Oct 28, 2008 at 9:06 AM, George Bosilca wrote:
> It is complaining about a missing file. This is a file from the Open MPI
> distribution, I wonder how it can be missing. Can you verify that the file
> opal/mca/timer/windows/timer_windows_component.h is there ?
No, it's not. But I see a
opa
It is complaining about a missing file. This is a file from the Open
MPI distribution, I wonder how it can be missing. Can you verify that
the file opal/mca/timer/windows/timer_windows_component.h is there ?
Thanks,
george.
On Oct 27, 2008, at 4:52 PM, Jeff Squyres wrote:
Sorry for
Sorry for the lack of reply; several of us were at the MPI Forum
meeting last week, and although I can't speak for everyone else, I
know that I always fall [way] behind on e-mail when I travel. :-\
The windows port is very much a work-in-progress. I'm not surprised
that it doesn't work.
Hi All,
(Sorry if you already got this message befor, but since I didn't get
any answer, I'm assuming it didn't get through to the list.)
I am trying to install OpenMPI in Cygwin. from a cygwin bash shell, I
configured OpenMPI with the command below:
$ echo $MPI_HOME
/home/seabra/local/openmpi-1
21 matches
Mail list logo
