heimdal headers ordering (gssapi/gssapi.h, crypto-headers.h)

Michael Tokarev mjt at tls.msk.ru
Mon Mar 28 07:49:12 UTC 2022

28.03.2022 10:21, Michael Tokarev via samba-technical wrote:
> 28.03.2022 10:14, Michael Tokarev via samba-technical wrote:
> ...
>> We should list heimdal_build/include *before* heimdal/include in
>> all cases. Yet the order is random, non-deterministic:
> The include path is stored in a hash-like structure with
> randomness in waf, right?

And it pretty much seems to be the case. The build success
or failure depends on the source path.

In debian the automated build procedure by default
unpacks the source in a random directory like

It always builds fine in
/build/samba-HZ1vA1/samba-4.16.0+dfsg/ and it always fails in
/build/samba-HZ1vA0/samba-4.16.0+dfsg/ (note the 1 vs 0 at the
end of the second path component).

Who-heee!.. It is fun to hit bugs as hilarious as this one ;)

Now, please someone who have knowlege of python and waf,
please take a look at this.  Everything's under the fingers

> It is not a set, it is an ordered list...

It should not be a set/hash which depends on the pathname :)



More information about the samba-technical mailing list