Le 30/05/2024 à 22:25, Paul Gevers a écrit :
Currently, shaderc 2023.2-1 is in testing. This version suffers from an
"undefined symbol" bug
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070983). This bug is
fixed in version 2023.8-1 which is now in unstable.
Can you please elaborate how the fix works.
libshaderc1 was in fact underlinked (see also this bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029939), triggering
this kind of undefined symbol errors.
The fix comprises to correctly link the library at build time (see
https://salsa.debian.org/debian/shaderc/-/commit/5e2d70f32363ab86d94a170087303e6fb62a86af).
I don't think a transition for glslang is required here, since the
missing symbol reported by Debian CI exists in library shipped by
glslang in both testing and unstable (I just checked that). The problem
was really a linking issue. Looking at the changelog of glslang, the
update from version 13 to 14 included some changes of how libraries are
built and I think this is the origin of the problem.
As I understand it (but I can be wrong), the current state of glslang
and shaderc in unstable is correct; mixing versions from testing and
unstable triggers bugs that are now fixed in unstable.
Philippe.
