Hi all,
I am having some trouble with this function. I want to map data to a
2x2 block-cyclic configuration in C, using the code:
MPI_Barrier(blacs_comm);
// size of each matrix
int *array_of_gsizes = new int[2];
array_of_gsizes[0]=this->nx;
array_of_gs
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
Brock
I have a patch for 1.2 that will allow hostfiles to work with TM. If
it would help, I can send it to you off-list.
Ralph
On Oct 30, 2008, at 8:40 AM, Brock Palen wrote:
Yes I never made it to my mailbox. Strange, (wink wink, ahh email).
Thanks for letting me know about it, I have t
If you are using the module 'use mpi' then don't have "include
'mpif.h'"
use only one of those.
Make sure you use 'mpif90' to compile. Also make sure to read the
other reply on this list. about include paths for headers and modules.
Brock Palen
www.umich.edu/~brockp
Center for Advanced
Brock,
I am using the g95 compiler on Mac OS X.
I had
include 'mpif.h'
and I got the message "could not open mpif.h".
At your suggestion, I have added
USE mpi
include 'mpif.h'
I get the message "Can't open module file 'mpi.mod'
What am I doing wrong?
Thanks
Ben
On Thu, Oct 30, 2008 at 2:38 PM
Benjamin Lamptey wrote:
Hello,
I am new at using open-mpi and will like to know something basic.
What is the equivalent of the "mpif.h" in open-mpi which is normally
"included" at
the beginning of mpi codes (fortran in this case).
Hello Benjamin and List
As far as I know, it is just the s
Benjamin Lamptey wrote:
Hello,
I am new at using open-mpi and will like to know something basic.
What is the equivalent of the "mpif.h" in open-mpi which is normally
"included" at
the beginning of mpi codes (fortran in this case).
I shall appreciate that for cpp as well.
For Fortran:
Yes I never made it to my mailbox. Strange, (wink wink, ahh email).
Thanks for letting me know about it, I have the message now.
as for using 1.3 prerelease, that is not really an option right now
for us. I think we can get by with 1.2 without threads or do some
hacking (ppn=largest number
If your using fortran 90 the mpi module is best:
use mpi
If 77 (or don't have a working module)
include 'mpif.h'
Just like any other MPI library.
Brock Palen
www.umich.edu/~brockp
Center for Advanced Computing
bro...@umich.edu
(734)936-1985
On Oct 30, 2008, at 10:33 AM, Benjamin Lamptey w
Hello,
I am new at using open-mpi and will like to know something basic.
What is the equivalent of the "mpif.h" in open-mpi which is normally
"included" at
the beginning of mpi codes (fortran in this case).
I shall appreciate that for cpp as well.
Thanks
Ben
On Oct 30, 2008, at 8:13 AM, Reuti wrote:
Am 30.10.2008 um 14:46 schrieb Brock Palen:
Any thoughts on this?
We are looking writing a script that parses $PBS_NODEFILE to create
a machinefile and using -machinefile
When we do that though we have to disable tm to avoid an error (-
mca pls
Am 30.10.2008 um 14:46 schrieb Brock Palen:
Any thoughts on this?
We are looking writing a script that parses $PBS_NODEFILE to create
a machinefile and using -machinefile
When we do that though we have to disable tm to avoid an error (-
mca pls ^tm) this is far from preferable.
What abou
I believe I answered much of this the other day - did it get lost in
the email?
As for using TM with a hostfile - this is an unfortunately bug in the
1.2 series. You can't - you'll have to move to 1.3 to do so. When you
do, note the changed handling of hostfiles as specified on the wiki:
Any thoughts on this?
We are looking writing a script that parses $PBS_NODEFILE to create a
machinefile and using -machinefile
When we do that though we have to disable tm to avoid an error (-mca
pls ^tm) this is far from preferable.
Any ideas to tell mpirun to only launch on half the cpu
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
17 matches
Mail list logo
