Justin Erenkrantz wrote:
> This line:
> LIBS="-l${ldaplib} ${extralib} $LIBS"
> would be replaced with:
> APR_ADDTO(LIBS, "-l${ldaplib} ${extralib}")
> m4 escaping rules may want it to be (I forget):
> APR_ADDTO(LIBS, [-l\${ldaplib} \${extralib}])
>
> AC_CHECK_LIB stays the same. This just prevents multiple instances of
> the same library from being inserted into the LIBS string (which is a
> real annoyance).
Ok, makes sense.
The trouble is that the APR_ADDTO macro is not avaiulable to APR-util.
Should it be? Should I just copy the macro out of APR and into APR-util?
> On Solaris, -R specifies "add this directory to the run-time linker
> search path." GNU ld has -rpath. This obviates the need for
> LD_LIBRARY_PATH and other hacks. Wherever you do -L, you should add -R
> (only if you are on Solaris). I'd also do -rpath on Linux, but that's
> me.
>
> APR_ADDTO(LDFLAGS, "-L/path/to/lib")
> if on Solaris, you also want to do: APR_ADDTO(LDFLAGS, "-R/path/to/lib")
> if on Linux, you also want to do: APR_ADDTO(LDFLAGS, "-Wl,-rpath
> /path/to/lib")
Would I specifically have to test for Solaris and then add the -R flag,
or can I get autoconf to do this for me?
> In my experience, LDAP code should be fairly fast. It really doesn't
> even depend on your LDAP server. I run OpenLDAP on a SparcStation 10 -
> that's not much fun (40MHz CPUs), but the lookups and queries are
> really quick. On current hardware, this is really a non-issue.
The code is there, and mature and stable - I'll try do a test both with
and without the cache code to see what a difference it makes.
Regards,
Graham
--
-----------------------------------------
[EMAIL PROTECTED] "There's a moon
over Bourbon Street
tonight..."
smime.p7s
Description: S/MIME Cryptographic Signature
