[R-sig-hpc] Problems Installing Rmpi on openSUSE 11.1 x86_64

[Rowe, Brian Lee Yung (Portfolio Analytics)]

Hi Melwin,

A couple additional points:
1. mpicc is available in LAM/MPI as well, so you ought to try using that to compile Rmpi
2. Are you talking about spawning R slaves across multiple machines from within an interactive R session? This is quite possible in OpenMPI, as I do this regularly. When calling R directly, you are limited to spawning slaves on the same host as the master. If you use mpirun to start R (still interactive session), you can launch slaves on remote hosts as well. The main issue with OpenMPI is that the R processes utilize 100% of the processor that it was initialized on. For certain environments, this may not be acceptable.

HTH,
Brian


-----Original Message-----
From: r-sig-hpc-bounces at r-project.org [mailto:r-sig-hpc-bounces at r-project.org] On Behalf Of Melwin
Sent: Friday, June 26, 2009 3:13 AM
To: r-sig-hpc at r-project.org
Subject: Re: [R-sig-hpc] Problems Installing Rmpi on openSUSE 11.1 x86_64


Thanks for the reply.

2009/6/24 Rowe, Brian Lee Yung (Portfolio Analytics) <B_Rowe at ml.com>:
> Did you confirm that your MPI installation is working? That is the
> probably the first step.
LAM seems to work ok:
   johnson at linuxmodel:~> lamboot -v

   LAM 7.1.4/MPI 2 C++/ROMIO - Indiana University

   n-1<4165> ssi:boot:base:linear: booting n0 (localhost)
   n-1<4165> ssi:boot:base:linear: finished
   johnson at linuxmodel:~> lamexec C hostname
   linuxmodel


> Regarding LD_LIBRARY_PATH, since I don't know what your configuration
> is, make sure you export it to your environment and also don't overwrite
> any existing values.
>  i.e. This is better:
>  $ export LD_LIBRARY_PATH=/usr/lib64:$LD_LIBRARY_PATH
> since it looks like you're on a 64 bit platform.

Tried that. Same results as before:
   johnson at linuxmodel:~>     R CMD INSTALL Rmpi_0.5-7.tar.gz
   * Installing to library  
'/home/johnson/R/x86_64-unknown-linux-gnu-library/2.8'
   * Installing *source* package 'Rmpi' ...
   checking for gcc... gcc
   checking for C compiler default output file name... a.out
   checking whether the C compiler works... yes
   checking whether we are cross compiling... no
   checking for suffix of executables...
   checking for suffix of object files... o
   checking whether we are using the GNU C compiler... yes
   checking whether gcc accepts -g... yes
   checking for gcc option to accept ISO C89... none needed
   I am here /usr
   Try to find mpi.h ...
   Found in /usr/include
   Try to find libmpi.so or libmpich.a
   checking for main in -lmpi... no
   libmpi not found. exiting...
   ERROR: configuration failed for package 'Rmpi'
   ** Removing '/home/johnson/R/x86_64-unknown-linux-gnu-library/2.8/Rmpi'

> I use OpenMPI and it include an mpi-based compiler which I found to work
> better than gcc directly. You might try that. Just make sure you export
> your MPI_ROOT.
I would love to use OpenMPI, but I gather the slave spawning from within R  
is not yet possible - which is what I need in interactive mode  
(https://stat.ethz.ch/pipermail/r-sig-hpc/2009-February/000104.html). I'd  
love to hear that this has changed.

> It would also probably help to include a bit more output
> from the compilation process.
The dump above contains the entire output, I hope that helps.

thanks again,
Melwin

_______________________________________________
R-sig-hpc mailing list
R-sig-hpc at r-project.org
https://stat.ethz.ch/mailman/listinfo/r-sig-hpc

--------------------------------------------------------------------------
This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing.
--------------------------------------------------------------------------