[Pkg-samba-maint] Bug#1030593: tdb FTCBFS: performs run checks

[Michael Tokarev]

Hello Helmut!

Why did you include the sysname change? — this one:

+--- tdb-1.4.8.orig/buildtools/wafsamba/samba_conftests.py
++++ tdb-1.4.8/buildtools/wafsamba/samba_conftests.py
+@@ -440,7 +440,7 @@
+ def CHECK_UNAME(conf):
+     '''setup SYSTEM_UNAME_* defines'''
+     ret = True
+-    for v in "sysname machine release version".split():
++    for v in "sysname".split():
+         if not conf.CHECK_CODE('''
+                                int printf(const char *format, ...);
+                                struct utsname n;


For tdb, there's one more change needed. Its test target
requires host python for python tests.  This is unfortunate,
the build procedure itself uses python (which best to be the
native python), and determines python characteristics from
there instead of from host python, this is where that
_PYTHON_SYSCONFIGDATA_NAME hack is handy; but it doesn't
help with the tests.

Besides, the same set of changes is needed for other samba-related
packages, namely tevent and talloc, and for samba itself.
In tevent we already have cross.patch from you (I fixed that one
a week or so ago) which should be applied to tdb as well, I guess.

It would be great to push the changes upstream. But since cross-
compilation is not a very hot topic upstream, I guess debian can
be sort of a playground for that, to test things before submitting.

Overall, the samba build system is in a quite bad state, from my
PoV anyway, - it is based on many hacks (like including files
from "random" dirs, see for example "helper" attributes in librpc/
idl/*.idl files and try to guess how this "include" supposed to
work; the PYTHONHASHSEED fiasco on sparc64 and shipping multiple
include files of the same name in same-named dirs, - which is still
unfixed upstream with random -I order, so it's impossible to guess
which one will be included, and so on.) So maybe cross-compile
changes aren't of the first priority here.

/mjt