Alyssa Ross 67641d0589 wafHook: don't add cross compilation flags ... These flags are not part of waf, they're custom flags that are not widely implemented. More packages are broken because of these flags being added than actually recognise them. Of the packages in Nixpkgs that directly depend on wafHook that we can attempt to cross compile (i.e. all their dependencies cross compile), 5 already successfully cross compile and recognise these flags, 2 already successfully cross compile because they have been opted out of these flags, 3 don't cross compile successfully for reasons unrelated to these flags, and for the remaining 7, the only thing stopping them cross compiling successfully is that they are being passed these flags that they don't recognise. All of the five successfully cross-compiling packages that do recognise these flags are samba projects: ldb, talloc, tdb, tevent, and samba4. So this isn't a general waf convention, just a samba one. It therefore doesn't make sense to set these flags by default. They should just be included in the expressions for each samba project, like all the other quirks common to samba build systems. This change fixes cross compilation of the following packages: blockhash ganv ndn-cxx mda_lv2 pflask raul saldl		2024-05-15 16:47:16 +02:00
..
4.x-fix-makeflags-parsing.patch
4.x-no-persistent-install-dynconfig.patch
4.x-no-persistent-install.patch
4.x.nix	wafHook: don't add cross compilation flags	2024-05-15 16:47:16 +02:00
build-find-pre-built-heimdal-build-tools-in-case-of-.patch
patch-source3__libads__kerberos_keytab.c.patch