Brian and I chatted about this on the phone today. Conclusions that
we came to:
1. We need to add a few lines of code to ensure that the MCA base
refuses to open components that have a different MCA version number
(i.e., dlopen a DSO, dlsym to get the component struct, check the
version
On Jul 21, 2008, at 6:57 PM, Brian W. Barrett wrote:
I guess I don't understand. I thought there were three versions in
every
component -- the MCA version, the framework version, and the component
version. The first two should determine if the component can safely
be
loaded and the third i
> After starting, we decided that changing the MCA base revision number
> to 2.0.0 also meant changing *ALL* the framework version numbers.
> This is because the same components from framework compiled with
> MCA base version 1.x.x would not be binary compatible when compiled
> with MCA b
Short version:
==
MCA base component changes were a bit more extensive than we
anticipated. Please test the following hg tree on your systems before
we bring it into the SVN trunk this Friday evening:
http://www.open-mpi.org/hg/hgwebdir.cgi/jsquyres/mca-base-updates/
Longe
