Mir graphics platform ABI broke in series 0.26 but sonames never changed
Bug #1662455 reported by
Daniel van Vugt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Fix Released
|
High
|
Daniel van Vugt | ||
0.26 |
Fix Released
|
High
|
Daniel van Vugt | ||
mir (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
An ABI break in series 0.26 arose from changes to:
include/
include/
However the applicable ABI(s) never changed from series 0.25:
MIR_SERVER_
MIRPLATFORM_ABI
Related branches
lp://staging/~mir-team/mir/fix-1662455
- Daniel van Vugt: Approve
- Mir CI Bot: Approve (continuous-integration)
-
Diff: 134 lines (+18/-16)8 files modifieddebian/control (+10/-8)
debian/libmirplatform15.install (+1/-1)
debian/mir-platform-graphics-android12.install (+1/-1)
debian/mir-platform-graphics-mesa-kms12.install (+1/-1)
debian/mir-platform-graphics-mesa-x12.install (+1/-1)
src/CMakeLists.txt (+1/-1)
src/platform/symbols.map (+1/-1)
src/platforms/CMakeLists.txt (+2/-2)
Changed in mir: | |
milestone: | none → 0.26.1 |
importance: | Undecided → High |
milestone: | 0.26.1 → 1.0.0 |
assignee: | nobody → Daniel van Vugt (vanvugt) |
status: | New → In Progress |
Changed in mir (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in mir: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
It appears we could safely fix this on lp:mir/0.26 too. Because clients only have direct bindings to libmirclient, and servers don't have direct bindings to libmirplatform or graphics drivers.
You can verify that with:
objdump -x /path/to/binary | grep NEEDED