On Tue, 2008-01-29 at 22:24 +0000, Tang, Changqing wrote: > devel environments are just runtimes plus header files,
Actually, the runtime is in the base package. The devel package is headers plus a bare .so link (aka, libdat.so -> libdat.so.2). It's the bare .so links that overwrite each other. The last thing you want is to have an application that has #include <dat/dat.h> then link against -ldat and have that bare .so link point to the dapl-2 library because you will then be using the wrong header files with the shared object. Hence why I'm solving the issue the way I am in our release. > so the libraries won't overwrite each other, but header files will ? > > --CQ > > > -----Original Message----- > > From: Doug Ledford [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, January 29, 2008 4:03 PM > > To: Tang, Changqing > > Cc: Arlin Davis; general > > Subject: RE: [ofa-general] Re: Dapl 2 question/issue > > > > > > On Tue, 2008-01-29 at 21:57 +0000, Tang, Changqing wrote: > > > So can we install both v1 and v2 packages on a system ? At > > the install time, we don't know the app will run on v1 or v2. > > > > Currently, you can install both runtimes, but not both devel > > environments. > > > > > --CQ > > > > > > > -----Original Message----- > > > > From: Arlin Davis [mailto:[EMAIL PROTECTED] > > > > Sent: Tuesday, January 29, 2008 3:46 PM > > > > To: Doug Ledford > > > > Cc: Tang, Changqing; general > > > > Subject: Re: [ofa-general] Re: Dapl 2 question/issue > > > > > > > > Doug Ledford wrote: > > > > > > > > > > You *should* be claiming that regardless. The API between > > > > dapl-1 and > > > > > dapl-2 changed, some of which is fixed simply be > > > > recompiling and some > > > > > of which requires actual code changes. Just because the > > > > library name > > > > > is the same doesn't mean that code built and compiled > > > > against dapl-1 > > > > > could or should attempt to run against dapl-2 (unless I'm > > > > wrong here, > > > > > Arlin should really speak to this issue...if the dapl-2 > > libraries > > > > > provide backward compatible symbols via so symbol > > versions, then > > > > > it might be possible for a dapl-1 program to run against the > > > > > dapl-2 library, but then that would beg the question of > > why we are > > > > > still distributing dapl-1 libraries in a separate > > package, so I'm > > > > guessing > > > > > there is not a back compatible layer in the dapl-2 library). > > > > > > > > You are correct. dapl-1 programs cannot run against dapl-2. > > > > That is why both v1 and v2 packages are provided. We have > > to support > > > > existing v1 applications while providing a transition path to v2. > > > > > > > > -arlin > > > > > > > > > > -- > > Doug Ledford <[EMAIL PROTECTED]> > > GPG KeyID: CFBFF194 > > http://people.redhat.com/dledford > > > > Infiniband specific RPMs available at > > http://people.redhat.com/dledford/Infiniband > > -- Doug Ledford <[EMAIL PROTECTED]> GPG KeyID: CFBFF194 http://people.redhat.com/dledford Infiniband specific RPMs available at http://people.redhat.com/dledford/Infiniband
signature.asc
Description: This is a digitally signed message part
_______________________________________________ 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
