| Summary: | media-libs/mesa-amber-21.3.9-r1 is currently incompatible with >=media-libs/mesa-24.2.6 (?) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Dmitry <mittorn> |
| Component: | Current packages | Assignee: | Gentoo X packagers <x11> |
| Status: | UNCONFIRMED --- | ||
| Severity: | minor | CC: | awilfox.gentoo, mittorn |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=943297 https://gitlab.freedesktop.org/mesa/mesa/-/issues/12219 |
||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | Ebuild with workaround | ||
|
Description
Dmitry
2024-11-29 16:56:34 UTC
Created attachment 912724 [details]
Ebuild with workaround
Proposed workaround keeping mesa-amber in separate package:
move conflicting libs to /opt/mesa-amber and add rpath with patchelf
Tested on i965 driver: both mesa versions works and can be switched with environment variable, starting xorg with amber works too, but driver selected in /usr/share/glvnd/egl_vendor.d/ needs to be compatible with xorg DRI driver selection (Option "DRI" "foo" in xorg.conf's Device secion)
/opt isn't necessarily correct either, imo. USE=-gbm should fix at least some parts of loading, and glapi can be built static which should fix other parts. I was able to get Sway to seem to work that way, but I haven't had time to debug X11 further yet - it was still segfaulting for me on my Intel 945G test box (a 32-bit MacBook1,1). I'm not sure if it would be possible to rename libgbm to libgbm_amber or such, to make gbm work again. I believe this is the way forward, but I'm also trying to work with upstream to see what they think the best way to approach this is. (This also came up at https://bugs.gentoo.org/943297#c2, but it's unrelated to the original bug there.) 24.2.0 is where the incompatibility was most pronounced: https://gitlab.freedesktop.org/mesa/mesa/-/commit/93511c1c5c5fb60166c806d417e4b4378bf1fb31 But it likely stopped working at the 23.0.0 branchpoint: https://gitlab.freedesktop.org/mesa/mesa/-/commit/1026d29344192755dd340d6ac13a9674189d2d61 (In reply to A. Wilcox (awilfox) from comment #2) > /opt isn't necessarily correct either, imo. > > USE=-gbm should fix at least some parts of loading, and glapi can be built > static which should fix other parts. I was able to get Sway to seem to work > that way, but I haven't had time to debug X11 further yet - it was still > segfaulting for me on my Intel 945G test box (a 32-bit MacBook1,1). > > I'm not sure if it would be possible to rename libgbm to libgbm_amber or > such, to make gbm work again. I believe this is the way forward, but I'm > also trying to work with upstream to see what they think the best way to > approach this is. Maybe better using /usr/lib64/mesa? But i'm not sure how to handle multilib in that case. renaming libgbm to libgbm_amber will prevent using amber libgbm directly. For x11 on 945, it may segfaults without DRI=i915c xorg.conf option (because amber patch renames i915 to i915c). On KBL GT2 it tries to load iris_dri and crashes without correct DRI option, it seems, dri driver may be forced in xorg-intel driver I don't have the ability/capacity to test and maintain mesa-amber. If it's going to continue to exist in ::gentoo, it needs a maintainer. |
