hmm, this is recurring :-)
yes, it would be nice if it would be fixed :-)
Stefan Neis answer to my question about the same problem:
-----------------------------------------------------------------------------------------
> >The problem seems to be, again, that even one adds
> >> >--with-ltdl-lib=/opt/csw/share/libtool/libltdl
> >> >--with-ltdl-include=/opt/csw/share/libtool/libltdl
> >"make" does not seem to care about it.
>
>
> I've found this to be the case with several (if not all) of the
> --with-BLAH-lib and with --with-BLAH-include options.
A relatively easy way around that problem would be to use
CFLAGS="relevant -I options" LDFLAGS="relevant -L and -l
options" ./configure ...
That way, you can even reorder the libs as necessary, as I found
necessary
e.g. with 1.0.0 to get OpenSSL stuff compiled in (the default configure
script would try to compile stuff with -lcrypto -lssl which fails at least
for static libs, while "-lssl -lcrypto" in LDFLAGS telled configure to do
the right thing).
-----------------------------------------------------------------------------------------
My solution was to get OpenLDAP from blastwave.org
cp -r /opt/csw/include/* /usr/include/
to get /usr/include/ldap.h to hold all the definitions:
LDAP Fix:
./src/modules/rlm_ldap/rlm_ldap.c
unterhalb #define TIMELIMIT 5
/* Changes for OpenLDAP */
#define LDAP_OPT_SUCCESS 0
#define LDAP_OPT_DEBUG_LEVEL 0x5001 /* debug level */
#define LDAP_OPT_NETWORK_TIMEOUT 0x5005 /* socket
level timeout */
#define LDAP_OPT_X_TLS 0x6000
#define LDAP_OPT_X_TLS_CACERTFILE 0x6002
#define LDAP_OPT_X_TLS_CACERTDIR 0x6003
#define LDAP_OPT_X_TLS_CERTFILE 0x6004
#define LDAP_OPT_X_TLS_KEYFILE 0x6005
#define LDAP_OPT_X_TLS_RANDOM_FILE 0x6009
#define LDAP_OPT_X_TLS_HARD 1
-----------------------------------------------------------------------------------------
... the first mentioned solution is more elegant, I think :-)
Matthias Rumitz
TC Unix / Netzwerke
ADIVA Computertechnologie GmbH
Norsk-Data-Str. 1
D-61352 Bad Homburg v.d.H.
Fon: +49(0) 61 72 / 48 61 - 0
Fax: +49(0) 61 72 / 48 61 - 700
Web: http://www.adiva.de eMail: [EMAIL PROTECTED]
Diese E-Mail Nachricht enthält vertrauliche und/oder rechtlich geschützte
Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich
erhalten haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese Mail.
This e-mail message may contain confidential and/or privileged
information.
If you are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail.
----- Originalnachricht -----
Von: "Mitchell, Michael J" <[EMAIL PROTECTED]>
Datum: Donnerstag, Februar 3, 2005 5:29 am
Betreff: configure for rlm_ldap on Solaris
> Hi List,
>
> I've done some more investigation into why configure doesn't work
> out of
> the box on Solaris for rlm_ldap.
>
> I've found the reason, now I need to find a solution, hopefully with
> someone's help...
>
> By default, Solaris comes with ldap include files in /usr/include.
> However, rlm_ldap doesn't compile with these headers out of the
> box, as
> there are missing defines...
>
> We are using openLDAP, and therefore I have specified
> --with-rlm-ldap-include-dir and --with-rlm-ldap-lib-dir to
> configure to
> point to my openLDAP installation (which is not in /usr/local).
>
> It appears that the rlm_ldap configure script finds the /usr/include
> ldap headers, which are enough to pass the configure compile tests.
> However, what this means is that configure says "I don't need the
> --with-rlm-ldap-include-dir directory", and doesn't add it to the
> CFLAGSin the Makefile.
>
> Since Solaris doesn't have a liblber.so, the configure correctly uses
> the --with-rlm-ldap-lib-dir (as openLDAP does have the liblber.so).
>
> So, my problem now, is that I don't have enough knowledge to
> immediatelysay "here's how to fix configure". Or even if there's
> anything that can
> be done to make the configure script work "out of the box" for
> Solaris.
> Any help to fix this for future releases would be greatly
> appreciated...
>
> Sure, its easy to get around it, but it would be nice (for freeRADIUS)
> if it worked out of the box...
>
> Sorry this was so long winded!
>
> Regards,
> Mike
>
>
>
>
>
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
