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 orion@xxxxxxxxxxxxx changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dledford@xxxxxxxxxx ------- Additional Comments From orion@xxxxxxxxxxxxx 2008-04-16 15:28 EST ------- (In reply to comment #63) > (In reply to comment #62) > > > mpich2-devel.i386: W: symlink-should-be-relative > > /usr/share/mpich2/bin32/mpif90/usr/bin/mp32-mpif90 > > (and same for mpif77, mpicc, mpicxx). > > > I've fought with this in the past, I can't find a means of dealing with it > sanely, suggestions welcomed. I believe it can be ignored. > > > Lots of: > > > > mpich2-libs.i386: W: conffile-without-noreplace-flag > > /etc/mpich2-32/mpe_callstack_ldflags.conf > > > I think these can be safely ignored too, as most of them are constructed at > build-time. See the patch I'll be attaching to fix these, and do proper line wrapping of the description. > Good point. It seems you've not noticed I did enabled dynamically loading sock, > ssm, and shm channels; the default is still the sock channel though. > I'm actually considering configuring the package to use ch3:nemesis on x86*, > since it said to offer the best performance, thoughts? Hadn't notice, but that's nice. Can you build nemesis as another option but not as the default? Otherwise, I'd skip it for now. > > Another thing to think about it who should take precedence among lam, openmpi, > > and mpich2 when they are all installed. > > It really shouldn't matter, anyone who will knowingly install the three, should > be knowledgeable enough to set the default implementation, IMHO. Willing to agree, but I'm going to CC the lam/openmpi maintainer to get his take. -- 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. _______________________________________________ Fedora-package-review mailing list Fedora-package-review@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-package-review