Sender | Message | Time |
---|---|---|
20 Aug 2024 | ||
blitz | 15:13:52 | |
blitz | * | 15:13:59 |
blitz | *
| 15:14:22 |
blitz | this works | 15:14:28 |
emily | you can probably just use patchFlags also | 15:15:14 |
emily | but yeah, sure :) | 15:15:22 |
emily | (why do you need to do this anyway?) | 15:15:27 |
blitz | https://github.com/cloud-hypervisor/cloud-hypervisor/issues/6673 | 15:16:14 |
blitz | before the fix is merged, it's easier to just patch the couple of lines that cause the issue in the dependent crate rather than the crate updates | 15:16:52 |
emily | ah | 15:19:03 |
21 Aug 2024 | ||
Fraol Lemecha set a profile picture. | 20:24:14 | |
22 Aug 2024 | ||
Jared Baur set a profile picture. | 02:07:14 | |
Jack Leightcap joined the room. | 02:52:22 | |
Jack Leightcap | hey all -- i'm packaging a rust project, and noticed that nixpkgs doesn't include oxalica/rust-overlay: i'm curious then if there's a way to add targets to rustc inside nixpkgs, something like in a rust-toolchain.toml targets = [ "thumbv7em-none-eabihf" ] | 03:01:12 |
Jack Leightcap | the context is an embedded firmware, so the target platform is fixed to arm-embedded. would pkgsCross.arm-embedded accomplish this? | 03:05:10 |
ghpzin | Pretty sure this exact target is covered by something related to cross in rust section in nixpkgs. | 04:26:18 |
ghpzin | * Jack Leightcap: Pretty sure this exact target is covered by something related to cross in rust section in nixpkgs. https://github.com/NixOS/nixpkgs/blob/c79da508a6bea132f3a0debcec870063f99078f1/doc/languages-frameworks/rust.section.md#cross-compilation-cross-compilation | 04:27:01 |
Jack Leightcap | thanks, RTFM needed and useful here | 04:38:57 |
ghpzin | Does anybody know if there are workarounds for Cargo.lock having dependencies with same name, but different urls ?https://github.com/NixOS/nixpkgs/issues/183344 | 06:21:05 |
ghpzin | * Does anybody know if there are workarounds for Cargo.lock having dependencies with same name, but different urls ?https://github.com/NixOS/nixpkgs/issues/183344 (other than editing Cargo.lock to use same one and hoping for the best) | 06:24:01 |
ghpzin | * Does anybody know if there are workarounds for Cargo.lock having dependencies with same name, but different urls ?https://github.com/NixOS/nixpkgs/issues/30742 (other than editing Cargo.lock to use same one and hoping for the best) | 06:33:14 |
Artur Manuel joined the room. | 12:57:53 | |
Artur Manuel changed their profile picture. | 14:53:09 | |
nyanbinary 🏳️⚧️ left the room. | 17:19:45 | |
Theo Paris | In reply to @9hp71n:matrix.orgIs there a way to compile the rust std as a derivation in that case? It says the std isn't compiled when using the cross target... | 21:23:17 |
Theo Paris | * Is there a way to compile the rust std as a derivation in that case? It says the std isn't compiled when using the cross target... Not sure whether or not the core/alloc crate applies here | 21:23:46 |
23 Aug 2024 | ||
Theo Paris | So building a rust crate for mingw with llvm ends up trying to cross compile rustc and cargo for mingw instead of just the rust crate... What would be the correct fix for this? Additionally, building x86_64-w64-mingw32-rustc fails due to dlltool | 04:09:22 |
Theo Paris | * So building a rust crate for mingw with llvm ends up trying to cross compile rustc and cargo for mingw instead of just the rust crate... What would be the correct fix for this? Additionally, building x86_64-w64-mingw32-rustc fails due to dlltool with pkgsLLVM | 04:09:28 |
K900 | How are you doing that? Also, why LLVM? | 04:10:19 |
Theo Paris |
| 04:10:58 |