On Tue, 8 Jul 2003, Michael Lees wrote:
> I had lam 6.5.9 installed but wanted to upgrade.
> My machine is red hat 8.0 with gcc 3.02 installed.
>
> As suggested in the nice new installation guide I've gzipped the error
> logs from configure and attached them.
Most excellent. Helps find the problems easily! :-)
The specific problem that occurred is the following:
-----
configure:7863: ./conftest
./conftest: error while loading shared libraries: libstdc++.so.3: cannot
open shared object file: No such file or directory
configure:7866: $? = 127
-----
Hence, the test program compiled ok, but was unable to run because it
couldn't find a shared library. So either your LD_LIBRARY_PATH isn't set
right, or ld.so.conf file needs to be appended to say where that shared
library is.
Perhaps this means a missing RPM? It's kinda sketchy, because the program
was apparently linked to this when it was compiled/linked, but just wasn't
able to find it when it ran. Hmm.
> It's slightly strange but I've also tried using the rpm source and that
> seems to install okay. The only problem is I need to use ssh rather than
> rsh. I know how to configure this using configure --with-rsh="ssh -x"
> but not sure how to do it at run time? It says this is possible in the
> user manual, could someone please explain how?
The easiest way is to do it at compile-time with --with-rsh=ssh (-x is
typically only necessary for older versions of ssh). You can use the
"boot_rsh_agent" SSI variable at run-time, if you'd like.
--
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/
|
