On Feb 11, 2010, at 4:45 PM, Rainer Keller wrote: > Hi Ralph, > hmm, I don't really care about the name itselve. > As Jeff mentioned, we'd have a "abstraction break" either way.
There is no abstraction break - I talked to Jeff about it and cleared up the confusion. The OMPI code will have an install line that installs the opal file in a to-be-determined place where mpi.h can include it. No "mpi" references required in OPAL. > > The question I have, why does orte_info need to include the information, > which > compiler it was compiled with ;-)? Because people create cross-compiled versions, use module files to define which one they are using, etc. > > We basically only care to warn users about a typical MPI-user compilation > mismatch (C gcc+ Fortran pgf77). Not quite correct - you need to know that it was built to cross-compile vs native. HTH Ralph > > So, I would rather keep it as is... > > > Regards, > Rainer > > > > On Thursday 11 February 2010 12:33:28 pm Ralph Castain wrote: >> WHAT: Rename ompi/include/mpi_portable_platform.h to be >> opal/include/opal_portable_platform.h >> >> WHY: The file includes definitions and macros that identify the compiler >> used to build the system, etc. The contents actually have nothing specific >> to do with MPI. >> >> WHEN: Weekend of Feb 20th >> >> >> >> I'm trying to rationalize the ompi_info system so that people who build >> different layers can still get a report of the MCA params, build >> configuration, etc. for the layers they build. Thus, there would be an >> "orte_info" and "opal_info" capability. Each would report not only the >> info for their own layer, but the layer(s) below. So ompi_info remains >> unchanged, orte_info reports ORTE and OPAL info, etc. >> >> The problem I encountered is that the referenced file is required for the >> various "info" tools, but it exists in the MPI layer. Since the file is >> only accessed at build time, I can go ahead and reference it from within >> "orte_info" and "opal_info", but it does somewhat break the abstraction >> barrier to do so. >> >> Given that the info in the file has nothing to do with MPI itself, it >> seemed reasonable to move it to opal...barring arguments to the contrary. >> >> Ralph >> >> >> _______________________________________________ >> devel mailing list >> de...@open-mpi.org >> http://www.open-mpi.org/mailman/listinfo.cgi/devel >> > > -- > ------------------------------------------------------------------------ > Rainer Keller, PhD Tel: +1 (865) 241-6293 > Oak Ridge National Lab Fax: +1 (865) 241-4811 > PO Box 2008 MS 6164 Email: kel...@ornl.gov > Oak Ridge, TN 37831-2008 AIM/Skype: rusraink >
