-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Zellij relies on bootstrap-tools which makes cross-compiling a challenge #216
Comments
(I think something as simple as whatever depends on bash can cause this) |
Something I don't understand -- this cross-compiled to aarch64 just fine. So, there's something I don't understand. |
I tried to fix the dependencies a bit, they were still in some wrong spots from technical debt over the years.
The flake here prefers using mold as a linker on linux systems, maybe that has some impact? I added some very basic overlays, but they are not yet ready for cross compilation. |
I pushed exposing legacyPackages to a different branch for testing purposes. Do you mind checking this attribute?
It seems that Flake ref:
Attribute:
|
I haven't been able to check this yet, but I can say that while bee0cae builds for me, tip of |
Thank you for that information! |
I re-updated, and then re-downgraded due to hitting the same error:
To remove any ambiguity, I'm building my aarch64 system, updating all inputs, building again (fails), downgrading only |
Regarding the debug-PR, pkgsCross test:
this was executed (eval'd+built) on the |
Thank you for keeping on testing my changes! Do you mind checking the current: #222 please again? It should be able to be run with:
|
Hmm, I'm going to give it a shot, but I guess I'm still hoping for something like Helix, where I just include For me, this "just works", either native or cross-compiling. This invocation makes it seem like I'll be writing conditionals into my config for "if cross compiling...". Which isn't unprecedented, but seems less ideal. |
Sorry that I'm just getting back to this. I kind of forgot that I pinnned I'm currently still having issues with cross-eval, native-compilation. That is, I've let
So, something during eval is incorrectly relying on the evaluation host instead of the stdenv target platform. For now I'm probably just going to have the aarch64 machines default to using |
Thank you for the answer. I have updated main in hopes to improve cross compilation support again. Do you mind to check that? I am not 100% sure it will work in every context, since I am using an overlay to get the correct toolchain. |
I set my zellij config back to use the flake package for any combo of host/build platform, and re-added it to my last remaining
|
Thank you for checking again! |
I was thinking over this last night, I don't really see how this can work using the package directly, given how cross-compiling works by configuring However, I hit a different issue when using this as an overlay:
So it's acting like it doesn't have access to the rust-overlay you're using inside the flake. |
Hi,
I consider
zellij
a very core tool and have it as part of my very core profile that gets deployed to all of my NixOS machines, including those that I cross-compile for.I was able to get Helix and Bottom (btm) to cross-compile (which I consider in the same class of nice, new, Rust tools), but Zellij fails.
However, zellij breaks it:
Just throwing this out for initial consideration. For all I know a native dep of Zellij is bringing this in, but I'm not sure, I know in other places folks have managed to side-step requirements for bootstrap-tools for this cross-compile scenarion.
I don't think it matters, but I'm trying to cross compile from x86_64-linux buildPlatform for a riscv64-linux hostPlatform.
NOTE: I haven't tried zellij from nixpkgs yet...
The text was updated successfully, but these errors were encountered: