From wscript:135 if not (Options.options.without_ad_dc or Options.options.with_system_mitkrb5): conf.DEFINE('AD_DC_BUILD_IS_ENABLED', 1) With +addc and +system-mitkrb5, addc is not effective. Of particular interest to those still hoping for a resolution of #542462. Reproducible: Always Actual Results: Samba4 client and samba3 server built with a system-wide mit-krb5, but no ActiveDirectory Domain Controller functionality. Expected Results: Samba4 AD DC able setup, using system wide mit-krb5.
upstream does not support this configuration. see https://wiki.samba.org/index.php/MIT_Build and others
Created attachment 412480 [details, diff] Updated REQUIRED_USE
Great link, thanks. I had not seen this. There should be a REQUIRED_USE="addc? ( !system-mitkrb5 )" in the ebuild. Or should it be REQUIRED_USE="system-mitkrb5? ( !addc )", I don't know if one is preferable to the other.
*** Bug 561092 has been marked as a duplicate of this bug. ***
commit 2b01fa5a6176cda29103183ccecf3f391c27d291 Author: Lars Wendler <polynomial-c@gentoo.org> Date: Tue Sep 22 08:23:48 2015 net-fs/samba: AD Domain Controller only works with heimdal (bug #560370) Package-Manager: portage-2.2.21 Signed-off-by: Lars Wendler <polynomial-c@gentoo.org> net-fs/samba/samba-4.2.4-r1.ebuild | 2 +- net-fs/samba/samba-4.3.0.ebuild | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)