Nix Rust | 687 Members | |
| Rust | 156 Servers |
| Sender | Message | Time |
|---|---|---|
| 1 Apr 2025 | ||
| That sounds very hard to implement correctly for a separate sandbox. | 11:09:57 | |
| well, the point behind restrictions is to let you make a ring and then hand it off to someone less privileged than you (since it's just a fd, sending fds is easy) for that use case, making it per-ring is correct but for the seccomp use case of "protecting you from yourself", yeah, it has to be global | 11:26:04 | |
| 23:15:46 | ||
| 3 Apr 2025 | ||
| After I do some basic testing on darwin I think https://github.com/NixOS/nixpkgs/pull/390171 is good to go | 08:26:19 | |
| 12:52:01 | ||
| 4 Apr 2025 | ||
| https://github.com/nix-darwin/nix-darwin/issues/1418 is this a recent breaking change in the Rust builder interface? | 11:32:39 | |
| wonder if it's my fault | 11:32:40 | |
| (It wasn’t, hah) | 14:42:13 | |
| 5 Apr 2025 | ||
| 15:39:20 | ||
| 20:07:27 | ||
| 23:01:47 | ||
| 9 Apr 2025 | ||
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 | |
| Our default compilers should have WASM targets I think? | 04:59:58 | |
| At least on unstable | 05:00:01 | |
| Not sure about 24.11 | 05:00:03 | |
In reply to @k900:0upti.meand i'm on master, so it should work... | 11:55:34 | |
| How does it fail? | 11:55:49 | |
In reply to @k900:0upti.mehttps://github.com/paritytech/polkadot-sdk/blob/master/substrate/utils/wasm-builder/src/prerequisites.rs#L228-L250 | 11:56:43 | |
this error is getting triggered via build.rs | 11:56:49 | |
Rust WASM target for toolchain 0rn3apgrjdqrq6zpqsrh5b8dmlxbci42-rustc-1.85.0 is not properly installed; please install it! | 11:56:58 | |
| Maybe the check is wrong? | 12:37:34 | |
| 12:48:36 | |
| it looks like its trying to run the llvm linker for some reason?? | 12:48:47 | |
| I wouldn't call it "check". From linked code it seemingly tries to build their "dummy crate" inside and fails to output anything as a result around here (which I assume may not be expected to work properly inside buildRustPackage):https://github.com/paritytech/polkadot-sdk/blob/65441c8199ba8c9c1fe75ba4d432352109e87d43/substrate/utils/wasm-builder/src/prerequisites.rs#L211 https://github.com/paritytech/polkadot-sdk/blob/65441c8199ba8c9c1fe75ba4d432352109e87d43/substrate/utils/wasm-builder/src/prerequisites.rs#L150-L177 | 12:49:51 | |
| I wouldn't call it "check". From linked code it seemingly tries to build their "dummy crate" inside and fails to output anything as a result around here (which I assume may not be expected to work properly inside buildRustPackage, because it does cargo build with its' own things):https://github.com/paritytech/polkadot-sdk/blob/65441c8199ba8c9c1fe75ba4d432352109e87d43/substrate/utils/wasm-builder/src/prerequisites.rs#L211 https://github.com/paritytech/polkadot-sdk/blob/65441c8199ba8c9c1fe75ba4d432352109e87d43/substrate/utils/wasm-builder/src/prerequisites.rs#L150-L177 | 12:50:36 | |
the other issue that makes things slower, is the inability of buildRustPackage to cache the deps | 12:52:40 | |
| so it takes 20 minutes to reproduce the failure, after every change | 12:52:49 | |
| Honestly I would just try to patch it out to be "noop" (always assume toolchain it tries to check is fine) and see if it is builds. | 12:55:59 | |
| * Honestly I would just try to patch it out to be "noop" (always assume toolchain it tries to "check" is fine) and see if it is builds. | 12:56:22 | |
| * Honestly I would just try to patch it out to be "noop" (always assume toolchain it tries to "check" is fine) and see if it builds. | 12:56:28 | |