766f5ffb76
llvmPackages_*.clang should check the default compiler for the package set it is targeting (targetPackages.stdenv.cc) instead of the compiler that has been used to build it (stdenv.cc) in order to get some sense of whether to use libc++ or libstdc++. Since we are now inspecting targetPackages in the llvmPackages.clang attribute, we need to avoid using it in the cross stdenv — which just forces us to explicitly request libcxxClang for darwin instead of relying on the clang attribute to pick it for us. We also need to do something similar for targetPackages.stdenv.cc: Here the llvmPackages.clang logic would work as we want (inspect targetPackages.stdenv.cc and if it doesn't exist, make the choice based on stdenv.cc), but it gets locked in a cycle with the previous package. We can easily break this, however: We know that the previous set had clang and the next one doesn't exist, so we'd choose libcxxClang any day of the week. |
||
|---|---|---|
| .. | ||
| androidndk-pkgs | ||
| beam-modules | ||
| bower-modules/generic | ||
| chez-modules | ||
| compilers | ||
| coq-modules | ||
| dhall-modules | ||
| dotnet-modules | ||
| em-modules/generic | ||
| embedded | ||
| gnuradio-modules | ||
| go-modules | ||
| go-packages | ||
| guile-modules | ||
| haskell-modules | ||
| idris-modules | ||
| interpreters | ||
| java-modules | ||
| libraries | ||
| lisp-modules | ||
| lua-modules | ||
| misc | ||
| mobile | ||
| nim-packages | ||
| node-packages | ||
| ocaml-modules | ||
| octave-modules | ||
| perl-modules | ||
| pharo | ||
| php-packages | ||
| pure-modules | ||
| python-modules | ||
| quickemu | ||
| r-modules | ||
| ruby-modules | ||
| scheme-modules/scheme-bytestructures | ||
| tools | ||
| web | ||