wongsyrone
commented
8 years ago https://bugzilla.samba.org/show_bug.cgi?id=10128
I built samba 4.2.0 on a custom embedded system now, and the major hurdles to overcome were as follows: libldap.so depends on other shared libraries (openssl). With a native linker, the linker would typically find those, but with a cross linker, the -L parameter is not enough (it is being used for finding -l
but not for dependencies of those libs). On samba3 there was the LDAP_LIBS configuration variable to handle this. Here came -rpath-link switch to the rescue - for each -L switch in LDFLAGS I also added a corresponding -rpath-link switch, telling the linker where to look for those dependent libs (e.g. if LDFLAGS was "-L /foo" now it's "-L /foo -Xlinker -rpath-link=/foo) Python (sigh). You really need a functioning python-config for the target, that can run on the host. So that when you run "python-config --includes" it will print out the include directories for the target's python, on the build machine. Python 2.7 doesn't have that out-of-the box. You can backport the fix from Python 3, as buildroot are doing, but I had to tweak that too. Bottom line is that python-config --includes must be correct. Then you put it in configure's environment (PYTHON_CONFIG=/path/to/target/python-config ./configure)
Strangely, for Python libraries and link flags, python-config is not consulted. I wish it were because if you get it right, that solves everything. There's a partial solution in the form of python_LIBDIR (which allows you ONLY to add to linker search path) and python_LDFLAGS (which allows you ONLY to set more link flags). Best thing is to set them to empty string, relying on existing LDFLAGS that already points to python libs. However, the additional libraries to link against (additional -l flags) are taken from the build machine python (distutils) and that's a bug. Luckily for me they were the same, but even if my target python was statically-linked, I would run into a problem b/c the order of libraries included is dependencies first, python second.
Another issue I encountered was that my embedded kernel didn't support IPv6 and I couldn't find a way in the build system to disable IPv6 - IPv6 was enabled based on it being supported by libc. That means smbd cannot listen to connections. My fix for that was simply to add IPv6 support.
So to summarize: PYTHON_CONFIG=/path/to/my/target python-config \ python_LDFLAGS="" \ python_LIBDIR="" \ LDFLAGS="${LDFLAGS} -Xlinker -rpath-link=/path/to/openssl/libs \ ./configure --cross-compile --cross-answeres=/my/answers/file ....
boypt
mormts
hbl0307106015
waf needs python2 to work. package python should be tweaked to fit need of samba 4.1 or higher
Build Requires: https://github.com/wongsyrone/packages-1/commit/4f3a6ecca7d6d076c0b0ce17bdad2b5dd13450b1 https://github.com/wongsyrone/packages-1/commit/60ca6f0f2b6712e023bc4af38f15a10d1aa78154
Notice: I simply removed two functions in source4/torture/local/nss_tests.c to pass linking stage since nobody will run
smbtortureon embedded system, hardware is expensive. :)