Tristan Ross

> Thanks for the pointer! But why would the kernel need patching, if it builds fine with the unwrapped toolchain? It seems like we do something weird in our wrapping...

Also, we shouldn't use the unwrapped toolchain because if something does need it but needs dynamic libraries then that would cause build failures. The safe and proper solution is to...

> > Also, we shouldn't use the unwrapped toolchain because if something does need it but needs dynamic libraries then that would cause build failures. The safe and proper solution...

I think we'll have to override some stuff to produce a build platform stdenv that uses a build platform LLVM linker. It should be doable and shouldn't require changing the...

I was able to cross compile an x86_64-linux kernel on aarch64-linux using LLVM via `{ crossSystem = legacyPackages.aarch64-linux.lib.systems.examples.gnu64 // { useLLVM = true; linker = "lld"; }; }`.

I've made an attempt in #12227, it's a little delayed at closing out but it does seem to improve the problem.

Do you get these log messages when you launch it from the terminal? ``` ** (localsend_app:115217): WARNING **: 23:54:20.320: gtk.dart: failed to call method: No engine to send to **...

Huh, why is systemd saying localsend is starting? Also, could you try using `GTK_DEBUG=interactive`? Find the window object, go into properties, and toggle the visibility. Does that make the window...

Issue seems to be with `dart pub get` being called from a sandbox, `jaspr` should have a switch to be able to disable `dart pub get`.

The CLI completion error doesn't prevent building, I added verbose logging and got a socket error. For whatever reason, jaspr is fetching from `pub.dev` inside a networkless sandbox.