| 8 Oct 2023 |
Yuka (she/her) | https://github.com/python/cpython/blob/v3.12.0/configure.ac#L978 | 10:16:49 |
Yuka (she/her) | there it has gnusf and gnuf32 | 10:17:00 |
Yuka (she/her) | starting from python 3.12 | 10:22:41 |
Yuka (she/her) | so my point is not what is or is not currently in the configure script, but that the configure script will change over versions, and the cpython/default.nix is used for all versions of python | 10:23:09 |
Yuka (she/her) | but I'm somewhat for inverting the logic to only rewrite the pythonAbiName for specific abis and otherwise using the nixpkgs parsed.abi.name | 10:24:03 |
Yuka (she/her) | https://github.com/NixOS/nixpkgs/pull/259752 | 11:54:13 |
| 9 Oct 2023 |
Alyssa Ross | hmm, there's no bootstrap tarball for Rust 1.72.1 mips64el-unknown-linux-gnuabi64 | 11:44:12 |
Alyssa Ross | that's not good | 11:44:14 |
Alyssa Ross | because it blocks updating Rust on all platforms | 11:44:25 |
Lotte (it/its)/Cinny (she/her) θΔ& | you could build rust 1.72.1 with 1.72.0 i think i have some derivations for building rust with other rusts somewhere | 11:46:47 |
Alyssa Ross | ideally we'd bootstrap from mrustc, but people don't like it | 11:48:32 |
Alyssa Ross | current policy is not to keep old versions of rust around | 11:48:42 |
Alyssa Ross | aha https://github.com/rust-lang/rust/pull/113274 | 11:51:48 |
Lotte (it/its)/Cinny (she/her) θΔ& | In reply to @qyliss:fairydust.space ideally we'd bootstrap from mrustc, but people don't like it yeah it makes the bootstrap path extremely unpleasant | 11:52:59 |
Lotte (it/its)/Cinny (she/her) θΔ& | tried it out and it took around a day to get it built on just x86 with two pcs which are decently powerful | 11:53:46 |
Lotte (it/its)/Cinny (she/her) θΔ& | tried it out and it took around a day to get rust 1.69 built on just x86 with two pcs which are decently powerful | 11:54:21 |
Lotte (it/its)/Cinny (she/her) θΔ& | imagine that times however often nixos has a mass rebuild lol | 11:54:51 |
Lotte (it/its)/Cinny (she/her) θΔ& | i think it might be better with cargo2nix since you could relatively easily run that on a server farm | 11:55:34 |
Lotte (it/its)/Cinny (she/her) θΔ& | vs standard rust bootstrap which can only run on one system period | 11:56:11 |
raitobezarius | I would not be shocked to use mrustc for mips though | 12:06:55 |
Alyssa Ross | mips doesn't seem like the best arch to start with given how little CPU power most MIPS machines have… | 12:08:07 |
Lotte (it/its)/Cinny (she/her) θΔ& | yeah… | 12:11:00 |
Lotte (it/its)/Cinny (she/her) θΔ& | building a server system on riscv already takes a week lol | 12:11:14 |
raitobezarius | In reply to @qyliss:fairydust.space mips doesn't seem like the best arch to start with given how little CPU power most MIPS machines have… right but unsure what would be the best way here | 12:20:38 |
raitobezarius | I can see easily mrustc bootstrap, keeping old Rust versions around is meh but also second best I suppose, in all cases, it seems like a cross system is better for mips (?) | 12:21:09 |
Lotte (it/its)/Cinny (she/her) θΔ& | although i haven't figured out a way to express "cross compile from x target to host target" | 12:22:44 |
Lotte (it/its)/Cinny (she/her) θΔ& | although i haven't figured out a way to express "cross compile from x target to host target" in nixpkgs | 12:22:45 |
Lotte (it/its)/Cinny (she/her) θΔ& | cross compilation maybe? | 12:22:47 |
raitobezarius | In reply to @lotte:chir.rs although i haven't figured out a way to express "cross compile from x target to host target" in nixpkgs in nixpkgs or nixos? | 12:26:21 |
raitobezarius | you can set up your system as a cross system in nixos by instantiating nixpkgs with crossSystem | 12:26:32 |