[Date Prev][Date Next] [Chronological] [Thread] [Top]
RE: EVEN YET MORE Problem building openldap

To: "Openldap (E-mail)" <openldap-software@OpenLDAP.org>
Subject: RE: EVEN YET MORE Problem building openldap
From: "North, Walter" <wnorth@state.mt.us>
Date: Fri, 9 Jan 2004 14:25:44 -0700
Thanks Vadim, I think I'm finally beginning to see the light,
maybe <grin>.

I got the berkeley db to show, but -lgssapi is not accepted either
from the LIBS in configure or from the environment.

So I decided to dump MIT kerberos and try Heimdal and have run into 
 problems with it during make. (v0.6)

About then I'm pretty frustrated with AIX so I moved the exact
same stuff to a tru64 v5.1b box and after a few miscues everything
is installed.  If it will run is a different matter but at least
it is there to start doing some configuring and testing.
(used HPs tru64 cc and make instead of gcc and gnu make)

Perhaps I need to install some stuff from the IBM OpenSource cd they
sent with the os.  I will dig around on that.

Investigations will continue since management insists that we will
buy AIX because it is the greatest thing since sliced bread and pop 
top beer cans.

..................

> -----Original Message-----
> From: Tarassov Vadim [mailto:Vadim.Tarassov@winterthur.ch]
> Sent: Friday, January 09, 2004 10:09 AM
> To: 'North, Walter'
> Subject: AW: EVEN YET MORE Problem building openldap
> 
> 
> Hi Walter,
> 
> you are almost through! Look yourself now in config.log:
> 
> configure:20794: checking for sasl_client_init in -lsasl2
> configure:20813: gcc -o conftest -g -O2 
> -I/usr/local/ssl/include -I/usr/local/BerkeleyDB.4.2/include 
> -I/usr/local/include -I/usr/local/include/sasl 
> -L/usr/local/ssl/lib -L/usr/local/BerkeleyDB.4.2/lib 
> -L/usr/local/lib -L/usr/local/lib/sasl2 conftest.c -lsasl2  
> -lssl -lcrypto -lsasl2 1>&5
> ld: 0711-224 WARNING: Duplicate symbol: sasl_global_utils
> ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain 
> more information.
> ld: 0711-317 ERROR: Undefined symbol: .gss_display_status
> ld: 0711-317 ERROR: Undefined symbol: .gss_release_buffer
> ld: 0711-317 ERROR: Undefined symbol: .gss_wrap
> ld: 0711-317 ERROR: Undefined symbol: .gss_unwrap
> ld: 0711-317 ERROR: Undefined symbol: .gss_release_cred
> ld: 0711-317 ERROR: Undefined symbol: .gss_release_name
> ld: 0711-317 ERROR: Undefined symbol: .gss_delete_sec_context
> ld: 0711-317 ERROR: Undefined symbol: .gss_accept_sec_context
> ld: 0711-317 ERROR: Undefined symbol: GSS_C_NT_HOSTBASED_SERVICE
> ld: 0711-317 ERROR: Undefined symbol: .gss_import_name
> ld: 0711-317 ERROR: Undefined symbol: .gss_acquire_cred
> ld: 0711-317 ERROR: Undefined symbol: .gss_wrap_size_limit
> ld: 0711-317 ERROR: Undefined symbol: .gss_display_name
> ld: 0711-317 ERROR: Undefined symbol: GSS_C_NT_USER_NAME
> ld: 0711-317 ERROR: Undefined symbol: .gss_compare_name
> ld: 0711-317 ERROR: Undefined symbol: .gss_init_sec_context
> ld: 0711-317 ERROR: Undefined symbol: .gss_inquire_context
> ld: 0711-317 ERROR: Undefined symbol: .db_create
> ld: 0711-317 ERROR: Undefined symbol: .db_strerror
> collect2: ld returned 8 exit status
> configure: failed program was:
> #line 20802 "configure"
> #include "confdefs.h"
> /* Override any gcc2 internal prototype to avoid an error.  */
> /* We use char because int might match the return type of a gcc2
>     builtin and then its argument prototype would still apply.  */
> char sasl_client_init();
> 
> int main() {
> sasl_client_init()
> ; return 0; }
> 
> 
> As you can see configure now founds everything from SSL, 
> gss_* symbols are from another library that I have mentioned, 
> from GSSAPI. Please also notice that berkeley DB libraries 
> are also missing as it writes 
> 
> ld: 0711-317 ERROR: Undefined symbol: .db_create
> ld: 0711-317 ERROR: Undefined symbol: .db_strerror
> 
> Therefore try LIBS="-lssl -lcrypto -lsasl2 -lgssapi 
> -ldb-4.2", and you'll get it!
> 
> Please use openldap mailing list, as I am not always 
> available under this email address.
> 
> Cheers, vadim tarassov.
> 
> 
> -----Ursprüngliche Nachricht-----
> Von: North, Walter [mailto:wnorth@state.mt.us]
> Gesendet: Freitag, 9. Januar 2004 17:54
> An: 'Tarassov Vadim'
> Betreff: RE: EVEN YET MORE Problem building openldap
> 
> 
> 
> 	Thank you Vadim,  I really appreciate the time you have taken to
> 	try and help me. 
> 
> 	I tried including the LIBS as you suggest.  It still looks to me
> 	as if it cannot find SASL but can find the rest.
> 
> 	I am sending you the config.log and the confdefs.h from 
> my failed
> 	attempt at configure in hopes you might have time to examine it
> 	further.
> 
> 	Setting LIBPATH and LIBS in my environment seems to make no
> difference
> 	as the environment appears to be ignored completely and 
> I have to
> add
> 	LDFLAGS and LIBS to the configure command line.
> 
> 	The configure I used is as follows:
> 
> CPPFLAGS="-I/usr/local/ssl/include -I/usr/local/BerkeleyDB.4.2/include
> -I/usr/local/include 
> -I/usr/local/include/sasl" LDFLAGS="-L/usr/local/ssl/lib
> -L/usr/local/BerkeleyDB.4.2/lib 
> -L/usr/local/lib -L/usr/local/lib/sasl2" LIBS="-lssl -lcrypto -lsasl2"
> ./configure 
> --with-threads=no --with-cyrus-sasl >/tmp/conf1.out
> 
> I use --with-cyrus-sasl so it will stop at the point it 
> claims to not find
> SASL.
> 
> I also agree with you about the problems making it work after 
> getting it
> compiled.
> But as you say at this point I'm just trying to get to that point.
> 
> I think I need a vacation!
> 
> I also looked at Howard Chu's suggestion to use a newer 
> libtool, I tried
> moving
> libtool over, but since it is created at configure I figured 
> it would do no
> good
> at make and I was right, I copied ltmain.sh and it did no 
> good.  It appears
> I
> could replace ltconfig in the sasl dist with the gnu libtool 
> but at this
> point
> I'm getting out of my depth.  Not to mention I feel I should 
> not have to
> mess
> around with a distribution so deeply.
> 
> thanks for you help.
> 
> > -----Original Message-----
> > From: Tarassov Vadim [mailto:Vadim.Tarassov@winterthur.ch]
> > Sent: Friday, January 09, 2004 6:28 AM
> > To: 'North, Walter'; Openldap (E-mail)
> > Subject: AW: EVEN YET MORE Problem building openldap
> > 
> > 
> > Hallo Walter,
> > 
> > I had to spend myself rather long time to figure out how to 
> > get OpenLDAP's configure to collect all libs. You are right 
> > saying that this particular version of configure is far from 
> > being handy. 
> > 
> > However, there are two thing which you have to take into account:
> > 
> > 1) As soon as you've got openssl, berkeley, sasl, and gssapi 
> > libs, it is only a metter of time and effort to make 
> > configure to find all of them. Configure does not check 
> > funcionality of these components, it only links all together 
> > and checks what linker returns. Which means that:
> > 
> > 2) you should pay attention to what Quanah said: after you've 
> > got configure to work it can be very possible that openldap 
> > will not work properly on your AIX with sasl and kerberos, 
> > however it is not your issue at the moment.
> > 
> > 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
> > 
> > Second option: fix configure script. Before trying to link 
> > configure script sets LIBS variable. Add -lcrypto and -lssl 
> > when it sets LIBS to "-lsasl2 $LIBS", or make sure that $LIBS 
> > has -lcrypto and -lssl always in it.
> > 
> > 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
> > 
> > ----------------------------------------------------- 
> > 
> 
>
Follow-Ups:
- RE: EVEN YET MORE Problem building openldap
  - From: Quanah Gibson-Mount <quanah@stanford.edu>
Prev by Date: Active Directory help
Next by Date: RE: EVEN YET MORE Problem building openldap
Index(es):
- Chronological
- Thread