Re: [OMPI users] Tracing the library using gdb and xterm

2008-01-01 Thread Doug Reeder
Krishna, If you are using ssh to connect to the second machine you need to be sure that ssh X11 forwarding is enabled and you may need to have mpi use ssh -X or ssh -Y to connect to the second machine. That is how the DISPLAY gets set using ssh. Doug Reeder On Jan 1, 2008, at 8:11 AM,

Re: [OMPI users] Can't compile C++ program with extern "C" { #include mpi.h }

2008-01-01 Thread Brian Barrett
On Jan 1, 2008, at 12:47 AM, Adam C Powell IV wrote: On Mon, 2007-12-31 at 20:01 -0700, Brian Barrett wrote: Yeah, this is a complicated example, mostly because HDF5 should really be covering this problem for you. I think your only option at that point would be to use the #define to not

Re: [OMPI users] Tracing the library using gdb and xterm

2008-01-01 Thread Jeff Pummill
Krishna, When you log in to the remote system, use ssh -X or ssh -Y which will export the xterm back thru the ssh connection. Jeff Pummill University of Arkansas Krishna Chaitanya wrote: Hi, I have been tracing the interactions between the PERUSE and MPI library,on one

[OMPI users] Tracing the library using gdb and xterm

2008-01-01 Thread Krishna Chaitanya
Hi, I have been tracing the interactions between the PERUSE and MPI library,on one machine. I have been using gdb along with xterm to have two windows open at the same time as I step through the code. I wish to get a better glimpse of the working of the point to point calls, by

Re: [OMPI users] Can't compile C++ program with extern "C" { #include mpi.h }

2008-01-01 Thread Adam C Powell IV
On Mon, 2007-12-31 at 20:01 -0700, Brian Barrett wrote: > On Dec 31, 2007, at 7:26 PM, Adam C Powell IV wrote: > > > Okay, fair enough for this test example. > > > > But the Salomé case is more complicated: > > extern "C" > > { > > #include > > } > > What to do here? The hdf5 prototypes must be