> Probably you're seeing an argon2 left over from some other build. When you
just use "--enable-remoteauth" it defaults to a static build, not a dynamic
module. So there is > no remoteauth.la to install, the code is just part of
the slapd binary.

So, if I'm understanding you correctly, using --enable-remoteauth is doing a
static build not a dynamic. How would I go about doing a dynamic build then?

> It's not really loading remoteauth. The moduleload command knows if a
module was built statically and just silently succeeds for those. It works
that way to allow easy
> migration between builds with static vs dynamic modules.

So, what parameters should I use to build dynamically?

Thanks

Reply via email to