diff options
| author | Rahul Butani <rrbutani@users.noreply.github.com> | 2023-01-15 13:01:22 -0800 |
|---|---|---|
| committer | Rahul Butani <rrbutani@users.noreply.github.com> | 2023-01-27 13:29:23 -0800 |
| commit | 3436075b2a7466a36dbc5687bbb98c6ab748308d (patch) | |
| tree | 6284420d3b399975829605586ca23feb6f48770b /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | 5e5ed7d8161e465fd086a74029e86c53b262a9d1 (diff) | |
llvmPackages_15.llvm: specify some deps explicitly to fix cross-compilation
The two scenarios described within where splicing doesn't handle
selecting the right package for us are observable in the following
(nix repl session):
```
> np = import <nixpkgs> { system = "x86_64-linux"; crossSystem = { config = "aarch64-linux"; }; }
> np.__splicedPackages.hello ? __spliced
true
> np.__splicedPackages.python3Packages.psutil ? __spliced
true
> np.__splicedPackages.python3.pkgs.psutil ? __spliced
false
> (np.__splicedPackages.python3.withPackages (ps: with ps; [psutil])) ? __spliced
false
```
See: #211340
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions
