377924dd7b
Fix instances of tool dependencies coming from `self` or `pkgs` instead of `self.buildHaskellPackages` or `pkgs.buildPackages` respectively. This makes sure cross-evaluation and -compilation will work although their may still be more kinks to work out (or cases I missed). This change was mostly created by searching for `[tTool]` and `\${` in the respective files. Note that this has intentionally not been for test tool dependencies: Like in `stdenv.mkDerivation` we need to view tests as being executed on the *host platform* which is why we can't run tests while cross compiling anyways. In practice this is not an important distinction, though: `pkgs.buildPackages` and `pkgs` are almost identical in the native case. Resolves #127232. |
||
---|---|---|
.. | ||
androidndk-pkgs | ||
arduino | ||
beam-modules | ||
bower-modules/generic | ||
chez-modules | ||
compilers | ||
coq-modules | ||
dhall-modules | ||
dotnet-modules | ||
em-modules/generic | ||
gnuradio-modules | ||
go-modules | ||
go-packages | ||
guile-modules | ||
haskell-modules | ||
idris-modules | ||
interpreters | ||
java-modules | ||
libraries | ||
lisp-modules | ||
lua-modules | ||
misc | ||
mobile | ||
node-packages | ||
ocaml-modules | ||
octave-modules | ||
perl-modules | ||
pharo | ||
php-packages | ||
pure-modules | ||
python-modules | ||
r-modules | ||
ruby-modules | ||
scheme-modules/scheme-bytestructures | ||
tools | ||
web |