On 09/02/08 22:56 -0800, Donnie Berkholz wrote:
...
> > 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) ?
>
Yup, it's actually grabbed during the addition of the implementation to
eselect-mpi.
> > 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.
>
That's the general idea, however it's not as simple as just setting *into
unless I mess with $D first. The plan being to have something like mpi_doX
which would handle setting the correct install path and restore global
variables (like $D) on exit. Not sure if this is the best method, comments
appreciated :)
> > 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.
>
Not yet, it's being hosted off my home machine which doesn't always have the
best connection. If a consensus can be reached that this is a worthy
solution, I presume I can talk to the overlay/infra guys then, or maybe even
the sci team who already has an overlay with some MPI applications in it.
Thanks,
--
Justin Bronder
|
