> A runtime dlopen is different than being linked against a > library, and yes in this case you would now have to > dlopen(libdat2.so) and if that fails fall back to > (libdat.so). However, given that according to the > dapl-1 to dapl-2 porting guide there are several structures > that have changed their layout between dat-1 and dat-2, I > would think that HP-MPI would have to jump through hoops > (either by knowing about both layouts, or by knowing what > structures to avoid because they change) in order to support > working with either dat-1 or dat-2 at runtime. If anything, > that would make me think this is a good example of why they > *should* be different library names.
If there is a way to seamlessl work on either version available on the system without asking user for choice, I am OK to change the library name. According what you said, we can dlopen(libdat2.so) first, then fallback to dlopen(libdat.so). But we have to claim that HP-MPI xxx version and older does not work with uDAPL 2.0. Currently HP-MPI works seamlessly on uDAPL 1.1 or uDAPL 1.2 system. --CQ > > --CQ > > > > > > > > > > > > -arlin > > > > > > > > > _______________________________________________ > > > general mailing list > > > [email protected] > > > http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general > > > > > > To unsubscribe, please visit > > > http://openib.org/mailman/listinfo/openib-general > > > > -- > Doug Ledford <[EMAIL PROTECTED]> > GPG KeyID: CFBFF194 > http://people.redhat.com/dledford > > Infiniband specific RPMs available at > http://people.redhat.com/dledford/Infiniband > _______________________________________________ general mailing list [email protected] http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
