[Date Prev][Date Next] [Chronological] [Thread] [Top]

RE: sasl version mismatch: 2.1.15 vs 2.1.17

> -----Original Message-----
> From: owner-openldap-software@OpenLDAP.org
> [mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of Andreas

> I compiled openldap 2.1.23 with sasl-2.1.17, everything went fine.
> Then, for other reasons, I had to downgrade sasl back to 2.1.15 on
> my machine, and openldap stopped working:
> slapd[22753]: slap_sasl_init: SASL version mismatch, got
> 201000f, wanted 2010011.
> So, is openldap just being pedantic or are there real
> incompatibilities
> between sasl 2.1.15 and 2.1.17?
> If these two versions are not compatible, shouldn't at least
> the soname be changed?
> (A question for the SASL folks, I know).

It would seem that both questions are for the SASL folks.

The point is that the code you're running with is not the code you compiled
against, and any number of APIs and data structures *may* have changed.
Whether they *have* changed or not is irrelevant, we're not going to sift
thru every line of 3rd party code to discover that. It is usually safe to run
code compiled with older headers against a newer version of a library. It is
seldom safe to run code compiled with newer headers against an older version
of that library. Call that pedantic if you like, I think it's common sense.

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support