That's it! It works. When I make export I don't have to even start from /usr/.../mpirun, plan "mpirun" do the work. Now I have to make that PATH to be like that all the time... hmm...
Thanks a lot :) much appreciate it :) 2010/5/24 Jeff Squyres <jsquy...@cisco.com>: > On May 24, 2010, at 12:06 PM, Dawid Laszuk wrote: > >> > What's the output from "ldd hello_c"? (this tells us which libraries it's >> > linking to at run-time -- from your configure output, it should list >> > /usr/local/lib/libmpi.so in there somewhere) >> >> kretyn@kretyn-laptop ~/Pobrane/openmpi-1.4.2/examples $ ldd hello_c >> linux-vdso.so.1 => (0x00007ffffbdbe000) >> libmpi.so.0 => /usr/lib/libmpi.so.0 (0x00007f5c7ba1e000) >> libopen-rte.so.0 => /usr/lib/libopen-rte.so.0 (0x00007f5c7b7d6000) >> libopen-pal.so.0 => /usr/lib/libopen-pal.so.0 (0x00007f5c7b563000) > > This seems to be the problem -- it's pointing to the "wrong" libmpi (and > friends). > > Ensure that you're using /usr/local/bin/mpicc to compile your apps. Then you > might also want to prefix the LD_LIBRARY_PATH environment variable with > /usr/local/lib to ensure that you pick up your local Open MPI installation > libraries (instead of the ones in /usr/lib). > > For example: > > export LD_LIBRARY_PATH=/usr/local/lib:$LD_LIBRARY_PATH > /usr/local/bin/mpicc hello_c.c -o hello_c -g > /usr/local/bin/mpirun -np 4 hello_c > > Try that. > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > > _______________________________________________ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users > -- Pozdrawiam, Dawid Laszuk
