Winbindd not running on Android
Andrew Bartlett
abartlet at samba.org
Tue Sep 15 10:35:38 UTC 2015
On Tue, 2015-09-15 at 06:30 +0000, Anoop Singh wrote:
> Hi Andrew,
>
> Thanks a lot for the help and guidance.
> Do you mean this issue is fixed probably in release 4.3, the newest
> one?
Only if the issue is a simple conflict with libidmap,so from NFSv4
(typically found on solaris), then 4.2 and above should fix it.
> Actually I am using older version of samba 4.1.14.
> So if I want to fix this issue in 4.1.14, as per your mail I need to
> remove all the instances of "allow_undefined_symbols=True" or does it
> mean to replace with "allow_undefined_symbols=False" in these files:
>
> 1. source3/wscript_build
> 2. source3/winbindd/wscript_build
> 3. source3/modules/wscript_build
>
> I also see the instance used in these files also
> 1. buildtools/wafsamba/wafsamba.py : in this file at line no 133 and
> 417, allow_undefined_symbols=False
> 2. buildtools/wafsamba/samba_python.py: in this file at line no 65,
> allow_undefined_symbols=True
>
> What should I do with these instances. Looks like I don't need to
> change anything in these two places. Please confirm.
You need to fix up source3/winbindd/wscript_build to remove the
'allow_undefined_symbols=True' statements, and then re-work the code
and dependencies until it works. I don't suggest you try with 4.1,
best to do it in master and then backport to 4.3.
This isn't trivial, but should be practical. It may also be enough to
simply disable all the idmap modules as a proof of concept.
Andrew Bartlett
--
Andrew Bartlett http://samba.org/~abartlet/
Authentication Developer, Samba Team http://samba.org
Samba Developer, Catalyst IT http://catalyst.net.nz/services/samba
More information about the samba-technical
mailing list