resolve naming conflicts when compiling rwm overlay as static (will disappear as soon as rwm stuff is removed from back-ldap/back-meta)

Works on BSD as well (equiv. to -DFD_SETSIZE=N).

Need to remove use of deprecated functions.

a mechanism is specified.  (Few mechanisms (DIGEST-MD5 only) support
separate realms.)

when comparing IDs to saslAuthzTo/From values, the saslAuthzTo
saslAuthzFrom values can take different forms:

dn[.<style>]:<pattern>

<style> ::= 	exact		; exact match
		children	; children of <pattern> match
		subtree		; <pattern> or children of <pattern> match
		regex		; <pattern> is regcomp() & regexec()
if no <style>, then exact is assumed

u[.<mech>][/<realm>]:<user>

when parsing a proxyAuthz value, only exact DN is allowed,
and no <mech> can be specified.  <user> cannot contain ':'
and <mech> cannot contain '/'.

in userid of a@b and realm of c.

with newly assigned protocol result codes.

Don't crash in slapcat when NULL entry is returned.