| 3 Apr 2025 |
| @2xsaiko:tchncs.de changed their display name from 2xsaiko to 2xsaiko (moved! @saiko:knifepoint.net). | 12:52:01 |
| 4 Apr 2025 |
emily | https://github.com/nix-darwin/nix-darwin/issues/1418 is this a recent breaking change in the Rust builder interface? | 11:32:39 |
emily | wonder if it's my fault | 11:32:40 |
antifuchs | (It wasn’t, hah) | 14:42:13 |
| 5 Apr 2025 |
| @tinybronca:sibnsk.net left the room. | 15:39:20 |
| Sapphire changed their profile picture. | 20:07:27 |
| staberinde joined the room. | 23:01:47 |
| 9 Apr 2025 |
cleverca22 | having some trouble building a package in rust, it needs both x86-64-linux and wasm32, all of the x86 stuff seems to work with normal buildRustPackage, but then a build.rs file goes and runs cargo with --target=wasm32-unknown-unknown and it fails, how would i get both targets at once? | 01:10:12 |
K900 | Our default compilers should have WASM targets I think? | 04:59:58 |
K900 | At least on unstable | 05:00:01 |
K900 | Not sure about 24.11 | 05:00:03 |
cleverca22 | In reply to @k900:0upti.me At least on unstable and i'm on master, so it should work... | 11:55:34 |
K900 | How does it fail? | 11:55:49 |
cleverca22 | In reply to @k900:0upti.me How does it fail? https://github.com/paritytech/polkadot-sdk/blob/master/substrate/utils/wasm-builder/src/prerequisites.rs#L228-L250 | 11:56:43 |
cleverca22 | this error is getting triggered via build.rs | 11:56:49 |
cleverca22 | Rust WASM target for toolchain 0rn3apgrjdqrq6zpqsrh5b8dmlxbci42-rustc-1.85.0 is not properly installed; please install it! | 11:56:58 |
Alyssa Ross | Maybe the check is wrong? | 12:37:34 |