!FBuJyWXTGcGtHTPphC:nixos.org

Nix Rust

722 Members
Rust169 Servers

Load older messages


SenderMessageTime
16 Apr 2026
@esperlily:matrix.orgEsperLily [she/her] i suppose i should take this opportunity to add disallowedReferences to rustc-unwrapped too, as long as we have to rebuild all of the rust packages anyway 06:49:32
@eveeifyeve:matrix.orgeveeifyeve I will ask in here. Can someone when the relibc is merged into nixpkgs, when there is a rustc update can you ping the redox team please? Because we will need to check if that breaks relibc as a lot of C Api's get changed on unstable. An example of this was with 1.94 with VaListImpl being renamed to VaList. 22:20:22
@eveeifyeve:matrix.orgeveeifyeve * I will ask in here. Can someone when the relibc is merged into nixpkgs, when there is a rust update can you ping the redox team please? Because we will need to check if that breaks relibc as a lot of C Api's get changed on unstable. An example of this was with 1.94 with VaListImpl being renamed to VaList. 22:22:25
@eveeifyeve:matrix.orgeveeifyeve * I will ask in here. Can someone when the relibc is merged into nixpkgs, when there is a rust update can you ping the redox team please? Because we will need to check if that breaks relibc as a lot of C Api's get changed on unstable. An example of this was with 1.94 with VaListImpl being renamed to VaList due to it wanting to be C-Abi compatible. 22:24:23
@charles:computer.surgeryCharles ⚡️Tbh I don't think putting relibc in nixpkgs is a good idea at this point because of its reliance on so many nightly features22:36:42
@charles:computer.surgeryCharles ⚡️Redox upstream is aware that relibc doesn't build on newer rustc versions and the recommendation I got is "just use an older rustc" which isn't really an option for nixpkgs aiui22:37:56
@charles:computer.surgeryCharles ⚡️I think nixpkgs probably has enough stuff in it to support doing Redox things with it out of tree, so that's probably best to do for the time being until the reliance on volatile nightly features goes away22:39:18
@charles:computer.surgeryCharles ⚡️* I think nixpkgs probably has enough stuff in it to support doing Redox things with it out of tree, so it's probably best to just do that for the time being, until the reliance on volatile nightly features goes away22:39:53
@charles:computer.surgeryCharles ⚡️
In reply to @charles:computer.surgery
Redox upstream is aware that relibc doesn't build on newer rustc versions and the recommendation I got is "just use an older rustc" which isn't really an option for nixpkgs aiui
I don't think complaining at them every time a new rustc version breaks their build will accomplish anything other than being obnoxious; this is expected behavior with nightly rust
22:41:08
@eveeifyeve:matrix.orgeveeifyeveI am working on fixing that currently. 23:29:48
@eveeifyeve:matrix.orgeveeifyeveNo not every version, but if it breaks relibc to let us know.23:30:17
@eveeifyeve:matrix.orgeveeifyeve* No not every version, but if it breaks relibc to let us know. Because it's important for the build support for redox.23:30:52
@eveeifyeve:matrix.orgeveeifyeveSince it's required at a very early step.23:32:41
@eveeifyeve:matrix.orgeveeifyeve* Since it's required at a very early step when building redox.23:32:58
@eveeifyeve:matrix.orgeveeifyeve* Since it's required at a very early step when building redox packages.23:33:06
@charles:computer.surgeryCharles ⚡️i think you misread what i wrote23:33:07
@eveeifyeve:matrix.orgeveeifyevehttps://gitlab.redox-os.org/eveeifyeve/relibc/-/commits/fix-relibc-for-1-94?ref_type=heads23:36:13
@eveeifyeve:matrix.orgeveeifyeve* https://gitlab.redox-os.org/eveeifyeve/relibc/-/commits/fix-relibc-for-1-9423:36:18
17 Apr 2026
@logn:zirco.devLogN changed their display name from LogN [unavailable @ CinemaCon -> 4/18] to LogN.01:23:38
@eveeifyeve:matrix.orgeveeifyeveIt works again!! I made an upstream pr to fix it: https://gitlab.redox-os.org/redox-os/relibc/-/merge_requests/1204 however they need to update their toolchain first.01:35:09
@eveeifyeve:matrix.orgeveeifyeve* It works again!! I made an upstream pr to fix it: https://gitlab.redox-os.org/redox-os/relibc/-/merge_requests/1204 however they need to update their custom toolchain first.02:12:12
@pyrox:pyrox.devdish [Fox/It/She]

(please correct me if I am wrong on this)

i believe the issue that was being brought up was not this specific breakage, but the fact that if it breaks even somewhat constantly, it will be an additional(potentially unwanted) burden on the rust team to deal with its breakage, even if that is just alerting the redox team to said issue. I would agree with Charles that it may be prudent to let it break and deal with it later as relibc reduces its usage of nightly features.

Your fixes are, i'd like to think at least, appreciated, but the issue is ongoing maintainance rather than a single specific incident

05:26:21
@charles:computer.surgeryCharles ⚡️yeah, that's indeed what i was trying to get at, in addition to the pressure this could/would then put on the redox maintainers05:28:32
@qyliss:fairydust.spaceAlyssa Ross

Rust 1.95 removes support on stable for passing a custom target specification to rustc.

06:00:18
@qyliss:fairydust.spaceAlyssa Ross 😭️ emily dramforever 06:00:49
29 Oct 2021
@grahamc:nixos.org@grahamc:nixos.org set the history visibility to "world_readable".19:57:43
@grahamc:nixos.org@grahamc:nixos.org changed the room name to "" from "".19:57:43
@grahamc:nixos.org@grahamc:nixos.org changed the room topic to "" from "".19:57:43
@server_stats:nordgedanken.devServer Stats Discoverer (traveler bot) joined the room.19:58:21
@voyager:t2bot.ioMatrix Traveler (bot) joined the room.19:59:14

Show newer messages


Back to Room ListRoom Version: 6