[Rd] Rmpi on CentOS (64bit)
Patrick Connolly
p_connolly at slingshot.co.nz
Sat Mar 6 06:42:44 CET 2010
On Wed, 03-Mar-2010 at 07:53PM +1300, Patrick Connolly wrote:
|> I got Rmpi to compile with little difficulty, but had a tricky time
|> setting the LD_LIBRARY_PATH to use the OpenMPI libs. I now get a
|> different error when I try to load Rmpi
|>
|>
|> > require(Rmpi)
|> Loading required package: Rmpi
|> librdmacm: couldn't read ABI version.
|> librdmacm: assuming: 4
|> libibverbs: Fatal: couldn't read uverbs ABI version.
|> CMA: unable to open /dev/infiniband/rdma_cm
|> --------------------------------------------------------------------------
|> WARNING: Failed to open "OpenIB-cma" [DAT_INTERNAL_ERROR:].
|> This may be a real error or it may be an invalid entry in the uDAPL
|> Registry which is contained in the dat.conf file. Contact your local
|> System Administrator to confirm the availability of the interfaces in
|> the dat.conf file.
|> --------------------------------------------------------------------------
I looked further into this uDAPL thing and found an FAQ:
http://www.open-mpi.org/faq/?category=udapl
This one was particularly interesting:
3. Where is the static uDAPL Registry found?
Solaris: /etc/dat/dat.conf
Linux: /etc/dat.conf
On my CentOS installation, I have two, neither of which is where it's
supposed to be for "Linux" in the opinion of open-mpi.org.
$ locate dat.conf
/etc/ofed/dat.conf
/etc/ofed/compat-dapl/dat.conf
/usr/share/man/man5/dat.conf.5.gz
Would there be a way at the time of compiling Rmpi to specify a
configure arg to use one or other of the ones I have? Or would it be
simpler to make a link in /etc/ to one or other of them? Is there any
danger that such a link could bother anything else?
best
--
~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.
___ Patrick Connolly
{~._.~} Great minds discuss ideas
_( Y )_ Average minds discuss events
(:_~*~_:) Small minds discuss people
(_)-(_) ..... Eleanor Roosevelt
~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.
More information about the R-devel
mailing list