On Thu, Feb 21, 2008 at 09:26:25AM -0600, Dirk Eddelbuettel wrote: > You can do what I did for Rmpi and use Open MPI where available and LAM where > not:
> Build-Depends: debhelper (>> 4.1.0), cdbs, r-base-dev (>= 2.6.0), \ > libopenmpi-dev (>= 1.2.4-5) [i386 amd64 alpha ia64 powerpc sparc], \ > lam4-dev [!i386 !amd64 !alpha !ia64 !powerpc !sparc] > Nothing wrong with that. I think a portable solution would be better. > | Why not use libatomic-ops which includes atomic primitives for all > | supported architectures and more? > Are you sure that these atomic ops are the one mssing in Open MPI? Could you > provide a proof of concept for one arch so that I could take that to upstream? I don't really know anything about openmpi internals, but looking at atomic-powerpc32-linux.s all but opal_sys_timer_get_cycles have similar definitions in libatomic-ops-dev. -- "rm -rf" only sounds scary if you don't have backups
signature.asc
Description: Digital signature
