FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Development

 
 
LinkBack Thread Tools
 
Old 03-10-2009, 03:29 PM
Jean Parpaillon
 
Default MPI binaries location

Hi,
I'm currently packaging hpcc (HPC Challenge Benchmark). Several binary
packages will be available, each one with different mpi implementations. Is
there a preferred place to put mpi binaries ? I've seen that each mpi
implementation has it's own bin/lib/share/include/etc hierarchy into
/usr/lib/<mpi>

Should I put the binaries into it ?


Regards,
--
Jean Parpaillon - Kerlabs
Engineer
B‚timent Germanium
80 avenue des buttes de CoŽsmes
35700 Rennes - France
Tel.: +33 6 80 332 73 85
http://www.kerlabs.com/
 
Old 03-10-2009, 07:47 PM
Geoff Jacobs
 
Default MPI binaries location

Jean Parpaillon wrote:
> Hi,
> I'm currently packaging hpcc (HPC Challenge Benchmark). Several binary
> packages will be available, each one with different mpi implementations. Is
> there a preferred place to put mpi binaries ? I've seen that each mpi
> implementation has it's own bin/lib/share/include/etc hierarchy into
> /usr/lib/<mpi>
>
> Should I put the binaries into it ?
>
>
> Regards,

Generally, a standalone issue of (for example) MPICH will put elements
in /usr/include, /usr/lib, /usr/bin, etc. On one-off servers where I
want multiple libraries available, everything is prefixed into a custom
directory under /usr/local (/usr/local/mpich-1.2.7, for example). At
first I used a homebrew script to switch between each, but this is now
possible using a more polished program. See http://modules.sf.net for
more. Note that this approach is important for cases where different
compilers are used. This is not a stipulated requirement in your note.

The prebuilt deb packages for OpenMPI, LAM, and MPICH are patched to
label the build scripts differently (mpicc becomes mpicc.lam) and
install the libraries and headers in subdirectories as well. Further
management is performed using the alternatives process. Perhaps such a
method would work for what you intend.

--
Geoffrey D. Jacobs


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 03-11-2009, 09:34 AM
Manuel Prinz
 
Default MPI binaries location

Hi Jean!

Am Dienstag, den 10.03.2009, 17:29 +0100 schrieb Jean Parpaillon:
> I'm currently packaging hpcc (HPC Challenge Benchmark). Several binary
> packages will be available, each one with different mpi implementations. Is
> there a preferred place to put mpi binaries ? I've seen that each mpi
> implementation has it's own bin/lib/share/include/etc hierarchy into
> /usr/lib/<mpi>
>
> Should I put the binaries into it ?

If MPI applications are build against multiple MPI implementations, the
usual way is to build binaries like hpcc.openmpi, hpcc.mpich, and so on
and use update-alternatives to provide /usr/bin/hpcc. [0]

If you'd like to look at an example, have a look at the gromacs source
package.

Best regards
Manuel

[0] Don't know about the actual executable name, but you'll get the
idea.
 

Thread Tools




All times are GMT. The time now is 11:13 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org