| 10 Feb 2025 |
trofi | loongarch64's libgcc is broken: https://github.com/NixOS/nixpkgs/pull/381016 | 23:18:25 |
| 11 Feb 2025 |
K900 | I wonder if we can just like | 05:46:12 |
K900 | Not | 05:46:13 |
| 14 Feb 2025 |
| irrelevancyisthygoal One Confused Being changed their display name from One Confused Being to irrelevancyisthygoal One Confused Being. | 00:30:02 |
| irrelevancyisthygoal One Confused Being set a profile picture. | 00:35:24 |
| 15 Feb 2025 |
| BenjB83 joined the room. | 10:14:39 |
| BenjB83 changed their display name from Benjamín Buske to BenjB83. | 10:43:17 |
| 16 Feb 2025 |
| KristijanZic joined the room. | 01:07:07 |
| steeringwheelrules joined the room. | 15:42:02 |
steeringwheelrules | Can QubesOS be mimicked in a reproducible manner by NixOS? | 15:43:10 |
Alyssa Ross | not without a lot of work | 15:43:18 |
Alyssa Ross | (although people are trying) | 15:43:32 |
| 17 Feb 2025 |
Axman6 | That feels like a good answer to most "Can I do X with Nix?" questions 😅 | 06:13:20 |
Tristan Ross | In reply to @steeringwheelrules:tchncs.de Can QubesOS be mimicked in a reproducible manner by NixOS? Technically yes, in nixpkgs probably not. | 18:57:54 |
Tristan Ross | In reply to @qyliss:fairydust.space not without a lot of work Yeah, would be cool to see but idk how practical it'd be to have it. | 18:58:16 |
| 19 Feb 2025 |
K900 | @Alyssa Ross do you have a musl environment built by any chance | 17:32:25 |
K900 | And can test https://github.com/NixOS/nixpkgs/pull/383432 | 17:32:28 |
Alyssa Ross | uh, depends on how well the wifi works in the channel tunne | 18:02:58 |
Alyssa Ross | usually the answer is "not very well" | 18:03:06 |
Alyssa Ross | do you just want it built or runtime tested? | 18:05:39 |
Alyssa Ross | * | 18:08:03 |
Alyssa Ross | Looks like I have staging-next musl built but not master | 18:14:48 |
K900 | Ideally both | 18:16:17 |
Alyssa Ross | Okay, then I'll apply it on top of staging-next and try that | 18:16:35 |
Alyssa Ross | builds | 18:34:37 |
Alyssa Ross | works fine for my very specific use case | 19:25:05 |
| 23 Feb 2025 |
rhelmot | wacky problem I'm coming across... just #include <execinfo.h> on FreeBSD right now doesn't actually work under nixpkgs. The FreeBSD execinfo.h starts with #include <stddef.h> and then __BEGIN_DECLS, which is supposed to be defined in sys/cdefs.h which is included from stddef.h. HOWEVER, stddef is actually being provided not by libc right now, but by clang, it's this file: https://github.com/llvm/llvm-project/blob/main/clang/lib/Headers/stddef.h - this file doesn't actually #include_next<stddef.h> (except for on z/OS) and instead replicates each posix feature of stddef.h | 21:19:12 |
rhelmot | who is at fault for this issue?? is clang allowed to not include_next? is freebsd allowed to rely on its own implicit behaviors for stddef.h? | 21:19:49 |
rhelmot | ah jeez. https://github.com/freebsd/freebsd-src/commit/f382bac49b1378da3c2dd66bf721beaa16b5d471 | 21:32:41 |
| 24 Feb 2025 |
Axman6 | Redacted or Malformed Event | 05:27:14 |