"ldd on a file" simply means run ldd on it. ldd will show you what dynamic libraries the executable or library will link against at runtime.
If no output is displayed, it means the file in question was linked to static libraries; and in your case might not be linking with the libtotalview.so library.
-----Original Message-----
From: Ilya Lashuk [mailto:ilashuk_at_[hidden]]
Sent: Wednesday, March 16, 2005 14:11
To: General LAM/MPI mailing list
Subject: Re: LAM: lam 7.1.1 & totalview 6.7.0.1 - warning at startup and
no message queue visible
Jeff Squyres wrote:
> On Mar 9, 2005, at 1:08 PM, Ilya Lashuk wrote:
>
>>>> i'm trying to use totalview 6.7.0.1 with lam 7.1.1, but it seems i
>>>> can't access mpi message queue from totalview for some reason.
>>>
>>>
>>> How did you install LAM/MPI? From compiling a tarball or from the RPM?
>>
>>
>> From compiling a tarball.
>
>
> Hum. That's quite odd. Can you send the output of "make" from when
> you built LAM/MPI? I'd like to see how it built the totalview
> library. It *shouldn't* be stripped. Also check that it was
> installed properly -- look in $prefix/lib/lam -- do you see
> liblam_totalview.so.0.0.0 in there? What do you get when you run file
> and ldd on it?
Attached is make output. Here's the list of files in $prefix/lib/lam:
liblam_totalview.la liblam_totalview.so liblam_totalview.so.0
liblam_totalview.so.0.0.0
Sorry, i don't know what "ldd on file" means - please tell me. If you
are asking what happens when i try to run the program in debugger, the
answer is that everything goes OK till the program goes parallel, and at
that point a warning "The library could not find the type definition of
struct _proc in libmpi" appears. After this warning most debugging
features work, but message queue viewer doesn't. I start totalview with
"mpirun -tv -np 2 myprog"
|
