25 Jun 2025 |
Grimmauld (any/all) | oh btw, did the i686 time thing happen yet? | 19:04:25 |
K900 | Nope | 19:04:48 |
K900 | Fuck | 19:04:50 |
Grimmauld (any/all) | XD | 19:04:56 |
K900 | I might be sniped into doing it tomorrow :( | 19:04:59 |
Grimmauld (any/all) | i tried, saw i was totally out of my depth, and gave up after a few hours | 19:05:28 |
emily | it should really only take like five lines | 19:06:58 |
K900 | dooo eeeet | 19:07:26 |
emily | do you want me to do that or test BPI kernels? :p | 19:07:51 |
Grimmauld (any/all) | you said that last time, and then i got stuck for a day | 19:08:09 |
emily | you had it in the wrong file I believe | 19:08:26 |
Tristan Ross | In reply to @emilazy:matrix.org right. but why do we set it to armv8-a explicitly for AArch64? I believe it's because of the difference between generic and armv8-a | 19:15:19 |
Tristan Ross | I do plan on reworking the CPU model stuff after the toolchain attributes PR is merged. I don't like that it's called gcc.arch . | 19:17:14 |
Tristan Ross | https://github.com/NixOS/nixpkgs/pull/365057 almost half a year old now | 19:27:20 |
emily | I will hopefully have time this weekend to catch up on my review backlog. (there's Darwin stuff I need to get to as well) | 19:32:49 |
emily | at a glance cxxrtlib is still wrong though | 19:32:54 |
emily | we don't currently use libcxxrt anywhere I don't think, certainly not on Linux | 19:33:21 |
emily | (FreeBSD probably should but currently doesn't) | 19:33:27 |
Tristan Ross | In reply to @emilazy:matrix.org we don't currently use libcxxrt anywhere I don't think, certainly not on Linux Huh, what should the value be then? | 23:07:27 |
emily | depends on the platform – but libstdc++ is coupled to libsupc++ for RTTI/exceptions and I think we use libstdc++ on most platforms right now | 23:13:26 |
Tristan Ross | Oh, so it should be null or libstdc++? | 23:30:06 |
emily | it should presumably be libsupc++ on Linux at least. | 23:37:19 |
26 Jun 2025 |
aleksana 🏳️⚧️ (force me to bed after 18:00 UTC) | https://github.com/NixOS/nixpkgs/pull/420107
Why we didn't switch to pkgconf like Arch Linux did | 03:47:24 |
Tristan Ross | I lost the issue but we had a discussion on it, I don't remember the outcome. | 03:54:00 |
aleksana 🏳️⚧️ (force me to bed after 18:00 UTC) | Oh right, here | 03:56:15 |
aleksana 🏳️⚧️ (force me to bed after 18:00 UTC) | https://github.com/NixOS/nixpkgs/issues/334195 | 03:56:18 |
Tristan Ross | Ah yeah, it looks like it won't be too long until we can do it. If we get it merged soon, 25.11 would be the version to start transitioning things. Likely drop in 26.05. | 04:00:12 |
Tristan Ross | https://github.com/NixOS/nixpkgs/pull/394610 | 04:00:23 |
aleksana 🏳️⚧️ (force me to bed after 18:00 UTC) | In reply to @rosscomputerguy:matrix.org https://github.com/NixOS/nixpkgs/pull/394610 So it is trying to standarise this behavior?
pkg-config is patched to ignore Requires.private for --cflags without --static , whereas libpkgconf is not. I believe such a change also has to be made for pkgconf to be viable.
| 04:01:14 |
Tristan Ross | I think so, haven't fully read into it. | 04:01:32 |