RE: EVEN YET MORE Problem building openldap

["Howard Chu" <hyc@highlandsun.com>]

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

> Now back to your trouble. In the last email you have sent me
> to my another address you've mentioned that linker could not
> resolve symbols like EVP_* and gss_*. First sort of symbols
> is defined in libcrypto, the rest in gssapi library. I also
> think there were symbols from libssl library unresolved.
>
> First option: add additional environmental variable LIBS in
> to the command line where your could include -lcrypto -lssl
> and another one for gssapi: like
>
> LDFLAGS="whatsoever" CPPFLAGS="whatsoever" LIBS="-lcrypto
> -lssl" ./configure --bla-bla

This is the standard method of getting configure going. You're expected to
know to do this, since it's in the INSTALL document. Yes, you're expected to
actually read the documentation.

> Second option: fix configure script.

The configure script isn't broken, although your build environment may well
be. If your libsasl2 is a shared library, then it should already have its own
dependencies on libcrypto and pull it in automatically. If it's not a shared
library, then you have to explicitly add the dependencies as above. Generally
these dependent libraries (libsasl2, libssl, libgssapi) are built as shared
libraries on most supported platforms. However, in the case of Cyrus SASL,
their bundled libtool script is extremely old and useless, and typically
fails to produce shared objects because it doesn't handle inter-library
dependencies. You're better off using the libtool script that the OpenLDAP
build generates to build SASL. (I.e., libtool 1.4.3 vs libtool 1.3.5 that
Cyrus bundles.) There is definitely a fault here, but it's in the Cyrus SASL
distribution.

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

> best regards, vadim tarassov.
>
> -----Ursprüngliche Nachricht-----
> Von: North, Walter [mailto:wnorth@state.mt.us]
> Gesendet: Donnerstag, 8. Januar 2004 21:08
> An: Openldap (E-mail)
> Betreff: EVEN YET MORE Problem building openldap
>
>
>
> Thanks to
>
> Vadim Tarassov (and others whose email I inadvertanly erased thus
> 	losing their names) who pointed out some things for me to check
> Quanah Gibson-Mount who informed me of kerb 5 issues and recommends
> 		heimdal 0.6
> Dieter Kluenter who told me I needed cyrus sasl 2.1.16 at least
> 	(I found 2.1.17 and used it)
>
> Unfortunately it still does not find the SASL libraries which
> are in /usr/local/lib  libsasl2.a & libsasl2.1a
>
> For some reason even tho I include /usr/local/lib in the
> LDFLAGS and / or
> in the LIBPATH the ./configure cannot find it.
>
> AFter all the suggestions and help it seems to come down to some
> problem between configure (or something) in the openldap dist and
> AIX v5.2.
>
> At this point I'm out of ideas as my knowledge of C is not great
> enough to try to get /usr/local/lib in there.
>
> Since I have had to put the include dirs and lib dirs in the CPPFLAGS
> and LDFLAGS to get openssl, BerkeleyDB and anything else I wanted
> on openldap is it possible something like libtool is busted as far
> as working with AIX v5.2 is concerned?
>
> Has anyone out there actually gotten openldap with sasl to compile
> for AIX v5.2?
>
> Color me Stumped.....
>
>
> -----------------------------------------------------
> Walter North 406-444-2914
> Operating Systems Programmer
> wnorth (at) state (dot) mt (dot) us
>
> -----------------------------------------------------
>
>