From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-cluster@lists.gentoo.org
Subject: Re: [gentoo-cluster] Installing and using multiple MPI implementations at the same time.
Date: Sat, 9 Feb 2008 22:56:06 -0800 [thread overview]
Message-ID: <20080210065605.GA16842@comet.romhat.net> (raw)
In-Reply-To: <20080208031923.GA27361@mejis.cold-front>
On 22:19 Thu 07 Feb , Justin Bronder wrote:
> Well bug 44132 [1] has been a real thorn in my side for some time. The
> problem being that all mpi implementations currently in portage block each
> other. This is a real pain for any serious administrators, makes testing
> new/other implementations too time-consuming, and in my opinion has probably
> slowed any progress related to getting cluster applications into portage or
> the overlays.
>
> All that being said, I set out to do something about it. Donnie Berkholz was
> nice enough to help me out early on and ended up suggesting that I look
> at crossdev. I shamelessly ripped off the aforementioned script and tuned
> it for mpi implementations and packages. It should be noted that all the
> changes I've implemented do [should, hopefully will] not effect the way the
> packages behave now, rather it just adds another option. The idea is as
> follows.
Cool, thanks for doing this much-needed work! I'm happy to hear this
approach worked. If there really is much common code, it might be worth
breaking it out into a library of some sort.
> sys-cluster/empi: Does the same stuff that crossdev does. You create a new
> implementation root by specifying a name and mpi implementation package to
> build it with. [2] Empi adds these to an overlay under a new category with
> the name you gave. The ebuilds inherit mpi.eclass which handles pushing all
> the files to /usr/lib/mpi/<name>, and providing files for eselect-mpi.
lib == $(get_libdir) ?
> A couple of final words, hpl and mpi-examples currently wouldn't work without
> empi, mainly because I'm lazy :) Also I still haven't figured out a good way
> to handle do{man,doc,www} etcetera, ideas are welcome.
Do the same thing as gcc. Install to a path under
/usr/libdir/mpi/..../{man,doc} and use environment variables (MANPATH
etc) and/or symlinks.
> There's still a fair amount of work to be done, but I wanted to see if
> anyone had any feedback regarding the general concept first before
> pushing on.
>
> You can pull the overlay from rsync://cold-front.ath.cx/mpi (for now...)
Is this in layman? The file's at
gentoo/xml/htdocs/proj/en/overlays/layman-global.txt.
Thanks,
Donnie
--
gentoo-cluster@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-02-10 6:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 3:19 [gentoo-cluster] Installing and using multiple MPI implementations at the same time Justin Bronder
2008-02-10 6:56 ` Donnie Berkholz [this message]
2008-02-11 14:32 ` [gentoo-cluster] " Justin Bronder
2008-03-10 16:31 ` [gentoo-cluster] " Alexander Piavka
2008-03-11 1:07 ` [gentoo-cluster] " Justin Bronder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080210065605.GA16842@comet.romhat.net \
--to=dberkholz@gentoo.org \
--cc=gentoo-cluster@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox