Thanks.
Saadat.
On 7/11/06, Ralph Castain wrote:
I'm afraid that the current comm_spawn system really can't run unless
started via mpirun. I'm going to take a shot at fixing it in the near future
and can let you know when that is accomplished, but it might take a little
while before I get th
I¹m afraid that the current comm_spawn system really can¹t run unless
started via mpirun. I¹m going to take a shot at fixing it in the near future
and can let you know when that is accomplished, but it might take a little
while before I get the time.
Ralph
On 7/11/06 4:26 PM, "s anwar" wrote:
On Tue, Jul 11, 2006 at 12:23:16PM -0400, George Bosilca wrote:
> I doubt that icc should know anything about
> the gxx_personality. In fact it look like icc is trying to use some
> libraries compiled with g++.
As an aside, both Intel C++ and PathScale C++ are 100% g++ compatible.
Symbols lik
Jeff:
I've tried my application with MPICH2 and OpenMPI only. The readline stuff
works in OpenMPI as long as I don't start my application with mpirun. It
does not work in MPICH2 irrespective of whether I start my application with
mpirun or not.
My application starts on a workstation and spawns s
Hey Justin,
Any further details?
Thanks,
Galen
On Jul 8, 2006, at 9:10 AM, Justin Bronder wrote:
1.) Compiling without XL will take a little while, but I have the
setup
for the
other questions ready now. I figured I'd answer them right away.
2.) TCP works fine, and is quite quick comp
Sorry for not replying earlier.
It is likely that Open MPI won't work properly in this situation -- Open
MPI provides basic I/O forwarding. I don't know if curses-based or
readline-based applications will work through our forwarding.
Do you know if this application works with other MPI imple
Yvan,
Shame on me for bringing this bug back into the 1.1. Until we release
the 1.1.1 please use the nightly build or the beta from our web site.
Starting with the revision 10710 this bug was removed. Forever I hope :)
Thanks,
george.
On Jul 10, 2006, at 5:27 PM, Yvan Fournier wrote:
> Message: 2
> Date: Tue, 11 Jul 2006 12:23:16 -0400
> From: George Bosilca
> Subject: Re: [OMPI users] OMPI 1.1 build failure with Intel 9.0
> To: Open MPI Users
> Message-ID: <507769b7-8495-478b-b9a8-189826653...@cs.utk.edu>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
The MPI standard definition of a port is not the one you expect. It
is nothing like a TCP port, even if they support similar operations
(open and close). This port is an opaque value (however MPI stadard
define it as being a TEXT) than will be used internally by the MPI
library in order to
Hi Edgar,
I really was responding to the original poster, not to you.
The MPI port should be treated as an opaque object, really, right?
I was also wondering whether the user was worried about the TCP port
that MPI daemons use to communicate with each other (assuming there
are daemons involved)
I have a seprate process which is not linked to this process and hence
doesnot know anything about this MPI process. I wants to receive some data
for this server process.
Hence I wanted to know if i could specify a specific port. I have used
MPI_publish and it seem to work fine.
Please advic
John Robinson wrote:
The MPI publish/lookup calls should handle this, if OpenMPI has them. I
haven't tried this with OpenMPI yet, but it claims MPI-2 compilance,
right? ;-)
of course, but MPI does not say what an MPI port has to be. For Open MPI
this is *not* equal to a TCP port number... S
The MPI publish/lookup calls should handle this, if OpenMPI has them. I
haven't tried this with OpenMPI yet, but it claims MPI-2 compilance,
right? ;-)
/jr
---
Ralph H Castain wrote:
On 7/11/06 11:59 AM, "Edgar Gabriel" wrote:
Abhishek Agarwal wrote:
Hello,
Is there a way of providing
On 7/11/06 11:59 AM, "Edgar Gabriel" wrote:
> Abhishek Agarwal wrote:
>> Hello,
>>
>> Is there a way of providing a specific port number in MPI_Info when using a
>> MPI_Open_port command so that clients know which port number to connect.
>
> the MPI port-name in Open MPI has nothing to do with
Abhishek Agarwal wrote:
Hello,
Is there a way of providing a specific port number in MPI_Info when using a
MPI_Open_port command so that clients know which port number to connect.
the MPI port-name in Open MPI has nothing to do with a TCP port number.
The port-name right now is a combination
I'm using the Intel compiler 9.0 on several platforms to compile Open
MPI. I never get such kind of errors. I look into the attached file
and I notice 2 things. First, there is a -m64 flag on the command
line, and icc complain about not knowing anything about it (and it's
right). Second, at
Hello,
Is there a way of providing a specific port number in MPI_Info when using a
MPI_Open_port command so that clients know which port number to connect.
Do advice of any solution so that we can create the portname inside the
client once we know the port number of server.
Thanks
Abhishek
What machine is this on, Daryl? I have a conference call with Intel
re: compiler problems today. If I can verify this is an Intel
problem I can bring it up to them.
Thanks,
david
On Jul 11, 2006, at 9:53 AM, Daryl W. Grunau wrote:
I'm trying to build version 1.1 with Intel 9.0 compilers a
I'm trying to build version 1.1 with Intel 9.0 compilers and getting an
error at the very end in the tools directory: ompi/tools/ompi_info. The
build appears to die with undefined references to things that belong to the
C++ string class (see long attachment). Strange thing is that this same
code
www.clustermonkey.net is a very good place to start, click on the "Columns"
section in the "Main Menu" in the left pane.
Le mardi 11 juillet 2006 07:25, Tony Power a écrit :
> Hi!
> Where can I find a introductory tutorial on open-mpi?
> Thank you ;)
>
Hi!
Where can I find a introductory tutorial on open-mpi?
Thank you ;)
21 matches
Mail list logo
