Nix Rust | 691 Members | |
| Rust | 156 Servers |
| Sender | Message | Time |
|---|---|---|
| 9 Feb 2025 | ||
| oh! then it might be even more broken than just the docs problem | 09:34:50 | |
| brb checking at which stage it failed | 09:53:46 | |
| So
will not just work? | 16:59:25 | |
so it's the docs after all | 09:54:33 | |
| yep, the build just failed with those 😕 | 17:05:55 | |
| https://github.com/rust-lang/rust/pull/135107#discussion_r1948052377 | 10:05:24 | |
| Someone wrote earlier that we could compile the mitmproxy-linux-ebpf crate separately. I could do that probably by copying things from rust-hypervisor-firmware but I am a bit lost how to integrate that back into mitmproxy-linux | 17:08:06 | |
yup tried with --disable-docs and that builds fine... | 10:25:18 | |
| probably we would need to hock into https://github.com/mitmproxy/mitmproxy_rs/blob/79dbbf7e080574b7bb8b92766232f7e1b6e1d0a3/mitmproxy-linux/build.rs#L141 ? | 17:09:36 | |
| so good news, unlike a few years ago it appears the set of crates to generate docs for is not hardcoded anymore | 10:36:49 | |
| now to find out how to configure this per target, and if that's not possible, how to patch it not to produce std docs for no_std targets | 10:37:10 | |
| the source of the crate set appears to be in https://github.com/rust-lang/rust/blob/43ca9d18e333797f0aa3b525501a7cec8d61a96b/src/bootstrap/src/core/build_steps/compile.rs#L399-L418 | 10:38:28 | |
| which appears to have no_std handling already, odd | 10:39:00 | |
| added in https://github.com/rust-lang/rust/pull/128182 which was shipped with Rust 1.82 | 10:39:48 | |
In reply to @sandro:supersandro.deplease no more of that pattern | 17:17:55 | |
| re-importing nixpkgs is a huge antipattern | 17:18:07 | |
| should absolutely not be doing that | 17:18:15 | |
| 21:40:20 | ||
| 22:52:42 | ||
| 10 Feb 2025 | ||
| I am fine with whatever but I just lack the knowledge to help with anything inside rustc 😕 | 17:08:07 | |
| 11 Feb 2025 | ||
Is there any way to specify a custom --target in buildRustCrate without using crossSystem? | 02:59:07 | |
| (using crate2nix fwiw) | 02:59:18 | |
trying to compile a rust lib for iOS and android. its easy enough to add the extra targets I need using rust-overlay and then use them on the command line | 03:16:05 | |
| but the advice in the manual says use crossSystem. I tried doing roughly this:
My rationale being "I just want to change the target for rustc" | 03:22:36 | |
| but that results in an infinite loop. and i've realized by rationale was flawed, since i don't want to change rustc everywhere, only for my one target | 03:23:06 | |
| * but that results in an infinite loop. and i've realized by rationale was flawed, since i don't want to change rustc everywhere, only for my one target (and perhaps its dependencies) | 03:23:17 | |
| on the verge of giving up and doing a fixed-output runCommand that just invokes cargo in the way I want | 04:04:23 | |
| actually I have something working!!! | 04:40:29 | |
| with crate2nix | 04:40:43 | |
| very jank though | 04:40:46 | |