FS#62495 - [libglvnd] glesv1_cm.pc, glesv2.pc are gone, some packages expect them to exist during configuration

Attached to Project: Arch Linux
Opened by Kyle Devir (QuartzDragon) - Sunday, 28 April 2019, 05:24 GMT
Last edited by Laurent Carlier (lordheavy) - Tuesday, 10 December 2019, 06:34 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No


After upstream Mesa commit b01524fff05eef66e8cd24f1c5aacefed4209f03, glesv1_cm.pc and glesv2.pc disappeared:


The Mesa devs argued that this was really GLVND's responsibility, and opened a bug report for this here:


It has gone ignored for years now, meaning that certain packages, like wlroots, complain and abort as they expect these .pc files to exist.

The patch, https://github.com/NVIDIA/libglvnd/pull/86/commits/5ad628f33033038f0b66622d16e617a606c96224.patch, fixes these issues.

Can it be added to the GLVND packages, to resolve these annoying issues, as Nvidia refuses to do anything about it?
This task depends upon

Closed by  Laurent Carlier (lordheavy)
Tuesday, 10 December 2019, 06:34 GMT
Reason for closing:  Fixed
Additional comments about closing:  libglvnd-1.2.0
Comment by Kyle Devir (QuartzDragon) - Sunday, 28 April 2019, 05:59 GMT
Actually, it turns out that the patch doesn't apply cleanly, so I fixed it up so it applies to that latest packaged version.

wlroots-git is happy now. :)
Comment by Térence Clastres (Terence) - Tuesday, 23 July 2019, 20:20 GMT