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: openmpi - a new MPI implementation https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=173719 ------- Additional Comments From orion@xxxxxxxxxxxxx 2006-02-16 00:21 EST ------- I have to second Ed's comments. I tried to shoe horn lam, mpich, and openmpi into an alternatives style system and it just doesn't fit. I might be acceptable to use it for binaries and have, for example: /usr/bin/mpif77.{name} /usr/bin/mpirun.{name} ... with alternatives for those, but not for anything else. Everything else should be in: /usr/include/{name} /usr/lib/{name} /usr/share/{name}/man ... with environment-modules files to select. There are still unresolved issues though: - Do we still want a default implementation accessible with no configuration by the user? If so, how to update /etc/ld.so.conf.d/ to point to the various libraries, or do we instead load a particular module (how?). - Can we guarantee that different mpi programs get the proper set of libraries when started remotely? - Others? Ed - do most places get around the library issues by linking statically? -- Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. -- fedora-extras-list mailing list fedora-extras-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-extras-list
