[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
RE: Install failure on AIX of openldap-2.1.30
- To: <openldap-software@OpenLDAP.org>
- Subject: RE: Install failure on AIX of openldap-2.1.30
- From: "Chapman, Kyle" <Kyle_Chapman@G1.com>
- Date: Thu, 3 Jun 2004 17:38:02 -0400
- Content-class: urn:content-classes:message
- Importance: normal
- Thread-index: AcRJrWX1VHyUPjnFS9Wt3px4YkEmmgABu/6g
- Thread-topic: Install failure on AIX of openldap-2.1.30
you can also build shared libs after you build without shared support... its a pain but it works.
-----Original Message-----
From: Donn Cave [mailto:donn@u.washington.edu]
Sent: Thursday, June 03, 2004 4:50 PM
To: openldap-software@OpenLDAP.org
Subject: Re: Install failure on AIX of openldap-2.1.30
On Thursday, June 3, 2004, at 12:41 PM, Bennett, Tony - CNF wrote:
> I just downloaded, configured, made, and installed 2.1.30.
>
> It appears that libtool is not correctly building
> executables, on AIX 5.1.
...
> ./configure --with-cyrus-sasl \
> --enable-bdb \
> --with-kerberos
If shared libraries aren't essential for some reason, I would
--disable-shared --enable-static
I actually do this for all platforms, but particularly on AIX
that's going to avoid an extra set of problems that I have
no interest in resolving. It may also be interesting, if you're
more interested in it, to edit link commands from your log and
re-issue them. Remove the usual duplicate liblber.a, for
example, or any parameter that seems gratuitous or whose
purpose is not obvious.
For what it's worth, I also --disable-ipv6, and I suppose you
know that --with-kerberos isn't needed for GSSAPI-Kerberos
SASL authentication.
Donn Cave, donn@u.washington.edu
NOTICE: This E-mail may contain confidential information. If you are not
the addressee or the intended recipient please do not read this E-mail
and please immediately delete this e-mail message and any attachments
from your workstation or network mail system. If you are the addressee
or the intended recipient and you save or print a copy of this E-mail,
please place it in an appropriate file, depending on whether
confidential information is contained in the message.