| 16 Apr 2026 |
 eveeifyeve | * Since it's required at a very early step when building redox. | 23:32:58 |
| eveeifyeve | * Since it's required at a very early step when building redox packages. | 23:33:06 |
 Charles | i think you misread what i wrote | 23:33:07 |
| eveeifyeve | https://gitlab.redox-os.org/eveeifyeve/relibc/-/commits/fix-relibc-for-1-94?ref_type=heads | 23:36:13 |
| eveeifyeve | * https://gitlab.redox-os.org/eveeifyeve/relibc/-/commits/fix-relibc-for-1-94 | 23:36:18 |
| 17 Apr 2026 |
|  LogN changed their display name from LogN [unavailable @ CinemaCon -> 4/18] to LogN. | 01:23:38 |
| eveeifyeve | 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 toolchain first. | 01:35:09 |
| eveeifyeve | * 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 |
 dish [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 | yeah, that's indeed what i was trying to get at, in addition to the pressure this could/would then put on the redox maintainers | 05:28:32 |
 Alyssa Ross |
Rust 1.95 removes support on stable for passing a custom target specification to rustc.
| 06:00:18 |
| Alyssa Ross | 😭️ emily dramforever | 06:00:49 |
 emily | I did always think it was odd that such an esoteric complicated interface was stable | 10:14:18 |
| emily | the definitive proof I live in opposite world is that everyone else's favourite part of Rust (Cargo, the toolchain UX, etc.) is my least favourite | 10:16:07 |
 Crony Akatsuki (balkan/slav) | Nope, you are better of than me | 10:32:48 |
| Crony Akatsuki (balkan/slav) | I don't like rust in general. I just package some rust programs from time to time | 10:33:22 |
| dish [Fox/It/She] changed their profile picture. | 16:58:36 |
 Ralith | cargo's in a weird spot where it's worlds better than what most people are used to but worlds worse than what a build system can be | 20:04:55 |
| Ralith | ultimately it generally achieves what it sets out to do and they've been good about ensuring rustc isn't tightly coupled to it | 20:05:22 |
| emily | build.rs ruined everything | 22:35:33 |
| emily | if not for that it might have been okay | 22:35:35 |
| emily | (but yeah I know, tradeoffs. I get why it's very nice for most people) | 22:35:59 |
| emily | problem is the entire ecosystem orbits around it so a better build system for Rust isn't really achievable, or rather, it still has to pay the cost of the bad things about Cargo and friends | 22:36:55 |
 figsoda | if build.rs didnt exist people will still find a way (proc macros) to do the things build.rs does like running pkg-config | 22:42:35 |
 whispers [& it/fae] | the biggest problem to me is that there aren't more structured ways to the tasks that people usually need. like, in this case, everyone has reinvented running pkg-config and then trying to build the library if you have a feature enabled and so you get to gamble on whether it's any good or you have overrides or anything like that | 22:44:48 |
| whispers [& it/fae] | it takes the idea of maximal flexibility (which you're probably right, people would find a way to do given the rest of landscape) and effectively pushes it into the common case so that even normal tasks require this machinery which is inconsistent and resistant to introspection | 22:46:19 |
| whispers [& it/fae] | * it takes the idea of maximal flexibility (which you're probably right, people would find a way to do given the rest of language) and effectively pushes it into the common case so that even normal tasks require this machinery which is inconsistent and resistant to introspection | 22:46:51 |
| whispers [& it/fae] | * it takes the idea of maximal flexibility (which you're probably right, people would find a way to do given the rest of language) and effectively pushes it into the common case so that even normal tasks require this machinery which is ad-hoc, inconsistent, and resistant to introspection | 22:47:08 |
| whispers [& it/fae] | i suspect a lot of it (e.g. this case of library loading) is mostly down to the fact that it's a lot of work to get right and so it was never implemented, but the effects are the same | 22:48:28 |
| whispers [& it/fae] | * | 22:48:56 |
