Cross-compiling with 4.1 ?
cvubrugier at lacie.com
Mon Sep 2 03:19:13 MDT 2013
Dear Jeremy Allison,
On Thu, 22 Aug 2013 14:41:28 -0700, Jeremy Allison wrote :
> In our haste to remove the autoconf build (for
> which I'm as guilty as anyone else) we may
> have lost something important - that's the
> ability to cross-compile 4.1.0 and above.
> Has anyone done this with master/4.1.0 ?
> Does it work ?
Two months ago, I tried to cross compile samba 4.0.7 and it did not
work. I looked a little bit why Samba 4 did not cross-compile but did
not manage to make it build fully. Here is what I saw:
* some programs are built for the target whereas they are expected to
be built for the host. This is the case for some heimdal binaries.
* in buildtools/wafadmin/Tools/python.py, I think that the
PYTHONXCPREFIX variable should be used if the user defines it. This
is necessary in order to build python packages for the target.
There are probably other errors occuring when cross-compiling Samba 4.
The errors I mention are just the first that I encountered.
> I know there are several
> OEMs who absolutely depend on this to
> create working file server builds.
My employer (LaCie) is such an OEM. We are sticking with Samba 3.6
because of the cross-compilation issues of Samba 4.0.
I am a bit busy at the moment, but I will try to cross-compile the
latest version of Samba, look more deeply at the errors and come up with
patches. I think the first step is to open a bug report.
LaCie will welcome you at IBC Amsterdam (13-17 Sept) on booth 7.G17 (Hall7). Come and visit us.
More information about the samba-technical