Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • mesa mesa
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3,058
    • Issues 3,058
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1,002
    • Merge requests 1,002
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • MesaMesa
  • mesamesa
  • Issues
  • #1846
Closed
Open
Issue created Sep 26, 2019 by Marvin Schmidt@marv

mesa and libglvnd install the same headers

libglvnd installs GL/GLES/GLX/EGL header files since https://github.com/NVIDIA/libglvnd/commit/ab9b5fcc3bf90064418f6915cf4259fa11ffe64b which is included in yesterdays 1.2.0 release. mesa no longer installs the pkg-config files when libglvnd support is enabled but still installs those header files. So in order to prevent collisions between mesa (19.2.0) and libglvnd (1.2.0) one has to either manually remove the headers installed by mesa in favour of the ones installed by libglvnd or build libglvnd with --disable-headers which isn't ideal either since it now provides pkg-config files for headers it doesn't install

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking