[Bug 171993] Review Request: mpich2 - An implementation of MPI

bugzilla at redhat.com bugzilla at redhat.com
Wed Apr 16 22:16:22 UTC 2008


Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: mpich2 -  An implementation of MPI


https://bugzilla.redhat.com/show_bug.cgi?id=171993





------- Additional Comments From dakingun at gmail.com  2008-04-16 18:16 EST -------
(In reply to comment #66)
> I should note that I've made significant changes to lam/openmpi that aren't
> reflected in Fedora yet.  The most important of which is dumping the
> alternatives usage entirely.  It has proven to be unwieldy at best, a nightmare
> at worst.  Instead, my current packages use mpi-selector.  You can find
> mpi-selector, openmpi, and lam packages for the upcoming rhel5.2 release that
> demonstrate what I'm talking about (and intending to bring into fedora after f9
> is released) at my Infiniband package page:
> 
> http://people.redhat.com/dledford/Infiniband/rhel5.2
> 
I'll work on implementing it for mpich2 once its available in fedora.

> Also of note is that, in line with the comments in comment #7 and comment #8, my
> current packages use %{_libdir}/%{name} as the prefix for all files in the lam
> package, and %{_libdir}/%{name}/%{version}-%{opt_cc} as the prefix for all files

Do you actually ship openmpi with multiple versions and compilers on RHEL? I saw
your use of the %{opt_cc} sometimes ago and copied it for mpich2, but I don't
think its necessary for Fedora builds, as one can build with gcc and we can only
carry a version at a time. I believe the second option in comment #7 (which is
what I'm using now) works fine for the multilib situation, which is farthest
multiple instance Fedora can allow now.  

> in openmpi (the difference being because I've never been given any requests to
> have more than one version or compiler of lam installed at a time, but I have
> been given requests to have multiple versions and multipler compilers of openmpi
> at the same time).
> 
> Another item of note is that I have outstanding requests to also include
> mvapich/mvapich2 in the distro for use over infiniband.  I've not gotten any
> requests for mpich, but then I'm not fully aware of the relationship between
> mpich and mvapich.

mvapich is one of several other projects that are built on top of mpich2. There
is no reason why it can be packaged/shipped independently of mpich2.



-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.




More information about the package-review mailing list