This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
On Aug 18, 2005, at 5:34 PM, David Daniel wrote:
> On Aug 18, 2005, at 4:24 PM, Brian Barrett wrote:
>> On Aug 18, 2005, at 4:53 PM, David Daniel wrote:
>>> A question for those who did the ROMIO port...
>>> The ROMIO component seems to be based on version 126.96.36.199 (the last
>>> version of ROMIO released independently). Did anyone make any
>>> progress using the ROMIO from later MPICH's (version 1.2.6 etc.)?
>>> Seems to me these are fairly broken as far as compatibility with
>>> other MPIs is concerned.
>> Yes, we took the last stable individual release of ROMIO for OMPI.
>> We haven't looked at bringing in the MPICH-integrated releases. I'm
>> not sure how hard it will be to rip out the MPICH-specific stuff from
>> ROMIO, but at this point, it would take some work to replicate
>> everything we did to integrate ROMIO into OMPI. Is this a 1.0
> No -- Don't panic! The parallel I/O folks here are just interested in
> seeing whether there are fixes in later versions that would help with
> I was trying to port 1.2.6 into LA-MPI but it is painful (i.e.
> broken) with an MPI implementation that doesn't have MPI_Info
> defined. My guess is it will be easier with Open MPI.
Ok. It's something we're half looking at for 1.0, but it's going to
be really tight on schedule. Realistically, probably wouldn't fit in
the schedule for the 1.0 release, but would be doable for a SC release.
Open MPI developer