| 18 Oct 2025 |
matthewcroughan @fosdem | Yes so I think there's a happy balance between conditionals and patches, and that not everything has to be an upstream patch | 12:23:47 |
matthewcroughan @fosdem | like in this case valgrind is pretty heavy and maybe not all platforms should include valgrind | 12:24:04 |
Alyssa Ross | if there's a principled criteria for that, sure | 12:24:18 |
Alyssa Ross | but there's no fundamental reason we should include valgrind for GCC builds and not LLVM ones | 12:24:44 |
matthewcroughan @fosdem | Sure, my discovery has highlighted two things:
- An issue with valgrind that needs to be fixed upstream
- Maybe valgrind is really heavy and we don't need it in mesa for all platforms
| 12:25:44 |
matthewcroughan @fosdem | The reason Alpine has things working with mesa across the board is because they're compiling with less deps in general, so we're probably not going to have working musl for years unless we did the same | 12:26:24 |
Alyssa Ross | we have a "working musl" | 12:26:36 |
matthewcroughan @fosdem | Not always, I know my issue here is LLVM related only, but I've had similar circumstances | 12:26:57 |
Alyssa Ross | yes, packages are broken sometimes | 12:27:21 |
matthewcroughan @fosdem | Like let's say we want to compile Blender with Musl, alpine seems to have that working, but we probably won't due to our enablement of every dep and feature | 12:27:24 |
matthewcroughan @fosdem | And it may be that upstream patching is needed, but it's also the case that we could just compile a more minimal blender. | 12:28:13 |