diff options
| author | Adam Joseph <adam@westernsemico.com> | 2022-08-22 02:05:50 -0700 |
|---|---|---|
| committer | Adam Joseph <adam@westernsemico.com> | 2022-08-22 02:27:06 -0700 |
| commit | 8682bd0a81797f64a825c8941272df2a6342bb5c (patch) | |
| tree | a41ada13d3aeb0ac64ab5838ea7e995004120639 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | eaf476b6080e0a7d60582cece4d6e4f6463b0814 (diff) | |
build-support/rust: toTargetArch: strip off endianness
`toTargetArch` in `pkgs/build-support/rust/lib/default.nix` is used to
set `CARGO_CFG_TARGET_ARCH`. This environment variable is supposed to
be the `<arch>` portion of an LLVM-style platform name:
```
<arch><sub>-<kernel>-<libc><abi>
```
Note that the pointer-width (the "64" in "x86_64" and "mips64") is
part of `<arch>`, but the endianness (the `_be` in `aarch64_be`) is
*not*.
Unfortunately at the moment nixpkgs' parsed `cpuType` has no way to
query for the three subparts (name, pointer-width, and
subarch/endianness), nor any way to ask for just the first two parts.
For now, this commit simply fixes the problem in the two cases that
matter: `mips64el` and `powerpc64le`, which I believe are the only two
platforms supported by both rust and nixpkgs which have a
"subarchitecture".
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions