[Pkg-samba-maint] samba-4.16 progress so far

[Andrew Bartlett]

On Wed, 2022-03-30 at 20:19 +0300, Michael Tokarev wrote:
> Okay. Since we have more-or-less usable python on unstable again,
> the salsa ci pipelines started working again, and this immediately
> triggered a problem which I already mentioned before, but I didn't
> think it is a real problem.
> 
> The problem is that `waf install' still compiles some files which
> `waf build' didn't build, even after the PYTHONHASHSEED  is set.
> 
> Namely, for some reason, it rebuilds:
> 
>   Linking bin/default/third_party/heimdal_build/compile_et.inst
>   Linking bin/default/third_party/heimdal_build/asn1_compile.inst
>   Linking bin/default/lib/replace/libreplace-samba4.inst.so
> 
> This fails at the install stage in salsa ci, since the install
> is run as root, the link is done using ccache not gcc, and ccache
> tries to create some cache files even when called for link,
> not for compile.
> 
> This is a new question for the build procedure, which I'm *still*
> not familiar with. Now from a different angle.. :)

This is by design in Samba, so you may need to adjust the tooling
around Samba.

Samba is designed to be able to run from the build tree for development
etc, or to run asn1_compile (these should not be installed, nor be
prepared to be installed that is a distinct bug) using -rpath pointing
into the build tree and with other things set for in-tree use.

The system install then changes some of these variables and paths and
so some things need to be rebuilt and re-linked.  It shouldn't be the
whole tree, but is non-zero.

Andrew Bartlett

-- 
Andrew Bartlett (he/him)       https://samba.org/~abartlet/
Samba Team Member (since 2001) https://samba.org
Samba Team Lead, Catalyst IT   https://catalyst.net.nz/services/samba

Samba Development and Support, Catalyst IT - Expert Open Source
Solutions