Hey Jim,
thanks for your response. I tried as you suggested....
lamboot mynodes
lamexec N env | grep LD_LIBR
and it only prints out one instance of the following?
LD_LIBRARY_PATH=/usr/local/lib:/usr/local/RTI-1.3NGv6/Linux-rh7.2-i386-gcc-3.0.2-opt-mt/lib:
Does this mean it's not seeing LD_LIBRARY_PATH at the other end? I'd
expect to see two version of the same $LD_LIBRARY_PATH printed? One for
each node?
as for step 2 if I redo the compile as follows...
mpic++ -L/usr/local/lib -lstdc++ hello.c
still have the same problem.
Thanks again
-Mike
Jim Procter wrote:
> No idea if this will help, but :
>
> On Tuesday 15 July 2003 16:39, Michael Lees wrote:
> <snip>
>
>>However I *don't* get the error if step 1.) becomes 'lamboot' or step
>>2.) becomes 'mpicc hello.c'
>>
>>ps. another note...
>>I also tried adding /usr/local/lib to /etc/ld.so.conf but still no joy?
>>
>
>
> Step 2 makes sense - you don't link in the missing library. Step 1 suggests
> that your schema is doing something funny to the library path...
>
> Try this :
>
> lamboot mynodes
> lamexec N env | grep LD_LIBR
>
> So you should see the same entry for LD_LIBRARY_PATH, everywhere. You could
> also do 'ldd' on the executable to see if the dependencies are all being
> resolved as the execution goes through the LAM demon.
>
> j.
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
|
