| 31 Oct 2021 |
 trofi | Congruts! \o/ | 15:42:46 |
 @AleXoundOS:matrix.org | Then I've hit a bunch of building problems for gstreamer dependencies and already solved one (boost). Currently, I've stumbled across building harfbuzz:
src/meson.build:631:4: ERROR: Pkg-config binary for machine MachineChoice.BUILD not found. Giving up.
meson guys answer quickly but I didn't understand fully how to use their tips: https://github.com/mesonbuild/meson/issues/1849#issuecomment-955721932. | 15:45:19 |
| @AleXoundOS:matrix.org | I suppose cross-compilation with meson is solved in nixpkgs. Isn't it solved for aarch64? | 15:47:26 |
| @AleXoundOS:matrix.org | * Then I've hit a bunch of building problems for gstreamer dependencies and already solved one (boost). Currently, I've stumbled upon building harfbuzz:
src/meson.build:631:4: ERROR: Pkg-config binary for machine MachineChoice.BUILD not found. Giving up.
meson guys answer quickly but I didn't understand fully how to use their tips: https://github.com/mesonbuild/meson/issues/1849#issuecomment-955721932. | 15:52:59 |
| @AleXoundOS:matrix.org | Redacted or Malformed Event | 16:02:56 |
| @AleXoundOS:matrix.org | harfbuzz cross-compilation issue is fixed in master nixpkgs. Though, it seems that harfbuzz upgrade (2.8.0 -> 2.8.2) also makes sense. | 16:12:39 |
| @AleXoundOS:matrix.org | * harfbuzz cross-compilation issue is fixed in nixpkgs master. Though, it seems that harfbuzz upgrade (2.8.0 -> 2.8.2) also makes sense. | 16:12:49 |
| @AleXoundOS:matrix.org | * Then I've hit a bunch of building problems for gstreamer dependencies and already solved one (boost). Currently, I've stumbled upon building harfbuzz:
src/meson.build:631:4: ERROR: Pkg-config binary for machine MachineChoice.BUILD not found. Giving up.
meson guys respond quickly but I didn't understand fully how to use their tips: https://github.com/mesonbuild/meson/issues/1849#issuecomment-955721932. | 16:16:07 |
 Rick (Mindavi) | I expect nixpkgs to be less broken in general on master vs 21.05 for cross compilation | 16:20:08 |
| 1 Nov 2021 |
 Sandro | For the best cross compilation experience please use unstable or master. We don't Backport cross fixes usually. | 00:20:18 |
| trofi | TIL llvmPackages points to llvm-7 on linux. | 08:46:54 |
 Alyssa Ross | and macOS | 09:19:10 |
| Alyssa Ross | We've been stuck for years because we've been stuck on it on Darwin, and everything uses LLVM on Darwin. | 09:19:43 |
| trofi | Oh, that makes sense.. I was very confused to see that mesa uses llvmPackages_latest (from llvm-12) and libclc (from llvm-11, hardcodes source version in .nix file). And libclc is built against llvmPackages libraries (llvm-7). | 09:33:20 |
| trofi | * Oh, that makes sense. I was very confused to see that mesa uses llvmPackages_latest (from llvm-12) and libclc (from llvm-11, hardcodes source version in .nix file). And libclc is built against llvmPackages libraries (llvm-7). | 09:33:39 |
| Alyssa Ross | the place to watch is https://github.com/NixOS/nixpkgs/pull/126411 | 09:36:23 |
 Domen Kožar | it's basically ready it's waiting on the next NixOS cycle (ironically, darwin is stuck due to linux, which is stuck due to darwin) | 18:27:11 |
| trofi | Sorry, I don't know how nixpkgs manages toolchain lifecycle :) Does cycle here mean NixOS release? Or just a staging->master merge? | 19:33:32 |
 sterni | nixos release | 19:33:48 |
| sterni | specifically upgrading LLVM from 7 to 11 is not possible anymore due to the feature freeze disallowing breaking changes on staging-next | 19:34:16 |
| sterni | it would have been fine if the PR would have been ready earlier | 19:34:29 |
| trofi | Ah, it's a matter of pre-release freeze. Otherwise, would it be fine to change major compiler version say, every 2 months in staging? (Not that they release that frequently). | 19:37:47 |
| Alyssa Ross | yes | 19:38:21 |
| Alyssa Ross | Redacted or Malformed Event | 19:38:31 |
| Alyssa Ross | as long as packages keep building | 19:38:56 |
| trofi | nod. Thank you! | 19:39:09 |
| sterni | shouldn't libexec be installed to $out/$bin? | 19:45:33 |
| trofi | probably rather $out/$lib. otherwise installing such a package would get internal tools (or their dir) into PATH. postfix or git should be good examples. | 19:51:04 |
| sterni | libexec is never in PATH? | 19:51:29 |
| trofi | I think it's never in PATH. https://www.gnu.org/prep/standards/html_node/Directory-Variables.html also says it's not for users. | 19:53:23 |
