Ralph Castain via users <users@lists.open-mpi.org> writes: > Just a point to consider. OMPI does _not_ want to get in the mode of > modifying imported software packages. That is a blackhole of effort we > simply cannot afford.
It's already done that, even in flatten.c. Otherwise updating to the current version would be trivial. I'll eventually make suggestions for some changes in MPICH for standalone builds if I can verify that they don't break things outside of OMPI. Meanwhile we don't have a recent version that will even pass tests recommended here, and we've long been asking about MPI-IO on lustre. We probably should move to some sort of MPICH for MPI-IO on probably the most likely parallel filesystem as well as RMA on the most likely fabric. > The correct thing to do would be to flag Rob Latham on that PR and ask > that he upstream the fix into ROMIO so we can absorb it. We shouldn't > be committing such things directly into OMPI itself. It's already fixed differently in mpich, but the simple patch is useful if there's nothing else broken. I approve of sending fixes to MPICH, but that will only do any good if OMPI's version gets updated from there, which doesn't seem to happen. > It's called "working with the community" as opposed to taking a > point-solution approach :-) The community has already done work to fix this properly. It's a pity that will be wasted. This bit of the community is grateful for the patch, which is reasonable to carry in packaging for now, unlike a whole new romio.
