waf install recompiles another 4k files after waf build built its own 4k?

Michael Tokarev mjt at tls.msk.ru
Wed Mar 30 18:22:00 UTC 2022


Here's one more issue with the build process of 4.16.
The context is - I'm packaging 4.16 for Debian.
We fixed the missing PYTHONHASHSEED=1 for waf already,
but it didn't help with the recompilation.

I noticed that `waf install' compiles a whole lot of files
after `waf build' finished already. Most of them are recompiled, -
for example, the dynconfig.c file (it is the first such
file), and many other files from all over the places.
I can't say they _all_ are recompiles or not, maybe some
of them are new.

Some of the linking calls definitely are new, for these 3:

  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

(these are linked at the install time _only_).

Why the build system might decide it needs to recompile right
to everything during the install stage?

The 2 waf invocations (for build & install) are the same.



More information about the samba-technical mailing list