| 18 Apr 2026 |
 Yureka (she/her) | https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/41040 | 14:53:23 |
| Yureka (she/her) | honestly a challenge to navigate xD | 14:53:37 |
| Yureka (she/her) | 
Download foo.png | 14:55:08 |
 K900 | Well the good news is that you can just yoink that patch into your config | 14:55:40 |
| K900 | Without a world rebuild | 14:55:42 |
| Yureka (she/her) | or revert to 26.0.4 since the patch does not apply cleanly | 15:01:35 |
| Yureka (she/her) | Redacted or Malformed Event | 15:02:01 |
| K900 | You can also do that | 15:08:43 |
| Yureka (she/her) | anyways not staging-related after all, just the mesa fix release | 15:08:57 |
| K900 | Maybe one day Mesa people will figure out how to run CTS before releasing | 15:09:35 |
| K900 | (it's genuinely a complicated problem, somehow) | 15:09:47 |
 Emil Thorsøe | some testsuite? | 15:11:49 |
| K900 | Multiple, technically | 15:13:04 |
| K900 | https://github.com/khronosgroup/vk-gl-cts | 15:13:12 |
| Emil Thorsøe | I guess it at least needs hw, if drivers are to be tested | 15:15:31 |
| Emil Thorsøe | always makes a bit harder | 15:15:39 |
| Emil Thorsøe | not insurmountable though | 15:15:47 |
| K900 | There's a whole bunch of issues really | 15:16:15 |
 Vladimír Čunát | Uh, the autoconf update is such a PITA for darwin. | 21:53:46 |
| Vladimír Čunát | Too many packages break from getting autoreconf-ed with -std=gnu23 | 21:54:04 |
| Vladimír Čunát | Many packages just aren't ready for such new stuff. | 21:54:33 |
| Vladimír Čunát | I hate that C standard even does get changed by autoreconfig. It doesn't make sense. Only upstream should switch that. | 21:57:05 |
| Vladimír Čunát | * I hate that C standard even does get changed by autoreconf-ing. It doesn't make sense. Only upstream should switch that. | 21:57:23 |
| 19 Apr 2026 |
 Alyssa Ross | Only upstream is supposed to run autoreconf | 06:16:08 |
| Alyssa Ross | That's the design. | 06:16:11 |
| Vladimír Čunát | I know, but not everyone agrees with that. And sometimes you need to apply patches which may make it hard to avoid it. | 07:57:20 |
| Alyssa Ross | Yep, and if we do that, we're opting into keeping up with autoconf changes and should be taking that into consideration. | 08:01:35 |
| Alyssa Ross | It's also changed by new compiler versions by default, right? So even without autoconf it's not solely on upstream. | 08:05:44 |
| Alyssa Ross | What we can do is make sure every time we have to pin a C standard, we send that change upstream so going forward upstream will take responsibility for it | 08:07:37 |
| Vladimír Čunát | We could. But that's even increasing the amount of work that we need to do. | 08:10:57 |
