Bug 2415824 - mesa-25.3.0-1.fc44 build breaks lld users (Chromium/CEF)
Summary: mesa-25.3.0-1.fc44 build breaks lld users (Chromium/CEF)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: mesa
Version: rawhide
Hardware: Unspecified
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Nick Clifton
QA Contact: Fedora Extras Quality Assurance
URL: https://koji.fedoraproject.org/koji/t...
Whiteboard:
Depends On: 2415065
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-11-19 09:38 UTC by Hoshino Lina
Modified: 2025-12-04 21:25 UTC (History)
17 users (show)

Fixed In Version: binutils-2.45.50-9.fc44 mesa-25.3.0-4.fc44
Clone Of:
Environment:
Last Closed: 2025-11-25 22:52:16 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Hoshino Lina 2025-11-19 09:38:34 UTC
Broken build: https://koji.fedoraproject.org/koji/taskinfo?taskID=139030950

ld.lld: error: corrupt input file: version definition index 0 for symbol gbm_create_device is out of bounds
>>> defined in /usr/lib64/libgbm.so
ld.lld: error: corrupt input file: version definition index 0 for symbol gbm_bo_get_plane_count is out of bounds
>>> defined in /usr/lib64/libgbm.so
ld.lld: error: corrupt input file: version definition index 0 for symbol gbm_bo_get_stride is out of bounds
>>> defined in /usr/lib64/libgbm.so
ld.lld: error: corrupt input file: version definition index 0 for symbol gbm_device_destroy is out of bounds
[...]

This seems to be bug 2415065, which hit the new mesa build in Rawhide.

Reproducible: Always

Comment 1 Hoshino Lina 2025-11-19 09:41:55 UTC
+cc Than, I assume this will break your next Chromium build for rawhide.

Comment 2 Hoshino Lina 2025-11-19 09:59:41 UTC
+ qtwebengine, I'm guessing that probably builds with lld too?

Comment 3 Nick Clifton 2025-11-25 09:48:24 UTC
The latest rawhide binutils (binutils-2.45.50-9.fc44) should resolve this problem.

Comment 4 Fedora Update System 2025-11-25 14:13:19 UTC
FEDORA-2025-09b8062b9b (mesa-25.3.0-4.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-09b8062b9b

Comment 5 Fedora Update System 2025-11-25 22:52:16 UTC
FEDORA-2025-09b8062b9b (mesa-25.3.0-4.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 6 Fedora Update System 2025-11-27 09:29:51 UTC
FEDORA-2025-0cd0e6dd4a (pipewire-1.5.83-3.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-0cd0e6dd4a

Comment 7 Fedora Update System 2025-11-27 10:25:14 UTC
FEDORA-2025-0cd0e6dd4a (pipewire-1.5.83-3.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2025-11-27 12:47:25 UTC
FEDORA-2025-f3760e6a5c (flac-1.5.0-6.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-f3760e6a5c

Comment 9 Fedora Update System 2025-11-27 23:40:14 UTC
FEDORA-2025-f3760e6a5c (flac-1.5.0-6.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2025-11-28 10:24:42 UTC
FEDORA-2025-4b8311a915 (cups-2.4.15-1.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-4b8311a915

Comment 11 Fedora Update System 2025-12-04 12:30:53 UTC
FEDORA-2025-1e73cbc4e8 (cups-2.4.16-1.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-1e73cbc4e8

Comment 12 Fedora Update System 2025-12-04 15:42:11 UTC
FEDORA-2025-3ab098cc60 (cups-2.4.16-2.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-3ab098cc60

Comment 13 Fedora Update System 2025-12-04 21:25:16 UTC
FEDORA-2025-3ab098cc60 (cups-2.4.16-2.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.