You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See libreoffice package update PR @ #26543 with failing builds with error
2024/08/28 15:39:50 INFO checking for eglMakeCurrent in -lEGL... no
2024/08/28 15:39:50 WARN configure: error: libEGL required.
2024/08/28 15:39:50 WARN Error running configure at ./autogen.sh line 321.
I note there was an update to mesa 5 days ago
24.1.5-r0 (4 weeks ago - 2024-07-31 23:42:46 +0000 UTC) in wolfi os repository
24.2.0-r0 (6 days ago - 2024-08-23 02:42:21 +0000 UTC) in wolfi os repository
That update was part of mesa version bump PR #26346
If I revert mesa build time dependencies in the LibreOffice to version 24.1.5-r0 then build does succeed.
Is there further changes required when depending on mesa, and subpackages, version 24.2.0-r0 or is this an issue in the new 24.2.0-r0 version? Was there a change in the ABI?
The text was updated successfully, but these errors were encountered:
Superseding libreoffice version bump PR #27736 build is failing due to the patch not being able to be applied cleanly but once patch is removed it fails in the same manner as previous version bump PR #26543
2024/09/06 17:04:38 INFO checking for gtk+-3.0 >= 3.20 gtk+-unix-print-3.0 gmodule-no-export-2.0 glib-2.0 >= 2.38 atk >= 2.28.1 cairo... yes
2024/09/06 17:04:38 INFO checking for eglMakeCurrent in -lEGL... no
2024/09/06 17:04:38 WARN configure: error: libEGL required.
2024/09/06 17:04:38 WARN Error running configure at ./autogen.sh line 321.
See libreoffice package update PR @ #26543 with failing builds with error
I note there was an update to mesa 5 days ago
That update was part of mesa version bump PR #26346
If I revert mesa build time dependencies in the LibreOffice to version
24.1.5-r0
then build does succeed.Is there further changes required when depending on mesa, and subpackages, version 24.2.0-r0 or is this an issue in the new 24.2.0-r0 version? Was there a change in the ABI?
The text was updated successfully, but these errors were encountered: